Kanban and Agile at Scale  Gil Irizarry  Constant Contact  June 2012Copyright © 2012 Constant Contact Inc.   1
Start with Lean Principles  • Eliminate Waste  • Build Quality In  • Create Knowledge  • Defer Commitment  • Deliver Fast ...
Add Kanban Principles  • Start with what you do now  • Agree to pursue incremental, evolutionary  change  • Respect the cu...
Properties of Kanban  • Visualize the workflow          • States in the team board are a reflection          of how a team...
Pull, not Push  • Work items should be accepted by the team.  • Work should not be pushed onto the team  by the organizati...
Some tools and techniques  • A value stream map to identify the work  states in a process  • Kanban board that has lanes m...
Kanban at scale  • Implied in the principles is that there are no  iterations.  • Teams should work continuously.  • Howev...
The Release Train  • If a deliverable misses a release (the train), it  simply waits to capture the next one  • We don’t p...
Automation  • To make this work, as much as possible needs  to be automated  • Automated builds upon code check-ins  • Aut...
Frequent deployments  • Code built but waiting to be deployed is not  producing value  • Shorter, frequent deployments bri...
Milo the dog  • Etsy – Code as CraftCopyright © 2012 Constant Contact Inc.   11
DevOps (DevTestOps?)  • There is a growing movement to reduce, if not  eliminate, the boundaries between development  and ...
Upcoming SlideShare
Loading in …5
×

Gil Irizarry, Constant Contact presentation from MassTLC seminar on taking your agile development to the next level

886 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
886
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Gil Irizarry, Constant Contact presentation from MassTLC seminar on taking your agile development to the next level

  1. 1. Kanban and Agile at Scale Gil Irizarry Constant Contact June 2012Copyright © 2012 Constant Contact Inc. 1
  2. 2. Start with Lean Principles • Eliminate Waste • Build Quality In • Create Knowledge • Defer Commitment • Deliver Fast • Respect People • Optimize the Whole Leading Lean Software Development: Results Are not the Point by Mary and Tom PoppendieckCopyright © 2012 Constant Contact Inc. 2
  3. 3. Add Kanban Principles • Start with what you do now • Agree to pursue incremental, evolutionary change • Respect the current process, roles, responsibilities & titlesCopyright © 2012 Constant Contact Inc. 3
  4. 4. Properties of Kanban • Visualize the workflow • States in the team board are a reflection of how a team completes its work • Limit work-in-progress (WIP) • Manage Flow • Aim for continuous flow • Make Process Policies Explicit • Improve CollaborativelyCopyright © 2012 Constant Contact Inc. 4
  5. 5. Pull, not Push • Work items should be accepted by the team. • Work should not be pushed onto the team by the organization. Pull: Push:Copyright © 2012 Constant Contact Inc. 5
  6. 6. Some tools and techniques • A value stream map to identify the work states in a process • Kanban board that has lanes mapped to the identified states • Cumulative flow diagram to chart the progress and status of work • Metrics such as cycle time to identify where to improveCopyright © 2012 Constant Contact Inc. 6
  7. 7. Kanban at scale • Implied in the principles is that there are no iterations. • Teams should work continuously. • However, still need software releases or other integration activity that’s often iterative. • How to address this dilemma?Copyright © 2012 Constant Contact Inc. 7
  8. 8. The Release Train • If a deliverable misses a release (the train), it simply waits to capture the next one • We don’t penalize a team if a deliverable is not done at the end of a release and misses the release train • Teams plan and test continuously • It’s OK if a team pulls functionality from a release within a release cycle • It’s OK if a team starts work for the next release in the current releaseCopyright © 2012 Constant Contact Inc. 8
  9. 9. Automation • To make this work, as much as possible needs to be automated • Automated builds upon code check-ins • Automated tests built into the builds • Automated deploys of successful builds • Automated e-mails containing results of build and test runsCopyright © 2012 Constant Contact Inc. 9
  10. 10. Frequent deployments • Code built but waiting to be deployed is not producing value • Shorter, frequent deployments bring value to your customers sooner • Again, automation is the keyCopyright © 2012 Constant Contact Inc. 10
  11. 11. Milo the dog • Etsy – Code as CraftCopyright © 2012 Constant Contact Inc. 11
  12. 12. DevOps (DevTestOps?) • There is a growing movement to reduce, if not eliminate, the boundaries between development and operations • Operations today looks a lot like coding. Should be scripting everything. This is called DevOps. • Some have extended the concept to DevTestOps. QA today looks a lot like software development too. The days of manually executing a test plan are over.Copyright © 2012 Constant Contact Inc. 12

×