Scrum Phases Flashcards

1
Q

What are Scrum Phases

A

Initiate / Plan & Estimate / Implement / Review and Retrospect / Release

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Waht processes are included in scrum “initiate” phase

A

Create product vision / Identify scrum master and stkeholder(s) / Form scrum team / Develop Epic(s) / Create prioritzed backlog / Conduct release planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What process are included in scrum “initiate” phase

A

Scrum does not have a specific phase called “initiate.” Instead, Scrum is organized into a set of defined events and roles that work together to deliver value incrementally and iteratively as it focuses on iterative development and continuous improvement. The Product Owner and stakeholders initiate the process by creating and maintaining the Product Backlog, and the Scrum Team initiates each Sprint during the Sprint Planning event. The emphasis is on delivering value incrementally and adapting to changing requirements throughout the project.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is Product Backlog

A

Product Backlog: A prioritized list of all the work that needs to be done on the project. It includes user stories, features, bugs, and other items. The Product Owner is responsible for maintaining and prioritizing the Product Backlog.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is Sprint Planning

A

An event that occurs at the beginning of each Sprint. During this meeting, the Scrum Team selects a set of items from the Product Backlog to work on during the Sprint. The team also defines the Sprint Goal and creates a Sprint Backlog, which is a list of tasks needed to complete the selected items.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What is a Sprint

A

A time-boxed period (usually 2-4 weeks) during which the Scrum Team works to complete the items from the Sprint Backlog. The team holds daily Scrum meetings to synchronize their work and identify any obstacles or impediments.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What is a Daily Scrum

A

Daily Scrum, also known as the Daily Standup, is a short daily meeting where the Scrum Team members discuss what they did yesterday, what they plan to do today, and any obstacles they are facing. The goal is to keep everyone informed and aligned.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What is a Sprint Review

A

At the end of each Sprint, the Scrum Team holds a Sprint Review to demonstrate the completed work to stakeholders and gather feedback. The Product Owner updates the Product Backlog based on this feedback.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What is Sprint Retrospective

A

The Sprint Retrospective is a meeting held at the end of each Sprint to reflect on the team’s performance and identify areas for improvement. The team discusses what went well and what could be done differently in the next Sprint.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is a Scrum Master

A

The Scrum Master is a role responsible for ensuring that the Scrum process is followed correctly, removing impediments, and facilitating communication within the team. The Scrum Master also helps the team continuously improve.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is a Product Owner

A

The Product Owner represents the interests of the stakeholders and is responsible for defining and prioritizing the Product Backlog. They work closely with the team to ensure that the highest-priority items are delivered.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a Scrum Team

A

The Scrum Team is a cross-functional group of individuals responsible for delivering the product. They collaborate to complete the work selected for the Sprint and are self-organizing.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Waht processes are included in scrum “plan and estimate” phase

A

Create user stories by product owner, including user acceptence critiera/ Estimate user stories by the team / Commit user stories, product owner add user story to sprint and development team commit to development / Identify tasks, list is created / Estimate Tasks, create effort estimate list / Creat Sprint backlog

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are included in Sprint Planning event

A

A crucial meeting for the Scrum Team determines what work they will commit to completing during the upcoming Sprint. All roles are involved. To do includes:
Preparation:
2. Selecting Sprint Goal:
3. Reviewing the Product Backlog:
4. Clarifying User Stories and Acceptance Criteria: (Most Important: Product Owner can ask questions to ensure the team fully understand the goal)
5. Estimating and Committing:
6. Creating a Sprint Backlog:
7. Time-Boxed:
8. Collaboration:
9. Commitment:
10. Record:

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What Scrum Master do for Sprint Planning event

A

