Scrum, Kanban and  Scalable Agile              March 13, 2012Damon PooleAndy Singleton                 www.assembla.com
AgendaIntroduction                       5 min.Scrum & Kanban –                                   30 min.   Damon PooleLik...
Damon Poole President, Valtivity Consulting Senior Coach, Eliassen Group Creator of multiple Jolt-award winning  produc...
Andy Singleton Founder and President, Assembla CTO of Assembla, leading a development team that spans 16 countries on fo...
Assembla Experience In 2011, we ran 3 week iterations (and getting slower). In 2012, we are doing daily releases. Each f...
Scrum & Kanban Like Chocolate and Peanut Butter                                         Valtivity
Overview Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban O...
Software Development Nirvana                     Continuous flow of                     working software             Team ...
 Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece...
ProductManagement             Customers   Valtivity
 Why bother? Bird’s eye view of Scrum Problems with Scrum Bird’s eye view of Kanban One-piece-flow (aka small batch s...
ProductManagement             Customers   Valtivity
Int  ProductManagement             Customers         Valtivity
Int  ProductManagement             Customers         Valtivity
Problems With Multi-Team Synchronization  Can’t say you are “shippable” until fully integrated  Hardening/stabilization ...
 Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece...
Kanbanbacklog                     todo                     wip                 coded                   tested             ...
 Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece...
What’s in a User Story  3226 – User wants   5  to undo a depot  operation                          Valtivity
Features of All Shapes and Sizes           Specify           DesignD             S           Code           Integrate     ...
One Piece Flow3226 – User  5                              I   W   Twants to undo adepot operation   S   D     C           ...
One Piece Flow                                                                    I       W           T    S              ...
One Piece Flow        W                       WS D C       I T   S    D    C        I      T        D                     ...
One Piece Flow        W                 W                  W                 WS D C       I T   S D C       I T   S D C   ...
 Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece...
Taskboard/Limited WIP/Pull    todo                    wip                  coded                   tested                 ...
todo                    wip                coded                    tested                     done                       ...
todo                    wip                coded                    tested                     done                       ...
todo                      wip                coded                    tested                     done                     ...
todo         wip                coded                    tested                     done       3244 – Surveyor            ...
todo         wip                coded                    tested                     done       3244 – Surveyor            ...
todo         wip                coded                    tested                     done       3244 – Surveyor            ...
 Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece...
✔                    ✔                       ✔                    ✔                       ✔                    ✔?         ...
✔               ✔       ✔           ✔       ✔✔           ✔       ✔           ✔           ✔✔               ✔       ✔       ...
Trailing 4 Week Burnup                      4 Week Burnup                 20  Story Points                 15             ...
Calculating Velocity Per iteration                                              Iteration Velocity                        ...
✔           ✔       ✔           ✔       ✔        ✔       ✔           ✔           ✔          ✔✔           ✔       ✔        ...
“Pure” Scrum           An Example MixSelf Organizing Team   Self Organizing TeamTeam Member            Team MemberProduct ...
 Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece...
Multi-Stage Continuous Integration                                         Int  ProductManagement                    Custo...
Multi-Stage Continuous Integration                                 Int                                Int                 ...
Individuals and Interactions  ProductManagement                    Customers        Valtivity
Agile Project Management  ProductManagement                  Customers      Valtivity
SCM (Version Control)                     Web                    Mobile                                Int                ...
Continuous Integration                      Web                     Mobile                                 Int            ...
Continuous Delivery Whole product touch point after every story Working software                         Int after ever ...
Continuous Delivery Flow continues around any problems                                         Int                       ...
Valtivity Learn more: http://www.Valtivity.com Agile Whole Team Training  • For the whole team  • $200/person or $1,000 ...
Problems with Scrum Teams limited to about 10 people, then you are into hierarchy and out of agile Explicitly designed f...
Solution: Scalable AgilePrioritize at beginningNo iteration plan                                              Plan at endN...
Simple Scalable AgilePrioritize at beginningNo iteration plan                                           Plan at endNo reso...
Simple Planner                 Valtivity
Simple Planner - New Column              Quickly enter tickets.              Simple format collects              informat...
Simple Planner - Backlog             Backlog is the heart of your             planning process. Sort in             PRIOR...
Simple Planner – Current work with Load                    Ticket count, points, and                    capacity at top o...
Current shows on Cardwall…                             Valtivity
Scalable Agile: Pull code throughPrioritize at beginningNo iteration plan                                            Plan ...
Merge Request                Valtivity
Merge Request– Contribute and Review                        Person submitting a                        request (contribut...
Merge Request– Clear instructions                       Open panels to get                       clear instructions      ...
Merge Request -             Request can come              from a branch              (Gerrit-style              workflow)...
Solution: Scalable AgilePrioritize at beginningNo iteration plan                                              Plan at endN...
Assembla Experience In 2011, we ran 3 week iterations, and it was getting slower. In 2012, we are doing daily releases. ...
Questions?Damon PooleAndy Singleton                 www.assembla.com
Upcoming SlideShare
Loading in …5
×

Scrum, Kanban, and Scalable Agile

2,153 views

Published on

Watch the recorded webinar at: http://youtu.be/Vb0PzjGq4AI

Note: SlideShare does not support slide animation so download the slides to see Damon's animations.



These are the slides from a Webinar that covered how to accelerate software development by combining elements of Scrum (with fixed-length sprints), Kanban (continuous flow with rapid completion of each selected task), and Scalable Agile (multiple contributing teams working on a big project).

Agile expert Damon Poole describes how to introduce Kanban into a Scrum process, how to accelerate development with "One Piece Flow", and how to coordinate the work of multiple teams.

You also get a look at two soon-to-be-released features of Assembla. Company founder Andy Singleton previews the "Simple Planner" view of Assembla tickets with an AJAX UI that will allow you to move effortlessly between Scrum iteration planning and Kanban. He also describes the Advanced Merge Request feature that can help you manage continuous development and release.

Published in: Technology, Art & Photos
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,153
On SlideShare
0
From Embeds
0
Number of Embeds
11
Actions
Shares
0
Downloads
102
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide
  • Do as little as possible with the highest possible value as fast as possibleWhat do we do that is like this today? Hot fixes! (patches)
  • Scrum is fairly straight forward when you have just one team, the challenge starts to increase as you have multiple interdependent teams.
  • Scrum is fairly straight forward when you have just one team, the challenge starts to increase as you have multiple interdependent teams.
  • Scrum is fairly straight forward when you have just one team, the challenge starts to increase as you have multiple interdependent teams.
  • Scrum is fairly straight forward when you have just one team, the challenge starts to increase as you have multiple interdependent teams.
  • You may or may not have a backlog.
  • each task that we are going to do needs each of these phases. And each task not matter what the size they all require those stages to be done.Uses heart monitoring, change color schema, and change heart rate monitor – responsible amountof attentionResponsible amount of attention
  • Poll: How many doing Scrum use a task board?Poll: stories of how taskboard have helped? Limited WIP have helped?Kanban is like Scrum in flight
  • When things are running smoothly, this is what you will see!
  • When things are running smoothly, this is what you will see!
  • When things are running smoothly, this is what you will see!
  • When things are running smoothly, this is what you will see!
  • When things are running smoothly, this is what you will see!
  • When things are running smoothly, this is what you will see!
  • When things are running smoothly, this is what you will see!
  • When things are running smoothly, this is what you will see!
  • Enter and sort tickets with a fast AJAX UI2. Assign points with one-click "small/medium/large" estimates3. Make a backlog list in priority order. This is a foundation of agile planning. Drag to sort. 4. Or, use these icons to "send to top" for things you want to work on, and "send to bottom" if you don't. Icons show on mouse over. 5. Click "load" to move tickets with <capacity> points into the Current milestone. Or, drag tickets manually from the top of Backlog. To run a scrum-style process with iterations, select "Load" to start the iteration, and finish the tickets without reloading. To run a continuous, Kanban-style process, just load frequently.6. Work with Current tickets right on the Planner, or move over to the Cardwall and List views for an expanded, configurable workspace.7. When you finish an iteration, select "Close Iteration" to move closed tickets to a closed milestone and create a new Current milestone.Can calculate a default capacity using a 4 week trailing average
  • Submit a merge request with a description. You can link it to a ticket.2. In the Reviewer role, you can:- Get changes and test them- Vote with the buttons. You should also comment in this case.- Merge. The system can do a server-side merge if there is no conflict and votes are positive- Reject the request with "Ignore"3. Open the "Get changes" panel for specific instructions about how to fetch the code or just use the copy icon.4. In the contributor role, you can get the most recent changes, edit them, and submit a new (and improved) version.5. Just "git branch" to make a branch for review. Contribute to a branch in the same repository (Gerrit-style temporary branches) or in a related clone (Github style forks).6. Write review comments, respond to requests, and discuss options in the attached discussion thread.7. Understand the change by looking at the "Changesets" and "Files Affected" tabs.
  • Scrum, Kanban, and Scalable Agile

    1. 1. Scrum, Kanban and Scalable Agile March 13, 2012Damon PooleAndy Singleton www.assembla.com
    2. 2. AgendaIntroduction 5 min.Scrum & Kanban – 30 min. Damon PooleLike Chocolate and Peanut ButterScalable Agile Preview - Simple planner 10 min. Andy Singleton - Advanced merge requestQ&A 15 min. Valtivity
    3. 3. Damon Poole President, Valtivity Consulting Senior Coach, Eliassen Group Creator of multiple Jolt-award winning products 20 years of process improvement ranging from small co-located teams to 80 team global development shops. Past President of Agile New England Author of “DIY Agile Kickstart” Founder and past CTO and CEO of AccuRev Valtivity
    4. 4. Andy Singleton Founder and President, Assembla CTO of Assembla, leading a development team that spans 16 countries on four continents Blogger and frequent speaker on accelerating software development Previously founder of PowerSteering Software and Cambridge Interactive Valtivity
    5. 5. Assembla Experience In 2011, we ran 3 week iterations (and getting slower). In 2012, we are doing daily releases. Each feature or fix is delivered faster Smaller releases put less stress on the team Uses a “Current” milestone and Assembla planning Uses Advanced Merge Request Took about 1.5 months to switch Biggest time expenditure was making complete, on- demand test environments at Amazon EC2 Valtivity
    6. 6. Scrum & Kanban Like Chocolate and Peanut Butter Valtivity
    7. 7. Overview Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity
    8. 8. Software Development Nirvana Continuous flow of working software Team Done stories as check points $ • Fast Customers • Small increment • Maximum value Valtivity
    9. 9.  Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity
    10. 10. ProductManagement Customers Valtivity
    11. 11.  Why bother? Bird’s eye view of Scrum Problems with Scrum Bird’s eye view of Kanban One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity
    12. 12. ProductManagement Customers Valtivity
    13. 13. Int ProductManagement Customers Valtivity
    14. 14. Int ProductManagement Customers Valtivity
    15. 15. Problems With Multi-Team Synchronization  Can’t say you are “shippable” until fully integrated  Hardening/stabilization iterations  “QA iterations” offset from “Dev iterations”  Integration iterations  Visibility into problems is clearest at end of iteration  Resolution may not come for multiple iterations Valtivity
    16. 16.  Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity
    17. 17. Kanbanbacklog todo wip coded tested done3244 – User wants 3256 – User wants 3226 – User wants 4246 – User wants 3241 – User wantsto remove a 8 to rename a depot 1 to undo a depot 5 to unhide a depot 2 to hide a depot 2replica operation 3249 – User wants 3247 – User wants 3146 – User wants 3236 – User wants to copy a depot 3 to combine depots 5 to replicate a 8 to split a depot 5 depot 3246 – User wants 3216 – User wants a list of depots 3 to remove a depot 1 1) Visual system of managing work 2) Limited work in progress 3) Work is pulled through the system Valtivity
    18. 18.  Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity
    19. 19. What’s in a User Story 3226 – User wants 5 to undo a depot operation Valtivity
    20. 20. Features of All Shapes and Sizes Specify DesignD S Code Integrate C I Document W Write tests D T Test Valtivity
    21. 21. One Piece Flow3226 – User 5 I W Twants to undo adepot operation S D C D Within an Iteration Valtivity
    22. 22. One Piece Flow I W T S D C W T DS D C I D S D C I D D S D C I W T W T I W T S D C W TS D C I D D S D C I D W T I W T S D C W TS D C I D D S D C I D W T Within an Iteration Valtivity
    23. 23. One Piece Flow W WS D C I T S D C I T D D Within an Iteration Valtivity
    24. 24. One Piece Flow W W W WS D C I T S D C I T S D C I T S D C I T D D D D W W WS D C I T S D C I T S D C I T D D D W W WS D C I T S D C I T S D C I T D D D Within an Iteration Valtivity
    25. 25.  Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity
    26. 26. Taskboard/Limited WIP/Pull todo wip coded tested done3256 – User wants 3226 – User wants 4246 – User wants 3241 – User wantsto rename a depot 1 to undo a depot 5 to unhide a depot 2 to hide a depot 2 operation3249 – User wants 3247 – User wants 3146 – User wants 3236 – User wantsto copy a depot 3 to combine depots 5 to replicate a 8 to split a depot 5 depot3246 – User wants 3246 – User wants 3216 – User wantsto create a depot 5 a list of depots 3 to remove a depot 13246 – User wantsto combine depots 5 Valtivity
    27. 27. todo wip coded tested done 3244 – Surveyor 3242 – Surveyor 3241 – User wants wants to remove 1 wants to browse 3 to take a survey 5 a question survey results 3245 – Surveyor 3246 – Surveyor wants to create a 3 wants to create a 2 multiple choice true/false question question 3243 – Surveyor wants to add a 3 new question3247 – Surveyorwants to add a 3freeform question Valtivity
    28. 28. todo wip coded tested done 3244 – Surveyor 3242 – Surveyor 3241 – User wants wants to remove 1 wants to browse 3 to take a survey 5 a question survey results 3245 – Surveyor 3246 – Surveyor wants to create a 3 wants to create a 2 multiple choice true/false question question 3243 – Surveyor wants to add a 3 new question3247 – Surveyorwants to add a 3freeform question Valtivity
    29. 29. todo wip coded tested done 3244 – Surveyor 3242 – Surveyor 3241 – User wants wants to remove 1 wants to browse 3 to take a survey 5 a question survey results 3245 – Surveyor 3246 – Surveyor wants to create a 3 wants to create a 2 multiple choice true/false question question 3243 – Surveyor wants to add a 3 new question3247 – Surveyorwants to add a 3freeform question Valtivity
    30. 30. todo wip coded tested done 3244 – Surveyor 3242 – Surveyor 3241 – User wants wants to remove 1 wants to browse 3 to take a survey 5 a question survey results 3245 – Surveyor 3246 – Surveyor wants to create a 3 wants to create a 2 multiple choice true/false question question 3243 – Surveyor wants to add a 3 new question 3247 – Surveyor wants to add a 3 freeform question Valtivity
    31. 31. todo wip coded tested done 3244 – Surveyor 3242 – Surveyor 3241 – User wants wants to remove 1 wants to browse 3 to take a survey 5 a question survey results 3245 – Surveyor 3246 – Surveyor wants to create a 3 wants to create a 2 multiple choice true/false question question 3243 – Surveyor wants to add a 3 new question 3247 – Surveyor wants to add a 3 freeform question Valtivity
    32. 32. todo wip coded tested done 3244 – Surveyor 3242 – Surveyor 3241 – User wants wants to remove 1 wants to browse 3 to take a survey 5 a question survey results 3245 – Surveyor 3246 – Surveyor wants to create a 3 wants to create a 2 multiple choice true/false question question 3243 – Surveyor wants to add a 3 new question 3247 – Surveyor wants to add a 3 freeform question Valtivity
    33. 33.  Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity
    34. 34. ✔ ✔ ✔ ✔ ✔ ✔? ✔ ? ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Done Backlog grooming ? Retrospective Story estimation Iteration Review Choose stories Valtivity
    35. 35. ✔ ✔ ✔ ✔ ✔✔ ✔ ✔ ✔ ✔✔ ✔ ✔ ✔ ✔ ? ? Valtivity
    36. 36. Trailing 4 Week Burnup 4 Week Burnup 20 Story Points 15 10 5 0 Trailing 4 weeks Valtivity
    37. 37. Calculating Velocity Per iteration Iteration Velocity 40 Story Points 30 20 10 0 IterationsTrailing 4 weeks 4 Week Velocity 40 Story Points 30 20 10 0 Iterations Valtivity
    38. 38. ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔✔ ✔ ✔ ✔ ✔ ✔ ? ? Valtivity
    39. 39. “Pure” Scrum An Example MixSelf Organizing Team Self Organizing TeamTeam Member Team MemberProduct Owner Product OwnerScrum Master Scrum MasterSprint Planning Weekly Story EstimationDaily Standup Daily StandupSprint Review Monthly ReviewRetrospective Weekly RetrospectiveProduct Backlog Product BacklogSprint Backlog Selected Stories ColumnBurndown Trailing 4 week burnupDaily Cycle Daily CycleSprintsReleases ReleasesScrum of Scrums Stop the Line Kanban Board One piece flow WIP limits Valtivity
    40. 40.  Why bother? Bird’s eye view of Scrum Problems with multi-Scrum-team coordination Bird’s eye view of Kanban One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity
    41. 41. Multi-Stage Continuous Integration Int ProductManagement Customers Valtivity
    42. 42. Multi-Stage Continuous Integration Int Int Int ProductManagement Customers Valtivity
    43. 43. Individuals and Interactions ProductManagement Customers Valtivity
    44. 44. Agile Project Management ProductManagement Customers Valtivity
    45. 45. SCM (Version Control) Web Mobile Int DB Int Server Int ProductManagement Customers Valtivity
    46. 46. Continuous Integration Web Mobile Int DB Int Server Int ProductManagement Customers Valtivity
    47. 47. Continuous Delivery Whole product touch point after every story Working software Int after ever story is complete Scales up Int Int ProductManagement $Customers Valtivity
    48. 48. Continuous Delivery Flow continues around any problems Int Int Int ProductManagement $Customers Valtivity
    49. 49. Valtivity Learn more: http://www.Valtivity.com Agile Whole Team Training • For the whole team • $200/person or $1,000 for a group of 7 • Public sessions or on-site Hands On Agile Immersion • Free 1 ½ hour event, March 20th, Waltham, MA • Covers: Co-location, cross-functional teams, User stories, backlog, story points, planning poker, release planning, self-organizing teams Valtivity
    50. 50. Problems with Scrum Teams limited to about 10 people, then you are into hierarchy and out of agile Explicitly designed for co-located teams, and not designed for distributed teams - about 70% of all teams, and almost all large development efforts Iteration planning – deciding at the beginning what will go into the next release - is hard for teams, very hard for bigger groups Valtivity
    51. 51. Solution: Scalable AgilePrioritize at beginningNo iteration plan Plan at endNo resource constraints (release assembly) Current Work Kanban Process Pull Tasks Propose merges Contributors Release Self- On- managed demand Merge dev Test env and Individuals Assembly Agile teams Prioritized Departments Take Backlog Partners Self- On- what’s managed demand dev Test env ready Outsource Market Valtivity
    52. 52. Simple Scalable AgilePrioritize at beginningNo iteration plan Plan at endNo resource constraints (release assembly) Current Work Pull Tasks Propose merges Contributor 1 Release Merge and Contributor 2 Assembly Prioritized Backlog Contributor 3 Take what’s ready Valtivity
    53. 53. Simple Planner Valtivity
    54. 54. Simple Planner - New Column  Quickly enter tickets. Simple format collects information from a range of stakeholders.  New tickets stay in this column, where a product owner or tech lead can find them and sort them to the correct priority position Valtivity
    55. 55. Simple Planner - Backlog  Backlog is the heart of your planning process. Sort in PRIORITY order  Drag and drop  Quick “Send to top” and “Send to bottom” rollover icons  Big backlog? We’re building a backlog sorter that can handle it. Follow this link. Valtivity
    56. 56. Simple Planner – Current work with Load  Ticket count, points, and capacity at top of column  Select “Load” to move <capacity> points into current  Current work shows status and user who accepted it  Scrum iterations? Load once, complete tickets, and select “Close iteration”  Kanban? Load frequently Valtivity
    57. 57. Current shows on Cardwall… Valtivity
    58. 58. Scalable Agile: Pull code throughPrioritize at beginningNo iteration plan Plan at endNo resource constraints (release assembly) Current Work Pull Tasks Propose merges Contributor 1 Release Merge and Contributor 2 Assembly Prioritized Backlog Contributor 3 Take what’s ready Valtivity
    59. 59. Merge Request Valtivity
    60. 60. Merge Request– Contribute and Review  Person submitting a request (contributor) writes a title and description, can link to tickets  Recipient gets a review control bar  1) Get change and test  2) Vote, merge, or ignore (reject) Valtivity
    61. 61. Merge Request– Clear instructions  Open panels to get clear instructions for the Reviewer, or the Contributor.  Contributor can respond to reviews by submitting a new version Valtivity
    62. 62. Merge Request -  Request can come from a branch (Gerrit-style workflow) or a fork (Github-style workflow)  See changes in AJAX panels with file and diff views  Discussion between reviewers and contributors, with alerts Valtivity
    63. 63. Solution: Scalable AgilePrioritize at beginningNo iteration plan Plan at endNo resource constraints (release assembly) Current Work Kanban Process Pull Tasks Propose merges Contributors Release Self- On- managed demand Merge dev Test env and Individuals Assembly Agile teams Prioritized Departments Take Backlog Partners Self- On- what’s managed demand dev Test env ready Outsource Market Valtivity
    64. 64. Assembla Experience In 2011, we ran 3 week iterations, and it was getting slower. In 2012, we are doing daily releases. Each feature or fix is delivered faster Smaller releases put less stress on the team About 25 people in all roles, distributed across about 10 countries Took about 1.5 months to switch Biggest time expenditure was making complete, on- demand test environments at Amazon EC2 Valtivity
    65. 65. Questions?Damon PooleAndy Singleton www.assembla.com

    ×