1 - introduction to lean product development 05052015104744
DESCRIPTION
Lean Product DevelopmentTRANSCRIPT
Steven Borg | Co-Founder & Strategist, Northwest CadenceAndrew Clear | ALM Consultant, Northwest Cadence
Lean Product DevelopmentPrinciples & Techniques for Software Organizations
Meet Andrew Clear | @aclear16• ALM Consultant, Northwest Cadence– Bias towards principles and management techniques– ALM Ranger– “It’s self-organization within a framework…”
Meet Steven Borg | @stevenborg• Co-founder & Strategist, Northwest Cadence– Bias toward math and proofs• But understand the importance of culture
–Microsoft ALM MVP since 2005– Love focusing on teamwork and the delivery of value
Course Topics
Lean Product Development01 | Introduction to Lean Product Development
06 | Feedback loops
02 | Economics over emotion 07 | Managing queues03 | Value flow over resource utilization and timelines 08 | Batch sizes
04 | System over local optimization 09 | Kanban, next steps and conclusions
05 | Decentralized decision making over command and control
Setting Expectations• Target Audience–Mid to senior level managers– Anyone interested in understanding Lean Product
Development• Suggested Prerequisites/Supporting Material– Donald Reinertsen, Principles of Product Development Flow–Mary & Tom Poppendieck, Lean Software Development– David J Anderson, Kanban: Successful Evolutionary Change
for your Technology Business
• Microsoft Virtual Academy– Free online learning tailored for IT Pros and Developers – Over 1M registered users– Up-to-date, relevant training on variety of Microsoft
products• “Earn while you learn!” – Get 50 MVA Points for this event!– Visit http://aka.ms/MVA-Voucher – Enter this code: LeanSftw (expires 4/20/2014)
Join the MVA Community!
Click to edit Master subtitle style01 | Introduction to Lean Product
DevelopmentSteven Borg | Co-Founder & Strategist, Northwest CadenceAndrew Clear | ALM Consultant, Northwest Cadence
Lean Product Development
Optimizing the flow of value through a system with inherent variation
Why you should care• The “project” paradigm doesn’t fit with modern
continuous deployment• No concept of intellectual inventory, or that it costs
us money• Focus on individual efficiency• Misunderstanding of variability• Management through proxies for value
Why you should care
Completely utilized, highly efficient IT shops that somehow never seem to produce what our customers
need when they need it.
Where it comes from• Quite a few different schools of thought, using very
similar vocabulary– Lean software development (Mary & Tom Poppendieck)– Lean product development (Donald Reinertsen)– Agile manifesto– PMBOK (agile or otherwise)
• This course aligns most strongly with lean product development, but includes aspects of the others
Principles Methodologies Enterprise Agility
Practices
agile
lean
Scrum XP
RUP AgileUP
Agile
SAFe
Scrum of Scrums
DADASD
TDD WIP limits User Stories Batch sizes CI\CD Backlogs Pair Programming
Today’s discussion structure
Principles• Economics over emotions• Value flow over resource
utilization• System over local
optimizations• Decentralized decision making
over command and control
Practices• Feedback loops• WIP limits• Batch sizes• Managing queues
Culture flag
Don’t let culture and process change become a bootstrapping problem; understand both and let them work together.
©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.