Agile Project Management


Published on

Created Fall 2010 for graduate Curriculum & Instruction course at ISU.

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Agile Project Management

  1. 1. 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: 21, 2010 Agile Project Development 2
  2. 2. Key Concepts Individual Characteristics Organizational Characteristics 0 Promotes cross-functionality 0 Aligns development with customer 0 Encourages transparency needs & company goals 0 Emphasizes personal 0 Short iterations followed by accountability acceptance testing by customer 0 Rewards teamwork 0 Leadership philosophy 0 Allows team members to choose 0 Best  utilized  in  ‘Learning’   tasks to work on OrganizationsSeptember 21, 2010 Agile Project Development 3
  3. 3. General PhilosophyValues These Principles over These Principles Individuals and interactions 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
  4. 4. Roles & Functions Role Function Product Owner Leader Communicator/Point-of-Contact Visionary Customer Scrum Master Protector/Gatekeeper Recorder/Communicator Facilitator Trainer/Coach Scrum Team Manager Problem Solver/Designer Visionary MentorSeptember 21, 2010 Agile Project Development 5
  5. 5. Process Flowchart SprintProduct Product Daily Stand-Up Sprint Planning Meeting Vision Backlog Meeting Review Burndown Chart Prioritization Sprint Meeting RetrospectiveSeptember 21, 2010 Agile Project Development 6
  6. 6. 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 Who Has Input:  Product Owner  Team Members  Scrum Master  CustomerProduct VisionBased  on  the  Product  Owner’s  conversations with the CustomerSeptember 21, 2010 Agile Project Development 7
  7. 7. Product BacklogPrioritized list of User Stories(customer needs andrequirements)Based on the Product Visiondeveloped by the ProductOwner with the Customer September 21, 2010 Agile Project Development 8
  8. 8. Sprint Planning MeetingTwo-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
  9. 9. Daily Stand-UpMeeting (DSM) Each Team Member will answer the following questions during the DSM:Who: Scrum Master, Scrum TeamWhat: 10-15 minute (brief) meetingWhere: Same place every dayWhen: Same time every day 1) What have you done since the lastWhy: To eliminate any/all impediments meeting? to team progress and to answer 3 questions. 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
  10. 10. Burndown ChartA graphical representation of team progress – monitors how muchwork remains in the current iteration; posted prominently in workspaceSeptember 21, 2010 Agile Project Development 11
  11. 11. Sprint Review Demonstration of functioning software to: Product Owner Users Corporate Management Stakeholders Team Members & Scrum Masters in attendanceSeptember 21, 2010 Agile Project Development 12
  12. 12. SprintRetrospectiveTeam meeting held after every iterationScrum Team reviews:  What went well  What went wrongDiscussion of any improvements forthe next iteration Led by a Neutral Third Party Result = Single Action Item September 21, 2010 Agile Project Development 13
  13. 13. 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 projectSeptember 21, 2010 Agile Project Development 14
  14. 14. Why Agile??? Structure Empowers Team Members Encourages Change & Learning Avoids rigidity of Traditional Bureaucratic Organizations Establishes an Environment Conducive to:  Communication  Cooperation  Cross-FertilizationEveryone is constantly improved making both the Process & Management better!September 21, 2010 Agile Project Development 15
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.