Scrum Master - PSM 1

What sets the minimum requirements for an Increment?

Acceptance Criteria

An adjustment must be made as soon as possible to minimize further deviation. What does this refer to?

Adaptation

What is the Sprint Retrospective?

An opportunity for the Scrum Team to inspect itself and create a plan for improvements to be carried out in the next Sprint.

What should the frequency of inspection be within the Sprint?

As frequently as decided by the team

When can a new item be added, refined, and/or prioritized in the Product Backlog?

At any time during the product's existence

When is the order of Product Backlog items decided?

At any time during the product's existence.

What are the 3 C's of user stories?

Card, Confirmation, and Conversation

The Increment must be successfully integrated and working in the main branch. This can be an item in:

Definition of Done

What is the method used by the Scrum Team to bring in shared understanding of the criteria for confirming that a Backlog item is done in all respects?

Definition of Done

The duration of a Sprint must be one month or less. What are some of the characteristics with Sprints longer than one month?

Delayed feedback and the risk of being detached from stakeholders.

Design and architecture evolve as the product is being built. Who will be working toward this?

Developers

Developers follow certain ground rules for performing and updating work within the Sprint. Who is responsible for maintaining these rules?

Developers

Who decides the format of the Daily Scrum?

Developers

In the middle of a Sprint, the team realizes that their estimates have gone wrong and they are not able to complete all the promised work in the Sprint. A decision must be taken on the selected items. Who are the mandatory participants in this discussion?

Developers and Product Owner

The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. Who is responsible for sizing Product Backlog items?

Developers size the work since they are responsible for it. Product Owners may help them understand and select trade-offs.

One week into the Sprint, a developer is facing issues with integrating his code. He finds that part of the code developed by another member does not follow the development guidelines. Who should resolve this problem?

Developers, as it is a collective responsibility.

As work progresses in the Sprint, Developers come to know that their Increment must be tested for its compatibility with the existing legacy components. Who is responsible for this?

Developers: they are responsible for producing a done, usable, & readily releasable Increment.

Who decides how to create the Increment?

Developers: they own the work within the scrum and decide how to perform it

Scrum helps reduce risk early on in software development. Which 2 Agile features are responsible for this?

Early testing and early customer feedback

TRUE/FALSE: In Scrum Projects planning is a one-time activity.

FALSE

TRUE/FALSE: The goal of any Sprint is to produce a done, shippable Increment of working software. This is non-negotiable, so the Sprint can never be cancelled.

FALSE

TRUE/FALSE: Transformation, inspection and adaptation are three pillars of empirical process control.

FALSE: 3 pillars of empirical process control are TRANSPARENCY, INSPECTION, AND ADAPTATION.

TRUE/FALSE: The start of a new Sprint can be postponed only if the Sprint Goal of the previous Sprint is not achieved.

FALSE: A new Sprint starts immediately after the previous Sprint ends. There are no exceptions.

TRUE/FALSE: A Sprint Review is recommended but not mandatory if the Increment is not getting released to production at the end of the Sprint.

FALSE: All formal events inside the Sprint (Planning, Daily Scrum, Review, and Retrospective) are opportunities to Inspect and Adapt, foregoing any one results in reduced transparency.

TRUE/FALSE: The Daily Scrum is the only way Developers track progress during the Sprint.

FALSE: At any point in the Sprint, the total work remaining in the Sprint Backlog can be summed (tracked).

TRUE/FALSE: A fully formed Sprint Backlog is one of the expected outcomes from Sprint Planning

FALSE: The Spring Backlog is a live document during the Sprint, developers update, add, or remove items in the Sprint Backlog as more knowledge becomes available.

TRUE/FALSE: The Developers own the work within the Sprint. In the Middle of the Sprint, they realize that their understanding of the work required toward the Sprint Goal was wrong. The work they have planned in the Sprint will not help achieve the Sprint Goal. They are able to make the decision to cancel the Sprint and regroup for next Sprint Panning.

FALSE: They are not authorized to take this decision - discuss with the Product Owner and decide collaboratively on future action.

TRUE/FALSE: Formal events remove the need for any other meetings in Scrum

FALSE: it may reduce the need, but not completely eliminate it.

TRUE/FALSE: A Product Backlog item is considered done when the functionality is approved by the Product Owner.

FALSE: the item can be considered done when it is potentially shippable as confirmed by the Definition of Done

TRUE/FALSE: The Product Owner is responsible for making sure that the Developers select enough number of items based on their capacity.

FALSE; Developers are responsible for selecting which items to include in a sprint as they are the ones who do the work. Product Owner can set expectations, but do not have final say here.

We are in the last week of the Sprint. Some of the stakeholders have expressed their inability to attend the Sprint Review as per the schedule. They will only be available next week. What is the best thing to do?

Go ahead with the Review in the proper sequence with available stakeholders.

