Is Agile Any Better? Damon Poole 2009 Scrum and Kanban Like Chocolate and Peanut Butter Damon Poole – CTO, AccuRev.

Slides:



Advertisements
Similar presentations
Quick ramp up on Agile Methods Frederic Oehl 10/16/2014.
Advertisements

© 2012 Eliassen Group. All Rights Reserved -1- Agile in a Nutshell.
A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
© 2006 Macrovision Corporation | Company Confidential Continuous Testing in an Agile Environment Nan Krull Manager, Software Quality.
Principles of Agile management of software development project 28 November 2014.
ECE44x SCRUM Overview slides adapted from Marty Stepp
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
An Introduction to Agile SCRUM Methodology
NAUG NAUG Knowledge Evening – th February 2007.
Scrum introduction XP Days Agenda Introduction The Scrum process – roles, ceremonies and artifacts Backlog management Conclusions and questions.
Scrum (software development)
Agile development By Sam Chamberlain. First a bit of history..
Presentation copyright © AccuRev, Inc. May be used with permission only. Contact for permission. Scrum &
Agile Software Development Matt Rice November 27, 2006.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Agile Survey GreenHopper 6 Demo Switch Q&A 3 June 2012 Agile Survey Scrum is still dominant > 50% 2 week sprints > 40% use story point estimates ~ 70%
If Agile had Oscars, which of its principles would qualify as “leading” vs “supporting?” David Greene BEFORE THE TALK:
Agile Methodologies for Project Management By – Komal Mehta.
Is Agile Any Better? Damon Poole 2009 Scrum and Kanban Like Chocolate and Peanut Butter Damon Poole – CTO, AccuRev.
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
Kanban “Signboard”.
© 2011 AccuRev, Inc. All Rights Reserved -1- Optimizing Your Software Process AccuRev Proprietary and Confidential Information - © 2011 Optimizing Your.
Agile Software Development What is Agile? And How are we implementing Agile?
Continuous Integration and Testing
Agile Software Development Brian Link
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
What is Scrum? Kane Mar Certified Scrum Coach and Trainer.
A Transition to Scrum Introduction Presented by Sylvain Jean, CSM © 2011 Révolution Agile. All rights reserved.
Presentation copyright © AccuRev, Inc. May be used with permission only. Contact for permission. Damon Poole – CTO, AccuRev.
Agile Development: How it Works Damon Poole. Proprietary and Confidential 2/29 08:31 Damon Poole  Founder/CTO of AccuRev, the leader in Agile SCM. 
Stephen Chief Strategy Officer Telerik
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
A Transition to Scrum The Right Ingredients Presented by Sylvain Jean, CSM © 2010 Sylvain Jean. All rights reserved. revolutionagile.ca.
Tejasvi Kumar Developer Technology Specialist | Microsoft India
Why Scrum? Kane Mar Certified Scrum Coach and Trainer.
CS3100 Software Project Management Agile Approaches.
Accelerating Agile Across the Enterprise © 2011 AccuRev, Inc. All Rights Reserved Accelerating Agile Across the Enterprise AccuRev.
Extreme Programming Based on and
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Dr. Rob Hasker. What if every project used Scrum?  Why might Scrum not be perfect for every project? Hard to get the big picture Early choices may have.
SCRUM © University of LiverpoolCOMP 319slide 1. SCRUM history In 1986, Hirotaka Takeuchi and Ikujiro Nonaka More an observation of good practise in manufacturing.
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Dr. Rob Hasker. Should every project use Scrum?  When might Scrum not be an appropriate model?  What are some of its limitations? Hard to get the big.
SCRUM. WITH ACKNOWLEDGEMENT TO MIKE COHN FROM MOUNTAIN GOAT SOFTWARE, LLC.
CS 4500: Software Development Software Process. Materials Sommmerville Chapters 1, 2 and 3 Software Cycle and Models:
Kanban Advanced Software Engineering Dr Nuha El-Khalili.
Extreme Programming מתודולוגיה לפיתוח פרויקטי תוכנה.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Presented By : Prima Business Solutions. Agile Software Development Process.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka.
About Me learn Professor 3 startups. Simplifying Agile – Delivering Value Quickly.
Agile Scrum Development Carter Jasinski. Outline ● Introduction ● Roles ● Artifacts ● Sprints ● Uses.
AGILE METHODS Curtis Cook CS 569 Spring 2003.
Embedded Systems Software Engineering
Agile Project Management
Manifesto for Agile Software Development
AGILE SCRUM METHODOLOGY
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Continuous Integration and Testing
Creating User Documentation in an Agile World
Johanna Rothman Agile Team Measurements Chapter 12
Teaching slides Chapter 1.
Agile Frameworks - Scaling Agile for the Large Enterprise
Adjective: Able to move quickly and easily. Principles and Values
Looking at XP, Scrum, Kanban or Lean
A quick intro to SCRUM and KANBAN By John Voris.
Chapter 5: New and Emerging Process Methodologies
Presentation transcript:

Is Agile Any Better? Damon Poole 2009 Scrum and Kanban Like Chocolate and Peanut Butter Damon Poole – CTO, AccuRev

Slide -2- Kanban, Lean, and Manufacturing  “Principles of Scientific Management”, Frederick Winslow Taylor, 1911  Henry Ford – Early application of “Lean” Interchangeable parts (1908) Division of labor (1908) Static assembly line (1908) Moving assembly line (1913)  Toyoda’s Automatic Loom, 1924 “Mistake Proofing”  W. Edwards Deming in Japan in 1950 Plan, do, check, act Systems thinking (“it’s the system, not the people”)  Hirotaka Takeuchi and Ikujiro Nonaka describe Scrum without calling it Scrum, 1986  Joint presentation by Schwaber and Sutherland on Scrum at OOPSLA ‘95  “Scrum was first application of Lean to software” – Jeff Sutherland

