Introduction to Lean, Agile, Scrum, & XP
42 likes14,575 views
This document provides an introduction to Lean, Agile, Scrum, and XP. It defines Lean as focusing on identifying value and optimizing processes. Agile emphasizes responding quickly to change through principles like valuing individuals, working software, and customer collaboration. Scrum is a framework that uses short cycles, daily stand-ups, and product backlogs to organize complex work. XP includes practices like pair programming, test-driven development, and collective code ownership.
Introduction to Lean, Agile, Scrum, & XP
- 1. Introduction to Lean, Agile, Scrum, & XP Si Alhir [email protected] http://salhir.wordpress.com 202-596-8202 Introduction to Lean, Agile, Scrum, & XP 1 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 2. Business Enterprise (Business & Technology and Management & Teams) Market Business Enterprise Harmonize Business and Technology Foster Optimization, Responsiveness, and Competitiveness Ensure Resilience Introduction to Lean, Agile, Scrum, & XP 2 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 3. Lean: Optimization ~ Lean ~ Roots in the Toyota Production System (TPS) ("Just-in- Time") ~ "The Machine That Changed the World: The Story of Lean Production” (James Womack, Daniel Jones, Daniel Roos, 1991) ~ "Lean Thinking” (Womack, Jones, 1996) ~ "The Toyota Way” (Jeffrey Liker, 2003) ~ Purpose: Identify Value ~ Process ~ Map the Value Stream ~ Create Continuous Flow ~ Establish Level Pull ~ People: Seek Perfection Introduction to Lean, Agile, Scrum, & XP 3 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 4. Agile: Responsiveness ~ Agility ~ Roots in Energy-Maneuverability (E-M) Theory (aircraft performance, F-15 Eagle, F-16 Fighting Falcon, F/A-18 Hornet) ~ "Destruction and Creation" (John Boyd, 1976) ~ "A Discourse on Winning and Losing” (John Boyd, 1987) ~ "Certain to Win“ (Chet Richards, 2004) ~ Observe ~ Orient: Genetic heritage, Cultural traditions, New information, Previous experience, Analysis & Synthesis ~ Decide: Appreciation and Leadership ~ Act Introduction to Lean, Agile, Scrum, & XP 4 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 5. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Introduction to Lean, Agile, Scrum, & XP http://agilemanifesto.org, 2001 5 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 6. Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer The most efficient and effective method of through early and continuous delivery conveying information to and within a development of valuable software. team is face-to-face conversation. Welcome changing requirements, even late in Working software is the primary measure of progress. development. Agile processes harness change for the customer's competitive advantage. Agile processes promote sustainable development. The sponsors, developers, and users should be able Deliver working software frequently, from a to maintain a constant pace indefinitely. couple of weeks to a couple of months, with a preference to the shorter timescale. Continuous attention to technical excellence and good design enhances agility. Business people and developers must work together daily throughout the project. Simplicity--the art of maximizing the amount of work not done--is essential. Build projects around motivated individuals. Give them the environment and support they need, The best architectures, requirements, and designs and trust them to get the job done. emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Introduction to Lean, Agile, Scrum, & XP http://agilemanifesto.org/principles.html, 2001 6 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 7. Lean and Agile Business Enterprise Context Lead Governance Collaborate Marketing, Sales, Support Results Products, Lines, Execution Strategy Focus Portfolios Feedback/Iterate Projects, Programs, Balance Portfolios Engineering, Arch., Infrastructure Contribute Confirm Empower Operations Enable Support People Introduction to Lean, Agile, Scrum, & XP 7 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 8. Solutions and lifecycles ~ Solutions to Problems ~ Products composed of components ~ Services delivered by people and processes ~ Lifecycle of a Solution ~ Vision, Roadmap, and Business Case ~ Releases composed of iterations ~ Iterations composed of requirements and work Roadmap Vision Release Iterative (Features) Incremental Iteration Iteration Iteration Iteration Time-boxed (Stories) (Stories) (Stories) (Stories) Zero Work Harden Define-Detail, (Review) Initiate (Plan) Build, & Parallel Close Test Continuous (Tasks) Introduction to Lean, Agile, Scrum, & XP 8 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 9. Scrum ~ Roots ~ "The New New Product Development game" (HBR, 1986) ~ Ken Schwaber and Jeff Sutherland, 1993 ~ Framework ~ Simple team-based "inspect and adapt" framework (Empirical vs. Define) ~ Organize "complex" work (systems and products) ~ Iterative, incremental approach to optimize predictability and control risk & confront uncertainty ~ Foundation ~ Grounded in Transparency, Inspection, and Adaptation ~ Fosters Commitment-based, Self-organizing, and Cross- functional Teams ~ Scrum Teams: Roles, Time-Boxes, Artifacts, and Rules Introduction to Lean, Agile, Scrum, & XP 9 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 10. Scrum and XP Sprint Product Owner Release (Customer) Burndown Daily Scrum Impediments Meeting Product Sprint Product Backlog Backlog ScrumMaster (Coach) Overall Practices Sprint Burndown Collective Code Coding Ownership Standard Test-Driven Def-Det, Development Bld, & Team Pair Tst Programming Refactoring Simple Scrum: A simple team-based "inspect and adapt" framework Design Continuous Sustainable to organize work around "complex" systems and products. Integration Pace eXtreme Programming (XP): A discipline of software development. Metaphor http://www.scrum.org/ Introduction to Lean, Agile, Scrum, & XP http://xprogramming.com/xpmag/whatisxp/ 10 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 11. Scrum: Intent, Work, and Results ~ Product Backlog (What) ~ Collection of requirements or stories ~ Items have a Description, Priority, and Estimate ~ Emerge ~ Sprint Backlog (How) ~ Collection of tasks ~ Items have Estimate Remaining ~ Emerge ~ Product ~ Release level: Bundle of Features/Services ~ Sprint level: Slice/piece of Product (potentially shippable) Introduction to Lean, Agile, Scrum, & XP 11 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 12. Scrum: Owners ~ Product Owner ~ Maximize value of the work ~ Product Backlog: Define(Value), Prioritize, Commit ~ Product: Accept or Reject ~ Team ~ Do the work ~ Self-organize (figure out how) ~ Cross-functional (have the skills to define-detail & build & test) ~ Product Backlog: Size, Select, Commit ~ Sprint Backlog: Define and Estimate ~ Product: Realize and Demonstrate ~ Scrum Master ~ Champion the Process ~ Coach the Product Owner and Team ~ Champion removing Impediments/dysfunctions Introduction to Lean, Agile, Scrum, & XP 12 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 13. Scrum: Flow and Pull ~ Sprint (2-4 Weeks) ~ Period of time to complete a Product Increment ~ Committed Product Backlog Items are fixed (and elaborated) for the duration of the Sprint ~If Team is unable to complete all items, Product Owner decides which items to remove ~If Team can address more items, Product Owner decides which items to add ~ Team self-organizes to assign and undertake the work (sign-up for, add, and remove Sprint Backlog Items) ~ May be abnormally canceled/terminated Introduction to Lean, Agile, Scrum, & XP 13 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 14. Scrum: Flow and Pull ~ Sprint Planning Meeting ~ Segment 1 (1/2 Day) - Product Backlog Selection (What) ~ Product Owner Defines, Prioritizes (Risk, value, Necessity), and Presents Product Backlog Items ~ Team Sizes Product Backlog Items ~ Product Owner and Team establish Sprint Goal and definition of "Done" ~ Team Selects Product Backlog Items ~ Segment 2 (1/2 Day) - Sprint Backlog Planning (How) ~ Team Defines and Estimates Sprint Backlog Items ~ Product Owner and Team Refine ~ Product Owner commits to the fixed (but will-be elaborated) Product Backlog Items ~ Team commits to do best to complete Product Backlog Items ~ Consider capacity and reality Introduction to Lean, Agile, Scrum, & XP 14 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 15. Scrum: Flow and Pull ~ Sprint Review Meeting (1/2 Day) ~ Inspect the Product Increment and Adapt the Product Backlog ~ Product Owner identifies what is "Done" and "Not Done" ~ Team discusses what went well, problems encountered, and how they were solved ~ Team demonstrates the work ~ Product Owner discusses the Product Backlog ~ Sprint Retrospective Meeting (1/2 Day) ~ Inspect and Adapt the Process ~ Worked well - Continue? ~ Improve - Start or Stop? Introduction to Lean, Agile, Scrum, & XP 15 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 16. Scrum: Flow and Pull ~ Daily Scrum Meeting (15 minutes) ~ Synchronization point among Team ~ Worked on: Accomplished? ~ Will work on: Do? ~ Impediments: Obstacles? ~ Impediments ~ Burndown Charts ~ Release-level and Sprint-level ~ Velocity ~ Scrum Board ~ Information Radiator ~ Story (Size), To-Do (Estimate), In-Process (Owner), Done Introduction to Lean, Agile, Scrum, & XP 16 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 17. eXtreme Programming (XP) ~ Roles ~ Core Practices ~ Customer ~ Simple Design ~ Coach ~ Pair Programming ~ Team ~ Test-Driven Development ~ Refactoring (Design Improvement) ~ Overall Practices ~ Supporting Practices ~ Whole Team ~ Continuous Integration ~ Planning Game ~ Collective Code Ownership ~ Small Releases ~ Coding Standard ~ Customer Tests ~ Metaphor ~ Sustainable Pace Introduction to Lean, Agile, Scrum, & XP 17 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.
- 18. Thank You Si Alhir [email protected] http://salhir.wordpress.com 202-596-8202 Introduction to Lean, Agile, Scrum, & XP 18 Copyright (c) 2009 Sinan Si Alhir. All rights reserved.