Facilitate the Sprint Planning meeting and ensures that it stays within the time-box.
Ensure documentation the outcome of the Sprint Planning meeting ( can be taken bt “Scribe” or “Secretary”)
- The selected Product Backlog items
- The Sprint Goal
- The Sprint Backlog tasks.
7. Time-Boxed:
- Sprint Planning is time-boxed.
- A one-month Sprint: 4-8 hrs.
- 2 weeks Sprint: 2-4 hrs.
- 1 week Sprint: 1-2 hrs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What product Owner do for Sprint Planning event

A

A crucial meeting for the Scrum Team determines what work they will commit to completing during the upcoming Sprint. All roles are involved. To do includes:
1 Preparation:
- The Product Owner: Ensure the Product Backlog is up to date and well-prioritized.
2. Selecting Sprint Goal:
- Product Owner: Communicates the product’s overall vision and the business goals for the Sprint.
3. Reviewing the Product Backlog:
- Product Owner:
- Presents the top-priority items from the Product Backlog to the Development Team.
- These items should have sufficient detail for the team to understand what’s required.
4. Clarifying User Stories and Acceptance Criteria: (Most Important: Product Owner can ask questions to ensure the team fully understand the goal)
6. Creating a Sprint Backlog:
8. Collaboration:
- Product Owner + Development Team
- Ensure that the team understands what needs to be done and that the selected work aligns with the Sprint Goal.
10. Record:
- Product Owner + Scrum Master: Document the outcome of the Sprint Planning meeting
- The selected Product Backlog items
- The Sprint Goal
- The Sprint Backlog tasks.

17
Q

What Development Team do for Sprint Planning event

A
  1. Selecting Sprint Goal:
    • Development Team:
      • Collaboratively defines a clear Sprint Goal
      • that describes what the team intends to achieve during the Sprint.
      • The Sprint Goal should be a concise statement of what value will be delivered.
  2. Clarifying User Stories and Acceptance Criteria: (Most Important: Product Owner can ask questions to ensure the team fully understand the goal)
    • Development Team:
      • Discusses the selected Product Backlog items with the Product Owner
      • Asking questions and seeking clarification as needed.
      • Collaborate with the Product Owner to refine user stories and acceptance criteria
      • Ensuring a shared understanding of what needs to be done.
  3. Estimating and Committing:
    • Development Team: Estimates the effort required to complete the selected Product Backlog items with story points or hours.
    • Development Team: Decides how many items they can realistically commit to completing during the Sprint.
      • This commitment forms the Sprint Backlog, which is the list of tasks or sub-tasks of the item to be done.
  4. Creating a Sprint Backlog:
    • Development Team:
      • Breaks down the selected Backlog items into smaller, manageable tasks and adds them to the Sprint Backlog.
      • The Sprint Backlog may also include other considerations, such as testing, design, and technical debt.
  5. Collaboration:
    • Product Owner + Development Team
      • Ensure that the team understands what needs to be done and that the selected work aligns with the Sprint Goal.
  6. Commitment:
    • Development Team should have a clear understanding of what they will work on during the Sprint, and they make a commitment to achieving the Sprint Goal.
18
Q

Waht processes are included in scrum “implement” phase

A

Create deliverables, using scrum board to imediment log for reviewing / Conduct Daily Standup, / Groom prioritized product backlog

19
Q

Waht processes are included in scrum “Review and retrospect” phase

A

Demonstrate and validate sprint
- Scrum team + the Scrum Master demonstrate the deliverables to the product owner + stakeholder in the Sprint review meeting, aiming to get the approval and
acceptance from the product owner for the deliverable in that particular sprint. The they can close the user stories.

Retrospect Sprint
- the Scrum master + the Scrum team will meet to discuss what was the lessons learned through the sprint. What were the objectives achieved? what’s the refelction on current work. what actionable improvement can be done? Waht influence factors in the sprint? what project managemnt office or scrum body can help? Aim to improve future sprint and results.

20
Q

Waht processes are included in scrum “Release” phase

A

Ship deliverables
- Deliver product
- Document the delivery with successful completion
Retrospect project
- Scrum team + stakeholders
- review results, leasson learm, documentation
-share knowledge