lean manifacturing(from TPS -Toyota Production System)• eliminate waste• reduce costs and time to market• continuous improvement
lean software development 2003 - Mary Poppendieck, Tom Poppendieck, “Lean Software Development: An Agile Toolkit”“maximize customer value while minimizing waste”
Agile Software Development • Individuals and interactions over processes and tools • Customer collaboration over con- tract negotiation • Responding to change over follow- ing a plan [www.agilemanifesto.org - 2001]
VISUALIZEChoose simple and efficient tools, where everybody can visualize thestate of your project(s!) and of single tasks inside them.Whenever possible, opt for phisical (vs digital) tools, like boards on theteam room walls.Always know where we are / how far we got.
MEASUREBeing able to measure both our goal and our current situation isa key step in order to understand and see the actual distance be-tween the two.Es. How do we define the SUCCESS of this web project (Pageviews? Ads revenue? Registered users? ...)Define actionable goals.I can measure my productivity, the number of bugs closed after theproduct release, the average delivery time of an additional feature,...Metrics are essentials to measure, compare and make corrections.
INSPECT AND ADAPTALWAYS do retrospectives.Try to understand what did not work the way it was expected to,last time.Find the cause(s). Fix the process.
PROTOTIPEWP is perfect for prototiping! The 1st “demo” can be online in aflash!Use that, with your customer, and limit meetings, plans, require-ments, based on “abstract ideas” .
DELIVERY OFTENMake small, progressive releases. Minimize risks!Remember to prioritize most relevant things / features(importance in terms of business value).
COMUNICATEWith your customers. And with your colleagues.Talk. Ask. And listen.(Which does not mean to spend whole days in endless meetings ;-)
COLLABORATEWork together, with the colleagues, and the customers, and not againstthem (nor anybody by his/her own).The project success must be a shared goal.(This is also called “alignment”)
LIMIT (IT)Do not add unnecessary complexity.Do not code unrequested features.Do your best, to “obtain more with less”.(Ex: Choosing hosting for a WP project. Maybe for that sitewp.com is just great, or godaddy is fine, or ...)Limit Work in Progress (WIP)
IMPROVEPut yourself in a mood of constant self-improvement and continuouslearning (KAIZEN)
Embrace change! Things change. It’s a fact. We have to live with it.(requirements change, budgets change, customers change, technolo- gies change, stakeholders, market, competitors, WP changes ;-) We can do our best to manage change. Smartly. To work better. We’re NOT predestined to mental strain, headache, rage, overwork.
REDUCE WASTE“Eliminate waste”.Unfinished features are waste. As well as delivered features neverused. And unread documentation. And meetings without a clearfocus and scope. And sofware defects. And pauses in software de-velopment (while waiting for ...)All that does not produce value is potentially muda (waste).
FOCUS ON VALUEWhat does actually generate value, for my customer, in this webapp? (ie: “makes him earn money”) What’s superfluous?What, in my organization, is central in respect to this value produc-tion? What’s superfluous?
Study, take part, share! www.agileday.it (Roma, November 2011) www.webdebs.org (Brescia , once a month) http://tech .groups.yahoo.com/group/milano-xpug/www.linkedin .com/groups/Lean-Agile-Italy-1944601 and much , much , much more !