Your SlideShare is downloading. ×
Agile Evolution with Kanban
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Agile Evolution with Kanban

410
views

Published on

Given at the BCS in Edinburgh on the 1/8/2012. Talk about change and failed attempt to introduce XP into an organisation. Suggests potential reasons for the failure, introduces Kanban and then …

Given at the BCS in Edinburgh on the 1/8/2012. Talk about change and failed attempt to introduce XP into an organisation. Suggests potential reasons for the failure, introduces Kanban and then speculates as to how change might have been more successful in an evolutionary manner with Kanban.

Published in: Technology, Business

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
410
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • We don’t have this landscape on most software development projects/teams etc\n
  • We don’t have this landscape on most software development projects/teams etc\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • 1. current\n2. abyss\n3. valley\n4. ascent\n5. mountaintop\n
  • \n
  • \n
  • \n
  • Karl Scotland\n
  • - Invented by Ohno in the early 50’s after studying supermarkets\n - uses the rate of demand to control the rate of production\n
  • set of techniques and practices used to provoke and help manage change\nno such thing as: \n - the Kanban Software Development Process \n - or the Kanban Project Management Method. \n
  • Background\nReason for Kanban\n
  • Changed the way the work works\n
  • \n
  • \n
  • does not prescribe a specific set of roles or process. \n\n\n\n
  • \n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • Card content\nStand Ups\n\n
  • \n
  • \n
  • \n
  • \n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • Limits set on agreed capacity\nWhy \n - Reduce Multitasking\n - Helps reduce lead time - Little’s Law (Lead time = WIP/Throughput)\n\nPull system main stimuli for change & improvement\n- Creates slack for improvement\n
  • \n
  • flow should be monitored, measured and reported\nchange can be evaluated\n
  • SPC - Variation in lead time\nCFD - Check that the Kanban System is working correctly\n
  • SPC - Variation in lead time\nCFD - Check that the Kanban System is working correctly\n
  • \n
  • - hard to discuss improvement if the system is not understood\n - with explicit policies discussions are emotional and anecdotal \n - facilitate consensus around improvement suggestions\n - Leads to a self organising team\n
  • \n
  • \n
  • \n
  • \n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • FD - demand caused by a failure to do something or do something right for the customer\nTC - e.g. expensive and time consuming release process\n\n
  • \n\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n\n\n
  • \n
  • \n
  • \n
  • \n
  • \n\n\n
  • \n
  • \n
  • \n
  • \n
  • 1. current\n2. abyss\n3. valley\n4. ascent\n5. mountaintop\n
  • \n
  • Transcript

    • 1. Agile revolution or an agile evolution? Chris McDermott @chrisvmcd chris.v.mcdermott@gmail.com
    • 2. Planning game Release planning Iterations Small releases
    • 3. Planning game Release planning Iterations Small releases Common code ownership Test driven development Refactoring Emergent design Pair programming Continuous integration
    • 4. Planning game Release planning Iterations Small releases Common code ownership Test driven development Refactoring Emergent design Pair programming Continuous integration Code as documentationGeneralists On site customer Sustainable pace
    • 5. Planning game Stand up meetings Release planning Retrospectives Iterations Small releases Common code ownership Test driven development Refactoring Emergent design Pair programming Continuous integration Code as documentationGeneralists On site customer Sustainable pace
    • 6. nothing happened
    • 7. why?!
    • 8. it is threatening!
    • 9. Iterations Release planning Stand up meetings Project ManagersSustainable pace Pair programming
    • 10. GeneralistsOn site customer Business Analysts Documentation light
    • 11. Test driven development Sustainable pace ContinuousCommon code integration ownership Emergent design Developers Refactoring Pair programming On site customer Generalists
    • 12. Automated testing Sustainable pace QA Generalists Documentation light
    • 13. it is risky!
    • 14. desired 1 2 3 4 5Capability current Time
    • 15. desired 1 2 3 4 5Capability current organisational threshold Time
    • 16. why not forget about adopting an “Agile” method?
    • 17. feedback quality through craftsmanshipimproved lead times strive for increased culture of trustpredictability agility patience
    • 18. what is Kanban and how can it help? stop starting, start finishing
    • 19. kanbanhttp://availagility.files.wordpress.com/2008/10/kenji-kanban-2.jpg
    • 20. kanban system• WIP (Work In Progress) limited pull system.
    • 21. Kanban Method• A change management system that uses kanban systems to provoke change • Catalyst for evolutionary change • Can help to create an culture of continuous improvement
    • 22. Microsoft XIT Worst to Best in 9 monthshttp://www.agilemanagement.net/AMPDFArchive/From_Worst_to_Best_in_9_Months_Final_1_3.pdf
    • 23. Corbis
    • 24. Principles• Start with what you do now• Agree to pursue incremental, evolutionary change• Initially, respect the current process, roles, responsibilities & job titles• Encourage leadership at all levels
    • 25. Visualise the workflow
    • 26. Demand Analysis Development Test Released
    • 27. Demand Analysis Development Test Released In
    • 28.  Progress Done In
    • 29.  Progress Done In
    • 30.  Progress Done
    • 31. Demand Analysis Development Test Released 214*** In
    • 32.  Progress Done In
    • 33.  Progress Done In
    • 34.  Progress Done Task 214***Taskdescription description **/**/2011**/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task TaskTask description description description description description description Taskdescription **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011**/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task TaskTask description description description description description descriptiondescription **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 **/**/2011 **/**/2011**/**/2011 214*** 214*** 214*** 214*** 214*** Task Task 214*** Task TaskTask description description Task description descriptiondescription **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011**/**/2011 214*** 214*** 214*** 214*** 214*** Task Task 214*** Task TaskTask description description Task description descriptiondescription **/**/2011 **/**/2011 description **/**/2011 **/**/2011**/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task 214*** Task TaskTask description description Task description descriptiondescription **/**/2011 **/**/2011 description **/**/2011 **/**/2011**/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task 214*** Task TaskTask description description Task description descriptiondescription **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011**/**/2011 **/**/2011 **/**/2011 214*** 214*** Task 214*** Task description Task description **/**/2011 description **/**/2011 **/**/2011 Reason
    • 35. Type: Feature 2146767 Work item type Digital tracking - Bug number - Feature Ability to search by product- Non Functional - etc Cust: Chris BA: Mike Due: 09/06 Dev: Liz Start: 07/06 QA: Brian End: 08/06 Tracking dates Contacts
    • 36. http://www.a-chau.net/gallery2/d/99171-2/supermarket_queue.jpg
    • 37. http://blog.flowkaizen.com/why-physical-card-walls-are-important
    • 38. Limit WIP
    • 39. Demand
    • 40.  (4) Analysis
    • 41.  (5) Development
    • 42.  (6) Test Released In
    • 43.  Progress Done In
    • 44.  Progress In
    • 45.  Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** Task Task Task description description description **/**/2011 **/**/2011 **/**/2011 214*** 214*** Task Task description description **/**/2011 **/**/2011
    • 46. Demand
    • 47.  (4) Analysis
    • 48.  (5) Development
    • 49.  (6) Test Released In
    • 50.  Progress Done In
    • 51.  Progress In
    • 52.  Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** Task Task description description **/**/2011 **/**/2011
    • 53. Demand
    • 54.  (4) Analysis
    • 55.  (5) Development
    • 56.  (6) Test Released In
    • 57.  Progress Done In
    • 58.  Progress In
    • 59.  Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** Task description **/**/2011
    • 60. Demand
    • 61.  (4) Analysis
    • 62.  (5) Development
    • 63.  (6) Test Released In
    • 64.  Progress Done In
    • 65.  Progress In
    • 66.  Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** 214*** Task 214*** Task Task Task description Task description description description **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011
    • 67. Demand
    • 68.  (4) Analysis
    • 69.  (5) Development
    • 70.  (6) Test Released In
    • 71.  Progress Done In
    • 72.  Progress In
    • 73.  Progress 214*** Done Done 214*** Task description (2) Task description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** Task description description description description description description Task description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Reason **/**/2011 214*** 214*** 214*** Task 214*** Task Task description Task description description **/**/2011 description **/**/2011 **/**/2011 **/**/2011 **/**/2011
    • 74. Manage Flow
    • 75. Demand
    • 76.  (4) Analysis
    • 77.  (5) Development
    • 78.  (6) Test Released In
    • 79.  Progress Done In
    • 80.  Progress In
    • 81.  Progress Done Done 214*** 214*** Task Task description (2) description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task Task description description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task Task description description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Lead Time
    • 82. Make process policies explicit
    • 83. Demand
    • 84.  (4) Analysis
    • 85.  (5) Development
    • 86.  (6) Test Released In
    • 87.  Progress Done In
    • 88.  Progress In
    • 89.  Progress Done Done 214*** 214*** Task Task description (2) description **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task Task description description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task Task description description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 Definition of Done: Definition of Done: Definition of Done: • Goal is clear • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
    • 90. Implement feedback loops
    • 91. Improve collaboratively (using models the scientific method)
    • 92. Demand
    • 93.  (4) Analysis
    • 94.  (5) Development
    • 95.  (6) Test Released In
    • 96.  Progress Done In
    • 97.  Progress In
    • 98.  Progress Done Done 214*** Task description (2) **/**/2011 214*** 214*** 214*** Task Task Task description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** Task Task Task description description description **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** Task Task Task description description description **/**/2011 **/**/2011 **/**/2011 214*** 214*** Task Task description description **/**/2011 **/**/2011 214*** 214*** Task Task description description **/**/2011 **/**/2011 **/**/2011 Definition of Done: Definition of Done: Definition of Done: • Goal is clear • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
    • 99. Demand
    • 100.  (4) Analysis
    • 101.  (5) Development
    • 102.  (6) Test Released In
    • 103.  Progress Done In
    • 104.  Progress In
    • 105.  Progress Done Done 214*** Task description (2) **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** Task description **/**/2011 214*** Task description **/**/2011 Definition of Done: Definition of Done: Definition of Done: • Goal is clear • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
    • 106. Demand
    • 107.  (4) Analysis
    • 108.  (5) Development
    • 109.  (6) Test Released In
    • 110.  Progress Done In
    • 111.  Progress In
    • 112.  Progress Done Done 214*** Task description (2) **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** Task description **/**/2011 214*** Task Failure Demand description **/**/2011 Definition of Done: Definition of Done: Definition of Done: • Goal is clear • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
    • 113. Demand
    • 114.  (4) Analysis
    • 115.  (5) Development
    • 116.  (6) Test Released In
    • 117.  Progress Done In
    • 118.  Progress In
    • 119.  Progress Done Done 214*** Task description (2) **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task Task description description description description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** 214*** 214*** 214*** Task Task Task Task description description description description **/**/2011 **/**/2011 **/**/2011 **/**/2011 214*** Task description **/**/2011 214*** Task Failure Demand description **/**/2011 Definition of Done: • Goal is clear Transaction Cost Definition of Done: Definition of Done: • Code clean checked in • Customer accepted • First tasks defined • Integrated tested • Ready for production • Story split, if necessary • Running on UAT env
    • 120. Improvements VisualiseFeedback Limit Loops WIP Explicit Policies Manage Flow
    • 121. Improvements VisualiseFeedback Limit Loops WIP Explicit Policies Manage Flow
    • 122. what if?
    • 123. LT C U GO Y A R O R CC IS ECIFI V SPA D XT NTE C O
    • 124. Input Analysis Dev Build Test UAT Signed
    • 125.  Off Doing Done Doing Done Doing Done
    • 126. Input Analysis Dev Build Test UAT Signed
    • 127.  Off Doing Done Doing Done Doing Done 214***Taskdescription **/**/ 214*** 214*** 214*** 214*** Task Task TaskTask description description descriptiondescription **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** Task Task Task description description description **/**/ **/**/ **/**/ 214*** 214*** Task description Task **/**/ description **/**/ 214*** Task 214*** description Task **/**/ description **/**/ 214*** Task description **/**/ 214*** Task description **/**/
    • 128. Input Analysis Dev Build Test UAT Signed
    • 129.  Off Doing Done Doing Done Doing Done 214*** 214***Task Taskdescription description **/**/ **/**/ Reason 214*** 214*** 214*** 214*** Task Task Task 214***Task description description description Taskdescription **/**/ **/**/ **/**/ description **/**/ 214*** **/**/ 214*** 214*** Reason Task Task Task description description description **/**/ 214*** **/**/ **/**/ Task 214*** description 214*** Task **/**/ Reason description Task **/**/ description 214*** **/**/ 214*** Task description Task 214*** **/**/ description Task Reason **/**/ description **/**/ 214*** Task description **/**/ 214*** Task description **/**/
    • 130. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 131. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 132. Improvements VisualiseFeedback Limit Loops WIP Explicit Policies Manage Flow
    • 133. Input Analysis Dev Build Test UAT Signed
    • 134.  Off 214*** Doing Done Doing Done Doing Done 214*** TaskTask descriptiondescription **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task TaskTask description description description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** Task Task Task Task 214*** Task description description description descriptionTask description **/**/ **/**/ **/**/ **/**/description **/**/ **/**/ 214*** 214*** 214*** 214*** Task Task Task Task 214*** description description description descriptionTask **/**/ **/**/ **/**/ **/**/description **/**/ 214*** 214*** 214*** Task Task Task 214*** description description descriptionTask **/**/ **/**/ **/**/description **/**/ 214*** 214*** TaskTask description **/**/description **/**/ 214*** Task description **/**/
    • 135. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 136. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 137. Input Analysis Dev Build Test UAT Signed
    • 138.  Off 214*** Doing Done Doing Done Doing Done 214*** TaskTask descriptiondescription **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task TaskTask description description description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** Task Task Task Task 214*** Task description description description descriptionTask description **/**/ **/**/ **/**/description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** Task Task Task Task 214*** description description description descriptionTask **/**/ **/**/ **/**/ **/**/description **/**/ 214*** 214*** 214*** Task Task Task 214*** description description descriptionTask **/**/ **/**/ **/**/description **/**/ 214*** 214*** TaskTask description **/**/description **/**/ 214*** Task description **/**/
    • 139. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 140. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 141. Input Analysis Dev Build Test UAT Signed
    • 142.  Off Doing Done Doing Done Doing Done 214*** 214*** 214***Task Task Taskdescription description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task 214*** 214*** description description description description Task TaskTask description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** Task Task Task Task 214*** 214*** 214*** Task Task TaskTask description description description description description **/**/ **/**/ **/**/ description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** Task Task Task TaskTask description description description description **/**/ **/**/description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** Task Task TaskTask description description descriptiondescription **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** Task Task Task description description description **/**/ **/**/ **/**/ 214*** 214*** Task description Task **/**/ description **/**/ unpredictable
    • 143. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 144. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 145. Improvements VisualiseFeedback Limit Loops WIP Explicit Policies Manage Flow
    • 146. Input
    • 147.   Analysis
    • 148.  (3) Dev
    • 149.  (8) Build Test
    • 150.  (6) UAT Signed
    • 151.  Off (4) Done 214*** Doing Done Doing Done Doing 214*** 214***Task Task Taskdescription description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** 214***Task description description Task Task description description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task 214*** 214*** Task Task TaskTask description description description description description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** Task Task 214***Task description Task Task descriptiondescription **/**/ **/**/ description description **/**/ **/**/ **/**/ 214*** 214*** Task 214*** Task Task description **/**/ description description **/**/ **/**/ 214*** 214*** Task Task description **/**/ description **/**/
    • 152. Input
    • 153.   Analysis
    • 154.  (3) Dev
    • 155.  (8) Build Test
    • 156.  (6) UAT Signed
    • 157.  Off (4) Done 214*** Doing Done Doing Done Doing 214*** 214***Task Task Taskdescription description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** 214***Task description description Task Task description description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task 214*** 214*** Task Task TaskTask description description description description description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** Task Task 214***Task description Task Task descriptiondescription **/**/ **/**/ description description **/**/ **/**/ **/**/ 214*** 214*** Task 214*** Task Task description **/**/ description description **/**/ **/**/ 214*** 214*** Task Task description **/**/ description **/**/
    • 158. Input
    • 159.   Analysis
    • 160.  (3) Dev
    • 161.  (8) Build Test
    • 162.  (6) UAT Signed
    • 163.  Off (4) Done 214*** Doing Done Doing Done Doing 214*** 214***Task Task Taskdescription description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** 214***Task description description Task Task description description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task 214*** 214*** Task Task TaskTask description description description description description description descriptiondescription **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** Task Task 214***Task description Task Task descriptiondescription **/**/ **/**/ description description **/**/ **/**/ **/**/ 214*** 214*** Task 214*** Task Task description **/**/ description description **/**/ **/**/ 214*** 214*** Task Task description **/**/ description **/**/
    • 164. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 165. user stories regular releases stand up meetings retrospectivescommon code ownership refactoring tdd Agile Toolkit bdd sustainable on site pace customer pair continuous programming automated integration acceptance testing
    • 166. Improvements VisualiseFeedback Limit Loops WIP Explicit Policies Manage Flow
    • 167. Input
    • 168.  (4) Analysis
    • 169.  (3) Dev
    • 170.  (8) Build Test
    • 171.  (6) UAT Signed
    • 172.  Off Done 214*** Doing Done Doing Done Doing 214*** 214*** Task Task Task description description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task Task Task 214*** 214*** Task description description Task Task description description description description description **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ description description **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** 214*** 214*** Task Task Task Task 214*** 214*** Task Task Task Task description description description description description description description description **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ **/**/ 214*** 214*** 214*** 214*** Task Task 214*** Task description Task Task description description **/**/ **/**/ description description **/**/ **/**/ **/**/ 214*** 214*** 214*** Task Task 214*** Task Task description description **/**/ **/**/ description description **/**/ **/**/ 214*** Task description **/**/ Definition of Done: Definition of Done: DoD: Definition of Done: • Goal is clear • Code clean checked in • On UAT env • Passes acc test • Acceptance criteria • Integrated tested • Running on UAT env Pull Criteria: • Least familiar with
    • 173. so...
    • 174. reduce the threatby doing it collaboratively and with well understood reason
    • 175. reduce the risk by doing it incrementally
    • 176. desiredCapability current Time
    • 177. Questions? September 21st 22nd 2012 Dynamic Earth www.leanagilescotland.com @LeanAgileScot