Which one is not a characteristic of the development team? Self Organized, Hierarchical, Cross Functional, Continuous Improvement

Hierarchical

Which of these is NOT expected from the Sprint Planning meeting? Spring Goal, Increment, Sprint Backlog, None of these are expected

Increment; it is an end result of the Sprint

The following points to which Agile Value: "Build projects around motivated individuals, give them the environment and support they need and trust them to get the job done.

Individuals and Interaction (over process and tools)

What are the values of the Agile Manifesto?

Individuals and interactions, responding to change, and customer collaboration

TRUE/FALSE: Confirmation from the Product Owner that there are enough Backlog items ready for implementation is a precondition for beginning a new Sprint.

It's good practice, but not a precondition. A new Sprint starts immediately after the previous Sprint ends.

By only writing down what is needed to satisfy the requirements that will be worked on in the near-term, the Agile methodology attempts to do what?

Maximize the amount of work not done and respond to changes efficiently.

In Scrum, how is the Product Backlog arranged?

Most important items at top, least important items at bottom.

For how many Backlog items can a team member be personally accountable at a given point in time?

None - Individual members may choose to take up work in the area of their expertise, but accountability remains with the team

When can an item in the Product Backlog be considered for a Sprint?

Only during Sprint Planning sessions.

Which one is a scrum artifact? Sprint Planning, Daily Scrumn, Product Backlog, Sprint

Product Backlog

Who has the final say on the priority of a new Backlog item that a key stakeholder has requested?

Product Owner

What term corresponds to the definition "a duty that a person takes on or plays"?

Role

Which option is not a component of Scrum? Scrum Team, Scrum Manifesto, Scrum Events, Scrum Artifacts

Scrum Manifesto

Which Roles constitute a Scrum Team?

Scrum Team consists of the Scrum Master, the Product Owner, and the Developers.

What are the advantages of senior leadership participating in the Daily Scrum?

Senior Leadership does not participate in the Daily Scrum. The Daily Scrum is a 15min event for the Developers of the Scrum Team.

During the Daily Scrum, which artifact is used to inspect the progress toward the Sprint Goal?

Sprint Backlog

Which is not an input to the Sprint Planning? Product Backlog, Sprint Backlog, Latest product Increment, Past performance of the team

Sprint Backlog

Which event(s) should not be avoided for any reason?

Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

The Developers track total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal. Which tool can help them do this?

Sprint burndown Chart

The remaining identified effort in the Sprint against time is shown by:

Sprint burndown Chart: it shows the remaining identified effort in the Sprint against the days in the Sprint.

TRUE/FALSE: A Sprint can be cancelled.

TRUE

TRUE/FALSE: In empirical process control theory, knowledge comes from experience.

TRUE

TRUE/FALSE: The Developers can renegotiate scope with the Product Owner

TRUE

TRUE/FALSE: The Product Backlog is a prioritized document that product owner updates

TRUE

TRUE/FALSE: The Scrum Master coaches the team in keeping the events within time box

TRUE

TRUE/FALSE: The Scrum Master makes sure scrum process is implemented

TRUE

TRUE/FALSE: Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint.

TRUE: (think this happens during the Sprint Planning?)

TRUE/FALSE: Management supports the Scrum Team on their way to excel as a self-organizing, self-managed team.

TRUE: support from management is important for the success of Scrum, but they are not daily participants.

Developers are about to start working on one of the selected Product Backlog Items for the Sprint. They realize that it may have an impact on the existing components of the system. Who should analyze the impact?

The Developers, as they are doing the work. They are responsible for any aspect of a usable Increment each Sprint.

There is no Definition of Done defined in the organization. What should Scrum follow?

The Scrum Team must create a Definition of Done appropriate for the product

What is the Sprint Review?

The Sprint Review is the second to last event of the Sprint and may result in changes to the Product Backlog and/or changes to the next Sprint. So, the Sprint Review must be completed in the current Sprint.

What is the lifetime of a Product Backlog?

The same as the product

The Definition of Done will be inspected and improved as the project progresses. New items may be added to it. How will this impact the work already done in the previous Sprints?

There is an impact: it may uncover work to be done in previously done Increments.

What can the time between two Sprints be used for?

There is no gap between Sprints

What issues are in the following user story: "As a grocery buyer, I want to see different food items in different colors: red for meats, brown for grains, green for vegetables so that I can identify food items by type."

This story breaks the quality of negotiable

When should we release the Increment to Production?

When it makes sense. The Increment must be done and shippable and that will depend on many factors.

The goal of a story writing workshop is to:

Write as many user stories as possible under the themes identified.

Do we need any documentation in agile project management

YES; just enough - just in time

Is the Product Owner a participant in the Retrospective?

Yes.

What is a challenge with waterfall methods that prompted the software industry to come up with alternatives like agile?

it is difficult to predict user/customer needs