Scrum, Kanban, and Scalable Agile

Scrum, Kanban and Scalable Agile March 13, 2012Damon PooleAndy Singleton www.assembla.com

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

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

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

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

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 One-piece-flow (aka small batch size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity

Software Development Nirvana Continuous flow of working software Team Done stories as check points $ • Fast Customers • Small increment • Maximum value Valtivity

 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

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 size) Applying Kanban basics to Scrum Moving away from iterations Synchronized Teams Valtivity

ProductManagement Customers Valtivity

Int ProductManagement Customers Valtivity

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

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

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 C I Document W Write tests D T Test Valtivity

One Piece Flow3226 – User 5 I W Twants to undo adepot operation S D C D Within an Iteration Valtivity

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

One Piece Flow W WS D C I T S D C I T D D Within an Iteration Valtivity

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

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

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

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

✔ ✔ ✔ ✔ ✔ ✔? ✔ ? ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ Done Backlog grooming ? Retrospective Story estimation Iteration Review Choose stories Valtivity

✔ ✔ ✔ ✔ ✔✔ ✔ ✔ ✔ ✔✔ ✔ ✔ ✔ ✔ ? ? Valtivity

Trailing 4 Week Burnup 4 Week Burnup 20 Story Points 15 10 5 0 Trailing 4 weeks Valtivity

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

✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔ ✔✔ ✔ ✔ ✔ ✔ ✔ ? ? Valtivity

“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

Multi-Stage Continuous Integration Int ProductManagement Customers Valtivity

Multi-Stage Continuous Integration Int Int Int ProductManagement Customers Valtivity

Individuals and Interactions ProductManagement Customers Valtivity

Agile Project Management ProductManagement Customers Valtivity

SCM (Version Control) Web Mobile Int DB Int Server Int ProductManagement Customers Valtivity

Continuous Integration Web Mobile Int DB Int Server Int ProductManagement Customers Valtivity

Continuous Delivery Whole product touch point after every story Working software Int after ever story is complete Scales up Int Int ProductManagement $Customers Valtivity

Continuous Delivery Flow continues around any problems Int Int Int ProductManagement $Customers Valtivity

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

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

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

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

Simple Planner Valtivity

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

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

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

Current shows on Cardwall… Valtivity

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

Merge Request Valtivity

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

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

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

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

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

Questions?Damon PooleAndy Singleton www.assembla.com

Scrum, Kanban, and Scalable Agile

by Assembla

Accessibility

Categories

Upload Details

Usage Rights

3 Embeds 8

Statistics

Scrum, Kanban, and Scalable Agile Presentation Transcript

http://blog.fasoulas.com	5
http://www.linkedin.com	2
http://flavors.me	1