Please enable JavaScript.
Coggle requires JavaScript to display documents.
Scrum (2. Scrum Events (2.2 Sprint Planning (Output:
Sprint Backlog
…
Scrum
2. Scrum Events
2.1 Sprint
-
-
Composition of the Development Team and the quality expectations should no changed during the sprint
Product Owner can cancel the sprint when the Sprint Goal becomes obsolete, due to changes in the Product Backlog, strategies, approach, market, etc.
-
2.2 Sprint Planning
-
-
Input:
- Product Backlog
- Development team capacity
- Last Increment
- Past performance
Output:
- Sprint Backlog
- Sprint Goal :
Sprint Backlog:
- The items selected from the Product Backlog, and
- The tasks (work/scope) created by decomposing those items
Task can change (emerge) --> Sprint Backlog can change
A detailed plan for turning the selected items into “Done” Increment of the product and to realize the Sprint Goal (they evolve during the Sprint)
Activities:
- Define "What" should be delivered --> Sprint Backlog
- Define "How" to deliver the items into a “Done” product Increment --> Tasks
Sprint Goal:an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment.
2.3 Daily Scrum
-
-
Answer 3 questions:
- What has been accomplished since the last meeting
- What will be done before the next meeting?
- What obstacles are in the way?
If there is Scrum of Scrums:
- What dependencies will your team have with other teams?
2.4 Sprint Review
-
Purpose:
- Development team present the "Done" items to collect feedback and raise change requests
- Product Owner discusses the status of the Product Backlog and the likely completion date based on the progress
- whole Scrum Team collaborates on revising the Product Backlog based on the output of the Sprint and the feedback received from the customer
-
2.5 Sprint Retrospective
-
Purpose: process improvement
Inspect/review the sprint to adapt/improve the process
With regards to people, relationships, processes, and tools, and identify ways of improving them in the next Sprint.
-
-
-
3. Artifacts
3.3 Increment
-
The set of all the Product Backlog items completed so far in the project (up to the end of a certain Sprint)
-
Scrum of Scrums: each team release a "Done" increment which is merged into a whole project increment
3.1 Product Backlog
-
All items are described in simple business language (non-technical) and all of them are presentable to every stakeholder.
-
-
-
3.2 Sprint Backlog
Selected items from the Product Backlog to be delivered through a Sprint, along with the tasks for delivering the items and realizing the Sprint Goal
-
-
-
Extra Concepts
Definition of “Done”
-
Contains:
Development processes (e.g. programming, testing, documenting)
Non-functional features (e.g. security, maintainability, scalability)
-
-
Based on organization level.
Otherwise Development Team will define
Discussed, reviewed and agreed by whole Scrum Team
-
-
Velocity
-
-
Usage:
- Helping the developers decide how much work we can pick for the next Sprint
- Helping the Product Owner forecast how many Sprints it takes to develop the
remaining items in the Product Backlog
-
- A product that is capable of being
produced incrementally and iteratively
-
-
-
-
-