Keeping Your PHP Lean

Keeping Your PHP Lean

Chris Cornutt [email protected]

ZendCon ’09 - Unconference

Wednesday, October 21, 2009

mailto:[email protected]


What is Lean?The goal of lean thinking is to improve the development of applications by reducing waste both in the development process and in the processes surrounding it.

This builds quality into the application and allows you to deliver a more complete, more robust end product.


Being Lean

•Customer value

•Mapped value stream

•Continuous flow

•Customer-focused pull

•Strive for perfection


History Lesson

•based on Toyota Production System

• “just in time”

•Autonomation

•DOTWIMP


Types of Waste•Defects

•Overproduction

•Transportation

•Waiting

• Inventory

•Motion

•Processing

•(Undervaluation)Wednesday, October 21, 2009

Lean Principles•Eliminate waste

•Build quality in

•Create knowledge

•Defer commitment

•Deliver fast

•Respect people

•Optimize the whole


Agile vs Lean

•Goals are different

•Scope is different

•Lean refines the process, not just the development

•Play well together


AgileDev

BusinessNeeds

Lean thinks

BIGGER

and smaller...

CustomerUse


Lean Planning

•Prioritize requirements

•Consider code reuse

• “Last responsible moment”

•Streamline the flow


Practice Zero

•Required for effective development

•Source control control

•Scripted builds

•Simpler testing, integration


Importance of Testing

•Good tests help with good code

•Tests as documentation

•Forces the developer to become a user

• “Red, Green, Refactor”


Less Code

•Same amount of work

• Just work smarter!

•Fewer lines of code

•Optimized, tested, effective


Lean Code

• “Just in time”

•Trim the fat

• Implement best practices

• Justify the future

•Remember the 80/20 rule!


Lean Terms


Kaizen

•Standardize

•Calculate the performance difference

• Implement it

•Change standard to include new process

•Lather, rinse, repeat


Value Stream Map

•Easily find The Problems

•Remove waste

•Focuses on time, not cost

•Assumes that the rest will follow


VSM: Waterfall


The Five Whys

•Ask “why”

•At least five times, more can be good too

•Root cause discovery

•Discovery along the way


Kanban

•Signal for replenishment

•Similar to the Agile boards (post-its)

• “Work unit” measurements

•Limit each step’s units allowed

•Make it visible!


Kanban : Board


Chris Cornutt

[email protected]

@enygma

@phpdeveloper

http://joind.in/talk/view/973

Contact




http://joind.in/talk/view/??

http://joind.in/talk/view/??

Keeping Your PHP Lean

Technology

Transcript of Keeping Your PHP Lean