An Intro to Scrum. Agile (Iterative) Project Development. Written in 2001 Can be read in its entirety at:

Transcription

1

2 An Intro to Scrum Agile (Iterative) Project Development Broken down into iterations Self-Managed Minimal Planning Easily/Quickly adapts to change The Agile Manifesto Written in 2001 Can be read in its entirety at: September 21, 2010 Agile Project Development 2

3 Key Concepts Individual Characteristics 0 Promotes cross-functionality 0 Encourages transparency 0 Emphasizes personal accountability 0 Rewards teamwork 0 Allows team members to choose tasks to work on Organizational Characteristics 0 Aligns development with customer needs & company goals 0 Short iterations followed by acceptance testing by customer 0 Leadership philosophy 0 Best utilized in Learning Organizations September 21, 2010 Agile Project Development 3

4 General Philosophy Values These Principles Individuals and interactions over These Principles processes and tools Working software comprehensive documentation Customer collaboration contract negotiation Responding to change following a plan While there is value in the items on the right, in Agile, we value the items on the left more. September 21, 2010 Agile Project Development 4

5 Roles & Functions Role Product Owner Scrum Master Scrum Team Function Leader Communicator/Point-of-Contact Visionary Customer Protector/Gatekeeper Recorder/Communicator Facilitator Trainer/Coach Manager Problem Solver/Designer Visionary Mentor September 21, 2010 Agile Project Development 5

6 Process Flowchart Product Vision Product Backlog Sprint Planning Meeting Daily Stand-Up Meeting Sprint Review Burndown Chart Prioritization Meeting Sprint Retrospective September 21, 2010 Agile Project Development 6

7 Provides consideration to the Customer s concept of the product adds clarity to the Customer s vision of the product. A Customer-approved Product Vision provides the basis for a trust agreement between the Customer and the Product Owner Product Vision Based on the Product Owner s conversations with the Customer Who Has Input: Product Owner Team Members Scrum Master Customer September 21, 2010 Agile Project Development 7

8 Product Backlog Prioritized list of User Stories (customer needs and requirements) Based on the Product Vision developed by the Product Owner with the Customer September 21, 2010 Agile Project Development 8

9 Sprint Planning Meeting Two-part Process 1) Clarity of Product Vision Teams ask questions to gain clarity 2) Team Members become autonomous Break down User Stories Pull Tasks Create Burndown Chart September 21, 2010 Agile Project Development 9

10 Daily Stand-Up Meeting (DSM) Who: What: Scrum Master, Scrum Team minute (brief) meeting Where: Same place every day When: Why: Same time every day To eliminate any/all impediments to team progress and to answer 3 questions. Each Team Member will answer the following questions during the DSM: 1) What have you done since the last meeting? 2) What will you do between now and the next meeting? 3) Is there anything standing in the way of you completing your goals? September 21, 2010 Agile Project Development 10

11 Burndown Chart A graphical representation of team progress monitors how much work remains in the current iteration; posted prominently in workspace September 21, 2010 Agile Project Development 11

12 Sprint Review Demonstration of functioning software to: Product Owner Users Corporate Management Stakeholders Team Members & Scrum Masters in attendance September 21, 2010 Agile Project Development 12

13 Sprint Retrospective Team meeting held after every iteration Scrum Team reviews: What went well What went wrong Discussion of any improvements for the next iteration Led by a Neutral Third Party Result = Single Action Item September 21, 2010 Agile Project Development 13

14 Prioritization Meeting Meeting held once an iteration Includes: Product Owner Scrum Team Scrum Master Stakeholders/Customers Review/Reassess remaining Product Backlog items Result = Changes reflect reassessed priorities of project September 21, 2010 Agile Project Development 14

15 Why Agile??? Structure Empowers Team Members Encourages Change & Learning Avoids rigidity of Traditional Bureaucratic Organizations Establishes an Environment Conducive to: Communication Cooperation Cross-Fertilization Everyone is constantly improved making both the Process & Management better! September 21, 2010 Agile Project Development 15

16 Supplemental Information All material found in this presentation is under copyright 2010 by Mary Macin unless otherwise noted. Inquiries for use of this presentation can be directed to: Mary Macin 1209 Hillcrest, Normal, IL Agile Project Development: Scrums, Burndowns, & Retrospectives was originally presented at IRAUG in September 2009 Illinois Regional Agile User Group (IRAUG) meets the third Tuesday of every month Find out more by visiting them at: September 21, 2010 Agile Project Development 16