Seminar 02 of PM Training 2025

What are Epics?

• Daily 15-minute meetings held every day during a sprint

• A large body of work that is broken into multiple stories

• The smallest unit of work, either representing a feature, or part of a feature to be implemented

• They are what stories are made up of

What should NOT happen in a sprint planning meeting?

• Sprint backlog is created from product backlog

• Dev team provides estimates for issues in the sprint backlog

• The team discusses potential improvements to their scrum process

• All team members participate, including the scrum master and product owner

• Sprint goals are defined

Which one of these tasks are NOT the responsibility of the scrum master?

• Ensuring the team has the daily scrum meeting

• Ensuring that there are no blockers on team members

• Monitoring the progress of the sprint

• Can help the product owner groom the backlog

• Acts as a supervisor of the development team

What happens if the Sprint time-box expires and the Sprint Goal is not reached?

• The Developers need to explain to the Product Owner what they did wrong.

• The next Sprint will have a longer time-box that allows for the Sprint Goal to be reached.

• The Sprint ends as planned with the Sprint Review and the Sprint Retrospective.

• The Sprint continues until the Sprint Goal is reached.

• A new Sprint begins with the Sprint Planning meeting.

One of the Developers on the Scrum Team has identified an issue with one of the items in the Sprint Backlog. When is the best time to clarify the requirements with the Product Owner?

• As soon as possible.

• During the next Product Backlog refinement activity.

• This is decided by the Scrum Master and only after an impediment has been raised and documented in the project management software.

• During the next Daily Scrum. 

During the Daily Scrum, one of the questions Developers must address is what they've accomplished in the past 24 hours

• FALSE

• TRUE

The Developers have been demonstrating completed features to the Product Owner throughout the Sprint. Is this an acceptable practice?

• Yes, but only if the Stakeholders are involved. 

• No. The Developers need to wait for Sprint Review for any demos. 

• Yes, as it encourages quick feedback. 

Scrum is founded on ...

• Intuition

• Empiricism

• Lean thinking.

• Agile best practices.

Which of the following statements are true about commitment in Scrum?

• The Scrum Team collaborates and finds solutions to reach the Sprint Goal by the end of the Sprint.

• The Definition of Done is a commitment for the Sprint Backlog.

• The Scrum Team is committed to supporting each other.

• The Product Goal is a commitment to the Product Backlog.

• Each Scrum artifact contains a commitment.

Some key Stakeholders have more important meetings to attend and have made a habit of not attending the Sprint Review. Under which circumstances is this acceptable?

• When the Product Owner collaborates with the Stakeholders after the Sprint Review and keeps them informed of the progress made. 

• There is no reason for the Stakeholders not to attend.

• When the Scrum Master organizes an additional Sprint Review at a different time, that works for the absent Stakeholders.

• When the absent Stakeholders collaborate with the Scrum Team during the Sprint to provide feedback.