The document discusses Agile and Scrum frameworks for project management. It explains that Agile focuses on individuals, interactions, working software, customer collaboration, and responding to change. Scrum is an Agile framework that uses short "sprints" or iterations to incrementally develop a product. Key Scrum roles include the Product Owner who manages requirements, the Development Team who does the work, and the Scrum Master who facilitates the process. The document outlines Scrum meetings and processes like sprint planning, daily standups, reviews, and retrospectives.

1. Lester Burson-Thomas (Senior Business Analyst)

2. Can you cook vegetarian food without
being a vegetarian?
Being vegetarian is based on ... Cooking is based on a recipe ...

3. Customer
collaboration
over contract
negotiation
Working
software over
comprehensive
documentation
Individuals and
interactions
over processes
and tools
Responding to
change over
following a plan
Agile is a set of principlesvalues …

4. Highest valued
items are
implemented
and delivered
first.
During each
sprint team
pulls work from
a prioritized list.
Complete work
in iterations or
sprints.
At the end of
each sprint have
a shippable
product.
… Scrum is a framework for building a product

5. Ready
Team
based
Value
Driven
Scrum
In Progress
Agile
Done
Incremental
Iterative
Frequent
Delivery
Production
Ready
Fully
Visible

6. Product Owner
Team
based
As a purchaser, I can Search for generic
equivalents of name-brand items so I can
save money.
Effort: 2 hrs. IA, 6hrs Dev, 2 hrs. Test = 10 hrs.
As a purchaser, I can Search for generic
equivalents of name-brand items so I can
save money.
Effort: 2 hrs. IA, 6hrs Dev, 2 hrs. Test = 10 hrs.
As a purchaser, I can Search for generic
equivalents of name-brand items so I can
save money.
Effort: 2 hrs. IA, 6hrs Dev, 2 hrs. Test = 10 hrs.
As a purchaser, I can Search for generic
equivalents of name-brand items so I can
save money.
Effort: 2 hrs. IA, 6hrs Dev, 2 hrs. Test = 10 hrs.
As a purchaser, I can Search for generic
equivalents of name-brand items so I can
save money.
Effort: 2 hrs. IA, 6hrs Dev, 2 hrs. Test = 10 hrs.
Product Backlog Manage Product Backlog
• Catalog of all User Stories
• Assign a prioritybusiness value
• Add User Stories
• Change User Story priority
As a purchaser, I can Search for
generic equivalents of name-brand
items so I can save money.
Effort: 2 hrs. IA, 6hrs Dev, 2 hrs. Test = 10 hrs.
User Story
Simple description of a desired function
As a purchaser, I can Search for generic
equivalents of name-brand items so I can
save money.
Effort: 2 hrs. IA, 6hrs Dev, 2 hrs. Test = 10 hrs.
The team is …

7. Product Owner
Team
based
Manage Product Backlog
• Elaborates on Features
• Sets Release Dates (release may contain several iterationssprints)
• Reviews Work
• Makes sure work done has the most value
Week
1
Week
2
Week
3
Week
4
Week
5
Week
6
Week
7
Week
8
IterationSprint 1 IterationSprint 2
Release
Date
Shippable
Product

8. Team
based
Development Team
• Full time
• Empowered
• 7 ± 2 members
• Cross functional
• The “engine”
Takes highest
priority stories
from backlog

9. Team
based
Scrum Master
• Coach
• Teacher
• Protects team
• Facilitate
• Administer
Educates the team
Facilitates the
team working
together
Coaches the
team to work
together

10. Product 1
Product 2
Iteration 1
Iterative
Iteration 0
Product 0
Product 3
Iteration 2
Iteration 3

11. Why call it Scrum?
Original idea ... January 1986 product development as a cross-
team, holistic approach where the team "tries to go the
distance as a unit, passing the ball back and forth“ as they all
advance forward … like rugby. 1
1 – Harvard Business Review. January 1986 “The New New Product Development Game”
by Hirotaka Takeuchi and Ikujiro Nonaka

12. Leads to the term Scrum in 19952
.
As you advance the product forward you need to have
periodic meetings to make sure things are on course -
these are scrums.
2 – “Scrum Methodology” paper OOPSLA ‘95 Austin, Texas. 1995 Sutherland and Schwaber

13. Scrum Meetings: Sprint Planning
Team decides how much work it can do in the Sprint.

14. Scrum Meetings: Daily Scrum
Daily 15-minute meeting to clarify state of work.
ScrumMaster asks each team member …
- What did you do yesterday?
- What will you do today?
- Is anything blocking you?

15. Scrum Meetings: Sprint Review
Demo of the “product” at the end of a Sprint.
Product owner determines which items to approve
and re-prioritizes the Product Backlog.

16. * The Human Side of Agile – Gil Broza
*
Teamwork
Shared
leadership
Responsibility
Scrum Meetings:
Sprint
Retrospective -
sample

17. Ready
Team
based
Value
Driven
Scrum
In Progress
Agile
Done
Incremental
Iterative
Frequent
Delivery
Production
Ready
Fully
Visible
Self
Directed

18. Ready
Scrum
In Progress
Agile
Done
Incremental Iterative
Production
Ready
Fully
Visible
Self
Directed
Team
based
Value
Driven Frequent
Delivery