Scrum Roles Events and Artifacts Flashcards by Kelvin Waters

What are the three Scrum events?

Reviews
Planning
Retrospective

How well did you know this?

Not at all

Perfectly

What three roles are recognized in Scrum?

Scrum Master
Product Owner
Development Team

How well did you know this?

Not at all

Perfectly

What is the job of a Scrum Master?

Servant Leader
Facilitator of Development Team
Process Coach
Impediment remover

How well did you know this?

Not at all

Perfectly

What is the job of a Product Owner?

Provides vision and direction to the team

Prioritizes the requirements for team

How well did you know this?

Not at all

Perfectly

What is the job of a Development Team?

Comprises of 10 developers

Makes efforts to meet goals set by PO

How well did you know this?

Not at all

Perfectly

Scrum Master Do’s

is a servant leader who helps the team achieve success
facilitator of scrum events (sprint planning, daily stand-up)
an impediment remover (like always having to seek approvals)
is the process coach for the team

How well did you know this?

Not at all

Perfectly

Scrum Master Don’ts

not to be a figure of authority under any circumstances
should not be the task master of the team (micro manage, assign tasks, as for daily status, chase people down)
will not be a technical or design authority for the team

How well did you know this?

Not at all

Perfectly

What are some important skills and attributes of a good Scrum Master?

Collaborative, knowledgeable, humble, influential, committed, patient.

How well did you know this?

Not at all

Perfectly

What are the two roles of a Product Owner?

Vision and Boundaries

How well did you know this?

Not at all

Perfectly

Product owner creates a product vision with several inputs such as:

customers
technical team
executive
SME’s

How well did you know this?

Not at all

Perfectly

Product owner creates a product vision with several inputs such as:

Sets expectations with stakeholders for delivery milestones and roadmap
Establishes acceptance criteria

How well did you know this?

Not at all

Perfectly

To be successful, a product owner must be:

available, business savvy, excellent communicator, decisive, empowered.

How well did you know this?

Not at all

Perfectly

True or False

The PO rarely makes decisions?

False

How well did you know this?

Not at all

Perfectly

True or False

The scrum master ought to be decisive in decision making

False

How well did you know this?

Not at all

Perfectly

True or False

Neither the PO or Scrum Master should have reporting authority over the Development Team

True

How well did you know this?

Not at all

Perfectly

True or False

The PO represents the interests of stakeholders in the product

True

How well did you know this?

Not at all

Perfectly

True or False

A scrum master may have to push back against unrealistic goals set by a “pushy” PO

True

How well did you know this?

Not at all

Perfectly

True or False

Over time, the scrum master becomes less busy whereas the PO becomes busier?

True

How well did you know this?

Not at all

Perfectly

Agile teams have three distinguishing characteristics which are:

Small
Cross-functional
Self-organizing

How well did you know this?

Not at all

Perfectly

True or False

Small teams are favorable, as it is more productive

True

How well did you know this?

Not at all

Perfectly

True or False

Scrum teams adjust better to component teams.

False

How well did you know this?

Not at all

Perfectly

True or False

Component teams are NOT favored in scrum teams

True

How well did you know this?

Not at all

Perfectly

What are some advantages of feature teams over component teams?

Evaluate design decision impact
Reduces waste by hand-offs
Ensures right people are talking 
No risk to schedule
Focuses on feature delivery

How well did you know this?

Not at all

Perfectly

In a Scrum team, the project manager’s duties are taken care by different roles. What responsibilities does a PO ingest from a PM?

Road maps
Release plans
Stakeholder engagement

How well did you know this?

Not at all

Perfectly

In a Scrum team, the project manager's duties are taken care by different roles. What responsibilities does a Scrum Team ingest from a PM?

Estimation Planning Day-to-day task management

True or False The Scrum Master takes over the role of establishing the process and advising the team

True

True or False Scrum makes no distinction for the different specialist positions in the Development Team.

True Architects, UX designers, Testers are all viewed as part of the team.

Product Owners are responsible for the W**** in the delivery of each increment

What

The Development Team is responsible for the H** in the delivery of each increment

How

A sprint is synonymous with __________.

iteraction

A sprint is a _______ event between one to _____ weeks.

timebox, 4

The goal for a sprint should be a complete and releasable product. Which encompasses ________ and _______.

Development | Testing

True or False Sprint duration and deliverables should not change once it has been planned.

True

What should occur in the first day of a Sprint

Iteration Preparation

What should occur in the second day of a Sprint

Iteration Planning

What should occur in next to the last day of a Sprint

Demo Preparation

What Team event occurs at the last day of a sprint?

Retrospective

The backlog refinement (grooming) process includes:

Discovering and describing items Prioritizing the backlog Sizing the backlog items Getting ready for planning the next sprint

The steps followed in a Scrum methodology are:

Sprint Planning Daily stand-up Sprint review Sprint retrospective

Who ought to attend a Sprint Planning meeting?

Developer Product Owner Scrum Master

During Sprint Planning, whose responsible for: Underline the goals of the sprint Clarify open questions Take priority decisions

Product Owner

During Sprint Planning, whose responsible for: Facilitating the meeting

Scrum Master

During Sprint Planning, whose responsible for: Plan the sprint in as much detail as possible

Team

During Sprint Planning, what two approaches are there to determine the workload?

Velocity-Driven | Commitment-Driven

If a team doesn't have enough past data (sprints) to determine work load, what could they begin with?

Start with the commitment-driven approach: decisions based on discussions and willingness to commit.

True or False Team buy-in is important regardless of what Sprint Planning work load is decided upon.

True

_________ is a measure of the amount of work that the team can do in a given sprint or iteration.

Velocity

Steps involved in a velocity-driven approach to sprint planning are:

``` Adjust priority Determine the target velocity Identify an iteration goal Select the user stories Split the user stories Estimate tasks ```

In a commitment-driven sprint planning event, the team adds stories to the backlog _____________ aligned with a sprint goal.

one at a time

Various failure modes of sprint planning are:

``` Too aggressive or too conservative Inability to reach consensus Not considering known events Not enough preparation Search for elusive certainty ```

True or False Scrum Master must let the team justify their commitment without any influence.

True

a meeting described as: OF THE TEAM, FOR THE TEAM, and BY THE TEAM is what meeting?

Daily Scrum

Daily Scrum Meeting agenda asks?

What happened yesterday What is planned for today What issues are blocking progress

Who ought to attend the Sprint Review event?

Developers PO Scrum Master interested stakeholders

What is the only event (meeting) that individuals NOT in the Scrum team can attend?

The Sprint Review

Who should attend a Sprint Retrospective event? (1hr)

Development team | Scrum Master

The purpose of the sprint retrospective is to:

Make issue visible Come up with improvement opportunities Take ownership of the actions

True or False A Scrum master should facilitate the Spring Retrospective and make people want to attend.

True

Failure modes of Sprint Review:

``` Inadequate preparation Too many or too few external invitees Team members getting too defensive Too much discussion Discussing retrospective or next sprint planning ```

Various failure modes of sprint retrospective are:

``` Temptation to skip Fatigue of the team Tendency to point fingers Presence of external stakeholders Too much attention to negatives ```

The definition of Done answers the question ___________.

What does success look like!