http://www.flickr.com/photos/yuvalyeret/265568342/in/set-72157594323037021/<br />Intro to product development flow<br />Yu...
www.linkedin.com/in/yuvalyeret<br />Blogging @ http://yuvalyeret.com<br />Presentations at http://www.slideshare.net/yyere...
What we will cover in this webinar<br />Why we need to think about flow – common dysfunctions of development processes<br ...
So how does an agile process look compared to traditional?<br />www.slideshare.net/wnazzaro/agile-it-and-the-business-comm...
The Waterfall approach<br />Requirements<br />Design<br />Code<br />Testing<br />DONE<br />Requirements<br />Design<br />C...
Ideal world Feature-Driven <br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<...
But what we typically see is...<br />Feature Freeze<br />Coding Done<br />DONE<br />Hardening<br />R<br />D<br />C<br />T<...
What this causes<br />Feature Freeze<br />Coding Done<br />DONE<br />QA GAP<br />Time<br />
Time to Complete<br />Many features in parallel<br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Par...
Scrumgate<br />Feature Freeze<br />DONE<br />Hardening<br />D<br />C<br />T<br />Requirements<br />D<br />C<br />T<br />D<...
And...<br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<...
Big Features<br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<b...
What about multiple teams?<br />T1<br />Team1<br />Team2<br />Integration Team<br />T2<br />Coding Done<br />T<br />R<br /...
A scrum example<br />Features in progress? <br />	3 			versus 		1<br />
So now that we see the pain...<br />
What do we do? <br />DavidAnderson’s recipe for success: <br />Focus on Quality <br />Reduce Work-in-Progress, Deliver Oft...
First impediment to flow – big Features/Batches<br />BIG Features<br />17<br />
That are stuck for long in each stage<br />18<br />
Move from rocks to pebbles<br />19<br />
Moving to small units of work is NOT enough<br />If our policy/behavior is early start of everything<br />“Working on many...
How do we Visualize the work status in more depth?<br />TODO<br />Work in Process (WIP)<br />Done<br />21<br />
The Cumulative Flow Diagram<br />Introduced in Lean Product Development by Don Reinertsen and David Anderson<br />Visualiz...
Mushon<br />Inbar<br />Inbar<br />Elad<br />Mushon<br />Elad<br />Inbar<br />Elad<br />Mushon<br />How to do a CFD<br />23...
How to do a CFD<br />24<br />
What can teams learn from Cumulative Flow?<br />Total Scope<br />Dev Burnup<br />Work in Process (WIP)<br />Done Burnup<br...
Work in Process<br />High Work-in-process leads to longest lead times to feedback and higher costs<br />Low work-in-proces...
How can I take this to my context?<br />
Visualize and manage the flow on your work tracking system <br />HP QualityCenter<br />Microsoft TFS<br />IBM Lotus Notes<...
If you don’t currently have a work tracking system – you can use a kanban system<br />AgileZen (RallyDev)<br />LeanKit Kan...
A Kanban board – Not a Must for Flow<br />But will SIGNIFICANTLY improve it<br />
Common questions/concerns about flow<br />
Isn’t this a waterfall?<br />
But wouldn’t the bottleneck slow everything? <br />
An example - focus on quality<br />Feature Freeze<br />Coding Done<br />DONE<br />Hardening<br />R<br />D<br />C<br />T<br...
How do I commit? <br />
How does flow relate to iterations/scrum?<br />
How is this different than Scrum? <br />Applicability?<br />Scope?<br />Prescription?<br />The interesting question – how ...
Mashups<br />DONE DONE<br />DONE<br />READY<br />IterationsFlow<br />IterationsFlow<br />IterationsFlow<br />38<br />
Project/Component Kanban Board<br />Flow<br />DONE<br />READY!<br />Opportunity Team & Project Manager<br />Scrum Teams<b...
Initiative/Program Kanban Board<br />
Scrum/Kanban - The way WIP limits/PULL work<br />Kanban board<br />Scrum board<br />Done :o)<br />To do<br />Ongoing<br />...
approaches to change<br />Evolution (Kanban) <br />Performance<br />Revolution (Scrum)<br />(kanban the tool)<br />Time<br...
Recommendations for scrummers looking at flow<br />If scrum works for you – don’t touch it!<br />If you see dysfunctions c...
Main attractiveness of flow<br />Finally, an agile-based approach that easily supports:<br />Mainstream/pragmatic organiza...
Take aways<br />Visualize YOUR workflow<br />Limit work in process:<br />Stop starting, start finishing<br />Identify bott...
It is not crucial to nail down the accurate optimized WIP Limit / Batch Size / Sprint length<br />½ the WIP, ½ the batch s...
Go do some reading...<br />
Questions?<br />
Summary<br />Limit work in process:<br />Stop starting, start finishing<br />49<br />
www.linkedin.com/in/yuvalyeret<br />Blogging @ http://yuvalyeret.com<br />Presentations at http://www.slideshare.net/yyere...
Upcoming SlideShare
Loading in...5
×