Slide -3- Agenda  Quick Review of Scrum and Agile Values  Common Problems  Introduction to One Piece Flow  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

Slide “Critical Mass” Agile Practices Continuous Integration User Stories “As a I want Unit Tests Collocation Iteration Review Refactoring Product Owner Backlog Retrospectives ? ? Daily Standup Short Iterations $$$ $ One Piece Flow

Slide -5- Agile At a Glance new reviewed IssueStoryPointsEffort Remaining StateAssignment 432User wants layout pleasing to the eye2reviewed- 420User wants example templates to choose from3reviewed- 419Admin wants zero installation5reviewed- 612Manager wants dashboard view5reviewed- 599Admin wants LDAP integration5reviewed- 831Admin wants self-serve password reset2reviewed- 692User wants automatic todo list generation2reviewed- 432User wants easy task entry1reviewed- 119User wants subscription-based notification5reviewed- 332Marketing wants fancy splash screen3reviewed- 516Admin wants 1-click license update2reviewed- 533User wants app to be ready in 3 seconds or less5reviewed- 619User wants app to work using Chrome5reviewed-

Slide -6- Agile At a Glance new reviewed todo $$$ $ Backlog (APM)

Slide -7- Agile At a Glance new reviewed todo wip coded tested done Backlog (APM) Iteration Burnup 10/2 10/4 10/9 10/11 10/1510/1710/1910/2310/ Story Points

Slide -8- Agile At a Glance new reviewed todo wip coded tested done prod 9612 as a user I want… 6921 as a user I want… 6291 as a dba I want… 2196 as an admin I… 1962 as an admin I… 1296 as a casual user I… 1269 as a dba I want… Iteration Review Retrospective Backlog (APM)

Slide -9- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, the Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

Slide -10- Common Agile Problems  Testers want to test completed stories, but need stable builds with those stories to do so.  Codebase is most stable at end of iteration, hard to get and stay stable during the iteration  Identifying which change or changes broke a build  Maintaining a build which only contains done stories  Keeping story status and the codebase in sync

Slide -11- Mini-Waterfall

Slide -12- Dev and QA Offset by an Iteration

Slide -13- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, The Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

Slide -14- Traditional Development is Like The Game of Telephone CustomersProduct Manager ArchitectDevelopersTest & Doc Customers 7 mos. SpecifyDesignCode Integrate Write tests Test Doc

Slide -15- Agile Leverages People’s Memory and Conversations Design Code Integrate Write tests Test Doc Specify CustomersTeam Customers 1 month days Developer Test & Doc

Slide -16- Iteration After Iteration SpecifyDesign Code Integrate Write tests Test Doc WIP limit of 3 stories

Slide -17- Continuous Integration SpecifyDesign Code Integrate Write tests Test Crunch Time Doc Big Bang

Slide -18- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, The Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

Slide -19- $5M per lane $11M per lane

Slide -20- “Complete” Feature Sets $ $ Architecture Highest Value Full Featured Future Proof “Complete” Traditional Development Agile Development $ $ $ $ $ $ $ $ $ $ $ $ $ $ Done as a unit Ready at the end Feedback at the end Some features every iteration Feedback every iteration Re-plan after every iteration A A A A A A A A A A A A A A A A A A $ $ $ $ $ $ $ $ $ $

Slide -21- Major Release Contents

Slide -22- Working With Dependencies

Slide -23- person days Advanced Dependency Reduction 12 28

Slide -24- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, The Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

Slide -25- Decoupling Done Iteration review Retrospective Backlog grooming Story point estimation Iteration planning

Slide -26- Decoupling Done Iteration review Retrospective Backlog grooming Story point estimation Iteration planning

Slide -27- Decoupling Done Iteration review Retrospective Backlog grooming Story point estimation Iteration planning

Slide -28- Decoupling Done Iteration review Retrospective Backlog grooming Story point estimation Iteration planning

Slide -29- Iteration Gaps

Slide -30- Iteration Gaps

Slide -31- Continuous Flow Based on Work Schedule limit or story point limit WIP limit of 3 stories or X story points done

Slide -32- Agenda  Quick Review of Scrum and Agile Values  Common Problems  One Piece Flow, The Scrum/Kanban overlap  The Simplest Thing That Could Possibly Work  Going With The Flow (aka Letting Go of Iterations)  Scaling One Piece Flow  Q&A

Slide -33- main ws Continuous Integration on Mainline Only MinutesHours Lots of small changes in the form of user stories. CI

Slide -34- A B ws Multiple Stages of Continuous Integration MinutesHours CI int CI Daily

Slide -35- A B ws Multiple Stages of Continuous Integration MinutesHours CI int CI Daily staging CI done

Slide -36- Conclusion  Many Lean and Kanban concepts and practices can be applied to Scrum Decoupling Lean thinking One piece flow WIP limits Eliminating waste

Slide -37- Resources/Q&A  Damon Poole   Free 188pg book, Do It Yourself Agile  Continuous Integration, Paul M. Duvall  The Toyota Way – Jeffrey Liker  Extreme Programming Explained - 2nd Edition, Kent Beck  Agile Software Development with Scrum, Ken Schwaber & Mike Beedle  Lean Software Development, Mary Poppendieck and Tom Poppendieck