1
Q
Projects have what?
A
- A product Backlog of prioritized requirements
- Product Owner who prioritizes these requirements
2
Q
What do Scrum Processes do?
A
Address specific activities & flow of a Scrum project. In total there are 19 processes which are grouped into 5 phases.
3
Q
What does the Initiate Phase consist of?
A
- 1st Phase
1. Create Project Vision
2. Identify Scrum Master & Business Stakeholder
3. Form Scrum Team
4. Develop Epics
5. Create a prioritized Product Backlog
6. Conduct Release Planning
4
Q
Create Project Vision
A
- First Process
- Project Business case is reviewed to create project vision statement
- Product owner is identified
5
Q
Identify Scrum Master & Business Stakeholder
A
- 2nd Process
- Scrum Master Identified
6
Q
Form Scrum Team
A
- 3rd Process
- Scrum Team identified
- Product owner responsible for selecting team members
- Often does so in collaboration with Scrum Master
7
Q
Develop Epics
A
- 4th Process
- Project vision Statement Serves as the basis for developing Epic
- User Group Meeting May be held to develop Epics
8
Q
Create Prioritized Product Backlog
A
- 5th Process
- Epics refined & elaborated & prioritized to create a Prioritized Product Backlog
- Done criteria is also established
9
Q
Conduct Release Planning
A
- 6th Process
- Scrum Core Team reviews Epics in the Prioritized product Backlog to develop a Release planning schedule
- Phase deployment schedule shared with project stakeholders
10
Q
What does the Plan & Estimate Phase consist of?
A
- 2nd Phase
- Create User Stories
- Estimate User Stories
- Commit User Stories
- Identify Tasks
- Estimate Tasks
- Update Sprint Backlog
11
Q
Create User Stories
A
- 7th Process
- User Stories & their related user story acceptance criteria are created
- Written by Product Owner
- Designed to ensure the customer’s requirements are depicted & understood
- Involves Scrum team member creating the User stories
- Incorporated into Prioritized Product Backlog
12
Q
Estimate User Stories
A
- 8th Process
- Scrum Team, supported by Scrum Master estimates user stories
- Identifies effort requested to develop functionality described in each user story
13
Q
Commit User Stories
A
- 9th Process
- Scrum Team commits to deliver Product Owner approved user stories for a Sprint
- The results of the process are the committed user stories & the Sprint Backlog
14
Q
Identify Tasks
A
- 10th Process
- Committed user stories are broken down into specific tasks & compiled into a Task list
15
Q
Estimate Tasks
A
- 11th Process (optional)
- Scrum core team estimates effort required to accomplish each task in the Task list
16
Q
Update Sprint Backlog
A
- 12th Process
- Scrum core team updates the Sprint Backlog with further details about tasks as part of the Sprint planning meeting
17
Q
What does the Implement Phase consist of?
A
- 3rd Phase
- Create Deliverables
- Conduct Daily Standup
- Refine Prioritized product backlog
18
Q
Create Deliverables
A
- 13th Process
- Scrum team works on tasks in Sprint Backlog to create Sprint Deliverables
- Scrumboard is often used to trak the work & activities being carried out
- Issues or problems being faced by the Scrum team could be updated in an impedimenting
19
Q
Conduct Daily Standup
A
- 14th Process
- Everyday a highly focused, time-boxed meeting is conducted referred to as the Daily Standup meeting
- Forum for the Scrum Team to update each other on their progress & impediments
20
Q
Refine Prioritized Product Backlog
A
- 15th Process
- Prioritized product backlog is continuously updated & maintained
- Prioritized product backlog review meeting may be held
-Any changes or updates to backlog are discussed & incorporated into Prioritized Backlogs
21
Q
What does the Review & Retrospect Phase consist of?
A
- 4th Phase
- Demonstrate & Validate Sprint
- Retrospect Sprint
22
Q
Demonstrate & Validate Sprint
A
- 16th Process
- Scrum Team demonstrates Sprint Deliverables
- Purpose of this meeting is to secure approval & acceptance of the product or service by the Product Owner
23
Q
Retrospect Sprint
A
- 17th Process
- Scrum Master & Scrum Team meet to discuss the lessons learned
- Info is documented as lessons learned which can be approved to future Sprints
- There may be Agreed Actionable improvements or updated Scrum Guidance Body Recommendations
24
Q
What does the Release Phase consist of?
A
- 5th Phase
-Ship Deliverables - Retrospect Release
25
Ship Deliverables
- 18th Process
- Accepted Deliverables are delivered or transmitted to relative business stakeholders
- A formal working deliverable agreement documents successful completion of Sprint
26
Retrospect Release
-19th & Last Process
- Business stakeholders & Scrum core team mebers assemble to retrospect
- Identify, document & internalize lessons learned
- Lessons led to documentation of Agreed Actionable improvements to be implemented in future projects