Introduction to product development flow

3,062

Published on

This is the presentation for a pre-LSSC11 webinar on the topic of Lean Product Development flow. I’m going to introduce an approach to mixing Lean and Agile in order to achieve end to end agility. This is a major focus of my work in the recent 2 years with AgileSparks clients.

Register for the Webinar which is on 16/3 at http://www.netobjectives.com/free-seminar-schedule/lssc11-session-4-intro-lean-product-development-flow-mar-2011-webinar

This is also the topic I will talk about in my Agile Israel 2011 session “Techniques and experiences for managing end to end Releases/Projects/Programs using Kanban and Flow” http://agilesparks.com/KanbanandFlowLecture

Published in: Business, Technology
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,062
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
157
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide
  • TraditionalLockup capital for a long time by having significant work in process before seeing any realization of business valueAgileBy releasing incrementally we open up the opportunity to obtain business value much earlier than would otherwise be possible and prior to the completion of the overall projectThis can be done by breaking the project into &quot;feature chunks&quot; that are delivered every few weeksIn this webinar, we will focus on FLOW and process, not so much on roles, responsibilities and other aspects of Lean/Agile
  • Focus on feature release-level qualityNot just storyreduce features in progress at the release levelReducing stories/tasks in progress at a person/team level is not enoughDeliver features often (To internal consumers / to production )Delivering stories is not enough
  • With big features everything is harder – time to define, to stabilize, to control variance, to test, to verify, to reproduce …Symptoms:Our features/user stories are too big to fit into one iteration – we need LONGER iterations..We need a long time to nail down the design for this. Our PSP for this iteration is a high-level design…Solution?Effective User Story Analysis to create Minimum Marketable Features (MMF)DesignEither do all design up frontOr have a growing evolutionary designEveryone works on highest priority – EVEN if outside comfort zoneNeed to improve collective code ownershipDevelopers need to feel safe to work everywhere in the team’s codebase
  • Incease time until we can test, and complexity to InstallSymptoms:Our features/user stories are too big to fit into one iteration – we need LONGER iterations..We need a long time to nail down the design for this. Our PSP for this iteration is a high-level design…Solution?Effective User Story Analysis to create Minimum Marketable Features (MMF)DesignEither do all design up frontOr have a growing evolutionary designEveryone works on highest priority – EVEN if outside comfort zoneNeed to improve collective code ownershipDevelopers need to feel safe to work everywhere in the team’s codebase
  • Also used to manage variability
  • How
  • More widely applicableLooks end to end – not just at the team levelTypically complementaryScrum at the team levelFlow at the e2e levelFlow to READY, iterate to DONE, FLOW to DONE DONE
  • Limit wip – applicable to every layer
  • Introduction to product development flow

    1. 1. http://www.flickr.com/photos/yuvalyeret/265568342/in/set-72157594323037021/<br />Intro to product development flow<br />Yuval Yeret<br />
    2. 2. www.linkedin.com/in/yuvalyeret<br />Blogging @ http://yuvalyeret.com<br />Presentations at http://www.slideshare.net/yyeret/<br />Yuval Yeret<br />yuval@agilesparks.com<br />Http://lssc11.leanssc.org<br />@yuvalyeret<br /> Agile Professionals in Israel - I'm there - Are you?  <br />
    3. 3. What we will cover in this webinar<br />Why we need to think about flow – common dysfunctions of development processes<br />Flow as part of a recipe for success<br />How to enable flow<br />How to see flow<br />Common questions/concerns about flow<br />Flow and Iterations/Scrum<br />What to do tomorrow with flow<br />
    4. 4. So how does an agile process look compared to traditional?<br />www.slideshare.net/wnazzaro/agile-it-and-the-business-community/<br />
    5. 5. The Waterfall approach<br />Requirements<br />Design<br />Code<br />Testing<br />DONE<br />Requirements<br />Design<br />Code<br />Testing<br />Requirements<br />Design<br />Code<br />Testing<br />Requirements<br />Design<br />Code<br />Testing<br />Requirements<br />Design<br />Code<br />Testing<br />Requirements<br />Design<br />Code<br />Testing<br />Time<br />
    6. 6. Ideal world Feature-Driven <br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Time<br />
    7. 7. But what we typically see is...<br />Feature Freeze<br />Coding Done<br />DONE<br />Hardening<br />R<br />D<br />C<br />T<br />QA GAP<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Time<br />
    8. 8. What this causes<br />Feature Freeze<br />Coding Done<br />DONE<br />QA GAP<br />Time<br />
    9. 9. Time to Complete<br />Many features in parallel<br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Parallel - WIP<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Requirements<br />Design<br />Code<br />Testing<br />DONE<br />R<br />D<br />C<br />T<br />Time<br />R<br />D<br />C<br />T<br />Requirements<br />Design<br />Code<br />Testing<br />R<br />D<br />C<br />T<br />Requirements<br />Design<br />Code<br />Testing<br />R<br />D<br />C<br />T<br />Time<br />Requirements<br />Design<br />Code<br />Testing<br />Requirements<br />Design<br />Code<br />Testing<br />Ideal Flow<br />Waterfall<br />Requirements<br />Design<br />Code<br />Testing<br />Time<br />
    10. 10. Scrumgate<br />Feature Freeze<br />DONE<br />Hardening<br />D<br />C<br />T<br />Requirements<br />D<br />C<br />T<br />D<br />C<br />T<br />D<br />C<br />T<br />D<br />C<br />T<br />D<br />C<br />T<br />Time<br />
    11. 11. And...<br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Time<br />
    12. 12. Big Features<br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Time<br />DONE<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Time<br />
    13. 13. What about multiple teams?<br />T1<br />Team1<br />Team2<br />Integration Team<br />T2<br />Coding Done<br />T<br />R<br />T1<br />T2<br />T<br />R<br />T1<br />T2<br />T<br />DONE<br />R<br />T1<br />T2<br />T<br />R<br />T1<br />T2<br />T<br />R<br />T1<br />T2<br />T<br />R<br />T1<br />T2<br />T<br />Time<br />
    14. 14. A scrum example<br />Features in progress? <br /> 3 versus 1<br />
    15. 15. So now that we see the pain...<br />
    16. 16. What do we do? <br />DavidAnderson’s recipe for success: <br />Focus on Quality <br />Reduce Work-in-Progress, Deliver Often <br />Balance Demand against Throughput <br />Prioritize <br />Reduce Variability and Improve the Process <br />
    17. 17. First impediment to flow – big Features/Batches<br />BIG Features<br />17<br />
    18. 18. That are stuck for long in each stage<br />18<br />
    19. 19. Move from rocks to pebbles<br />19<br />
    20. 20. Moving to small units of work is NOT enough<br />If our policy/behavior is early start of everything<br />“Working on many things in parallel will ensure high utilization”<br />“Everything is important”<br />“Each engineer has his own baby feature, they don’t want to collaborate, and there is a high collaboration overhead”<br />Batch size is still HIGH<br />20<br />
    21. 21. How do we Visualize the work status in more depth?<br />TODO<br />Work in Process (WIP)<br />Done<br />21<br />
    22. 22. The Cumulative Flow Diagram<br />Introduced in Lean Product Development by Don Reinertsen and David Anderson<br />Visualize where the Features/Stories are in the workflow across time<br />TODO<br />Work in Process (WIP)<br />Done<br />22<br />
    23. 23. Mushon<br />Inbar<br />Inbar<br />Elad<br />Mushon<br />Elad<br />Inbar<br />Elad<br />Mushon<br />How to do a CFD<br />23<br />
    24. 24. How to do a CFD<br />24<br />
    25. 25. What can teams learn from Cumulative Flow?<br />Total Scope<br />Dev Burnup<br />Work in Process (WIP)<br />Done Burnup<br />Real Done<br />Burnup<br />25<br />Average Cycle Time<br />
    26. 26. Work in Process<br />High Work-in-process leads to longest lead times to feedback and higher costs<br />Low work-in-process greatly reduces lead times to feedback<br />Results in more effective and safer projects<br />
    27. 27. How can I take this to my context?<br />
    28. 28. Visualize and manage the flow on your work tracking system <br />HP QualityCenter<br />Microsoft TFS<br />IBM Lotus Notes<br />JIRA<br />Etc..<br />
    29. 29. If you don’t currently have a work tracking system – you can use a kanban system<br />AgileZen (RallyDev)<br />LeanKit Kanban<br />29<br />
    30. 30. A Kanban board – Not a Must for Flow<br />But will SIGNIFICANTLY improve it<br />
    31. 31. Common questions/concerns about flow<br />
    32. 32. Isn’t this a waterfall?<br />
    33. 33. But wouldn’t the bottleneck slow everything? <br />
    34. 34. An example - focus on quality<br />Feature Freeze<br />Coding Done<br />DONE<br />Hardening<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />R<br />D<br />C<br />T<br />Time<br />
    35. 35. How do I commit? <br />
    36. 36. How does flow relate to iterations/scrum?<br />
    37. 37. How is this different than Scrum? <br />Applicability?<br />Scope?<br />Prescription?<br />The interesting question – how they can complement each other<br />
    38. 38. Mashups<br />DONE DONE<br />DONE<br />READY<br />IterationsFlow<br />IterationsFlow<br />IterationsFlow<br />38<br />
    39. 39. Project/Component Kanban Board<br />Flow<br />DONE<br />READY!<br />Opportunity Team & Project Manager<br />Scrum Teams<br />From my talk at #LSSC10... – Amdocs Case Study<br />
    40. 40. Initiative/Program Kanban Board<br />
    41. 41. Scrum/Kanban - The way WIP limits/PULL work<br />Kanban board<br />Scrum board<br />Done :o)<br />To do<br />Ongoing<br />Done :o)<br />To do<br />Ongoing<br />2<br />A<br />A<br />B<br />B<br />C<br />C<br />D<br />D<br />FLOW<br />FLOW<br />WIP limited per unit of time(iteration)<br />WIP limited per workflow state<br />Source: HenrikKniberg<br />
    42. 42. approaches to change<br />Evolution (Kanban) <br />Performance<br />Revolution (Scrum)<br />(kanban the tool)<br />Time<br />42<br />
    43. 43. Recommendations for scrummers looking at flow<br />If scrum works for you – don’t touch it!<br />If you see dysfunctions consider how flow can help you<br />Look at flow as a way to scale effectively<br />
    44. 44. Main attractiveness of flow<br />Finally, an agile-based approach that easily supports:<br />Mainstream/pragmatic organizations – wanting to improve, avoiding a revolution<br />Large/Complex environments where feature teams are not enough<br />
    45. 45. Take aways<br />Visualize YOUR workflow<br />Limit work in process:<br />Stop starting, start finishing<br />Identify bottlenecks/constraints and think how to improve <br />performance<br />This applies to all LAYERS (including the META one)<br />A pragmatic tip - Think how to <br />introduce Flow to YOUR work <br />tracking system<br />
    46. 46. It is not crucial to nail down the accurate optimized WIP Limit / Batch Size / Sprint length<br />½ the WIP, ½ the batch size, can be a good start...<br />Based on ReinertsenProduct Development Flow<br />
    47. 47. Go do some reading...<br />
    48. 48. Questions?<br />
    49. 49. Summary<br />Limit work in process:<br />Stop starting, start finishing<br />49<br />
    50. 50. www.linkedin.com/in/yuvalyeret<br />Blogging @ http://yuvalyeret.com<br />Presentations at http://www.slideshare.net/yyeret/<br />Yuval Yeret<br />yuval@agilesparks.com<br />Http://lssc11.leanssc.org<br />@yuvalyeret<br /> Agile Professionals in Israel - I'm there - Are you?  <br />
    51. 51. Images Attribution<br />http://www.flickr.com/photos/yuvalyeret/265568342/in/set-72157594323037021/<br />www.slideshare.net/wnazzaro/agile-it-and-the-business-community<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×