Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Transcript of GPR2016
Incremental and Iterative
Responsible for maximizing ROI
Identifying product features
Responsible for the value
Helps the group to apply Scrum
Is not the manager/leader
Protects the team from outside
Coaches the team
Builds the product
Decides its velocity
7 +/- 2 people (around)
A meeting to prepare for the Sprint
Part One (1 hour per week)
Review product backlog priority
Discuss the sprint goals
Focuses on understanding what
Size of items (1/4 of sprint)
Part Two (2 hour per week)
Focuses on how to implement
Select items on top of the backlog
Team decides how much work it will complete
Complete analysis of user stories
Short meeting (15 min.)
Every workday at an appointed time
Synchronize work meeting
What has been done yesterday?
What will be done today?
What obstacles are in the way?
1 hour per week
Product: Inspect and adapt
Accept user stories
Includes the actual live software
It is not a presentation; it is a demo
If preparation takes more than 30 minutes ...
Process: Inspect and adapt
What's working well?
What's working wrong?
What to improve?
45 minutes per week
Represents everything that could be done by the team
It is prioritized
Only one by product
It evolves over the lifetime
It is the roadmap
Includes a variety of items
Dedicated to refine PBI to support future sprints
It takes no more than 10% of sprint duration
Not for actual items
List of work for the sprint
Items are decomposed of tasks
It emerges from the Sprint planning
Tasks are tracked during the sprint
It shows the estimated effort remaining