SCRUM Professional Scrum Master I

As needed, while taking into account a short term reduction in productivity. ✘ Never, because it reduces productivity. ✘ As needed, with no special allowance for changes in productivity. ✘ Every Sprint to promote shared learning. ✔

The Project Manager. ✘ The Product Owner. ✘ The Scrum Master. ✘ The Development Team. ✔ All of the above. ✔

During Spring Planning. ✘ Prior to starting a new Sprint. ✘ During the Sprint Retrospective. ✘ Prior to starting a new project. ✔

The Scrum Master. ✘ The Development Team. ✘ The Product Owner. ✘ The most junior member of the Team. ✔

Add the item to the current Sprint and drop an item of equal size. ✘ Add the item to the current Sprint without any adjustments. ✘ Inform the Product Owner so he/she can work with the CEO. ✘ Add the item to the next Sprint. ✔

To facilitate the Scrum Teams with insights and resources that help them improve. ✘ To monitor the Development Team's productivity. ✘ To identify and remove people that aren't working hard enough. ✘ To continually monitor staffing levels of the Development Team. ✔

Monitor communications between them and facilitate direct collaboration. ✘ Teach the Development Team to talk in terms of business needs and objectives. ✘ Teach the Product Owner about the technologies employed during the Sprints. ✘ Act as a go-between for them. ✔

Two minutes per person. ✘ 15 minutes. ✘ 15 minutes for a 4 week sprint. For shorter Sprints it is usually shorter. ✘ 4 hours. ✔ The same time of day every day. ✔

Go-between development team and customers. ✘ Value optimizer. ✘ Requirements engineer. ✘ Team manager. ✔

Short enough to keep the business risk acceptable to the Product Owner. ✘ Short enough to be able to synchronize the development work with other business events. ✘ No more than one calendar month. ✘ All of these answers are correct. ✔