Agile Scrum training

Click here to load reader

  • date post

    10-May-2015
  • Category

    Technology

  • view

    495
  • download

    1

Embed Size (px)

description

this is my experience in Agile Scrum and materials collected over a period of time from various experts, credits goes to all who has directly and indirectly contributed

Transcript of Agile Scrum training

  • 1.Agile Scrum Training From M Jagannathun

2. 2 2010, Cognizant Technology Solutions. | Confidential Intro to Agile Development using Scrum 3. What??? 3 4. Why Scrum 4 5. Agile Manifesto 5 6. 6 7. 7 8. Iterative Vs Scrum 8 9. 9 10. What is SCRUM? The Power of Teamwork Referred to as the Rugby Approach". Actively Used in SW Industry since late 1990s Perfect Fit to Facilitate Business Agility Enables the Project to Change its Requirements According to Changing Needs 11. Agile - Scrum 12. Scrum - Key Concepts / Benefits Team Perspective Technical Perspective High Velocity (Sprint) Quality Deliverables Impediment Removal Focus Backlogs Pull Method Burn Down Feedback - Empowers/Motivates 13. Iterative Development Cycles CLARITY TIME RELEASES (4-6 MONTHS) SPRINTS (1 MONTH) SCRUMS (1 DAY) 14. The Scrum Cycle Backlog Planning Sprint Planning Sprint Execution Sprint Scrum Sprint Review Sprint Retrospective 15. Scrum Development Process 4-6 Sprints per Release 4 weeks 16. Backlogs: Product and Sprint Product Backlog User Stories (Scenarios) Fulfills Objectives of Product (Customer) Priority Based on Value Requires Planning Sprint Backlog Pull items from Product Backlog Breakdown of work packages Fulfill Objectives of the Sprint (Product) Requires Planning 17. Backward Compatibility Sprint Burndown Chart 18. Product Demo and Retrospective #1) Product Demo and Review w/ Product Owner plus other interested parties #2) Sprint Retrospective (Lessons Learned) 19. Scrum Master Retrospective Leading and Facilitating the team to be adaptive and improving effectiveness each daily stand up (Scrum) meeting Coach and protect team to keep focused on sprint tasks and effectively burning the tasks down Adding creative solutions or facilitate the team toward creative solutions Be more of an individual contributor to the success of the team Reporting on what I have done to progress the burn down not just remove obstacles (PIG, not Chicken) Facilitating the team to be adaptive and improving effectiveness each Sprint Facilitate the planning with the team to assure that the plan is effective and produces the highest value and quality deliverables 20. Keys to Successful Sprint Test Driven Development (Acceptance Criteria) Planning is an ongoing activity Leading progress not monitoring Embrace change - Adapt Testing Early and Frequently Front Load High Value Reduce Risk Early and Remove Risk Over Time Quality of Estimates Improve Predictability Impediments Removed Quickly Highly Motivated Teamwork (Sprint Beans) 21. Retrospective Team had good vision of who does what and when Planning was not as effective as could Specifics to tasks was not available Objectives for the sprint should apply directly to Data Storage Make sure technical domain expert is available to answer questions during planning (or else during early analysis in sprint. Customer must supply what the use case and acceptance criteria More effective Plan Clear objectives and technical detail for each use/technical case Estimates need to include unit test development and documentation Time allocated for Integration (Scrum of Scrum) 22. Functional Deliverables Current Team Status - Test Coverage - Burn-down Velocity - Morale - Open Issues / Defects Status of Projects - Burn-Down - Impediments Process Improvements - Planning - Execution - Adaptation 23. SCRUM An overview Full-Time Product Owner (with Expertise and Authority) Identified Product Owner Works With Team and All Other Stakeholders Product Backlog Created and Managed by Product Owner Daily Scrum Meeting with 3 Questions (Completed? Will Complete? Obstacles? Daily Scrum Meeting Same Place and Time and Less Than 15 Minutes Regular Sprint Length (no more than 30 days) Sprint Planning Meeting to Create Sprint Backlog of Estimated Tasks Sprint Burn-down Chart Team Room with All Needed Equipment and Supplies Retrospective Meeting for Process Improvements Definition of "Done Commitment Velocity Calculated (from Sprint Backlog Estimates) Team Size 7 +/-2, Maximum of 12 Cross-Functional Team Including Scrum-Master and Product Owner Team Self-Organization - Team Members Volunteer for Tasks Scrum-Master Tracking and Removing Obstacles Team Safety - No Interruptions to Team's Work During Sprints No "Break" Between Sprints Sustainable Pace - Timebox Effort, Not Just Schedule Quality is Not Negotiable - Defects Go on Top of Product Backlog 23 24. Scrum Roles The Product Owner Defines the features of the product, decides on release date and content Is responsible for the profitability of the product (ROI) Prioritizes features according to market value Can change features and priority every 30 days Accepts or rejects work results The Scrum Master Ensures that the team is fully functional and productive Enables close cooperation across all roles and functions and removes barriers Shields the team from external interferences Ensures that the process is followed. Invites to daily scrum, iteration review and planning meetings The Team Cross-functional, seven plus/minus two members Selects the iteration goal and specifies work results Has the right to do everything within the boundaries of the project guidelines to reach the iteration goal Organizes itself and its work Demos work results to the Product Owner 25. What is Scrum ? Scrum is commitment-oriented: Youll be introduced to chickens later. Scrum is results-oriented: projects produce increments of a shippable product, activities are time boxed, and ceremony is discouraged. Scrum is disciplined. There are practices you must follow on a specified time table. 26. Scrum Artifacts The Product Backlog Derived from Business Plan or Vision Statement, which sometimes have to be created with customer List of functionality, technology, issues Issues are placeholders that are later defined as work Product Owner responsible for priority Maintained and posted visibly The Sprint Backlog Tasks to turn product backlog into working product functionality Tasks are estimated in hours, usually 1-16 Tasks with more than 16 hours are broken down later Team members sign up for tasks, they arent assigned (be patient, just wait!) Estimated work remaining is updated daily Any team member can add, delete or change the Sprint Backlog (theirs or new) Work for the Sprint emerges The Sprint Burn-down Chart The Product Increment 27. Scrum Artifacts (Contd) The Sprint Burn down Chart To create a burn down chart, each day the Scrum Master records the estimated remaining work for the Sprint and records it on a chart Start at day zero, the day of the Sprint planning meeting End at the day of the Sprint review 0.0 200.0 400.0 600.0 800.0 1000.0 1200.0 1400.0 1600.0 1800.0 2000.0 2200.0 2400.0 2600.0 2800.0 3000.0 3200.0 3400.0 3600.0 3800.0 4000.0 4200.0 Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15 Day 16 Day 17 Day 18 Day 19 Day 20 Day 21 Day 22 Day 23 Day 24 Day 25 Day 26 Day 27 Day 28 Day 29 Day 30 Day 31 Days EstimatedRemainingHours Actual Planned Sep 25 2006 Oct 03 2006 Actual hours:2646 Estimated hours:2517 Deviation:129 Deviation: + Sample Sprint Burndown Chart 28. Daily SCRUM Daily 15 minute status meeting; Same place and time every day; Chickens and pigs; (Pigs are Scrum team members committed to the sprint, Chickens are members who are involved but not committed to the sprint Three questions; What have you done since last meeting? What will you do before next meeting? What is in your way? Impediments; and Decisions 29. 29