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

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: http://agilemanifesto.org/
September 21, 2010 Agile Project Development 2

3. 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 Organizations
September 21, 2010 Agile Project Development 3

4. General Philosophy
Values 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

5. 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
Mentor
September 21, 2010 Agile Project Development 5

6. Process Flowchart
Sprint
Product Product Daily Stand-Up Sprint
Planning Meeting
Vision Backlog Meeting
Review
Burndown
Chart
Prioritization Sprint
Meeting 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
Who Has Input:
 Product Owner
 Team Members
 Scrum Master
 Customer
Product Vision
Based on the Product Owner’s
conversations with the 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) Each Team Member will answer the
following questions during the DSM:
Who: Scrum Master, Scrum Team
What: 10-15 minute (brief) meeting
Where: Same place every day
When: Same time every day 1) What have you done since the last
Why: 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

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