The purposes of the Sprint Retrospective are to (select three): - ANSWER The purposes of the Sprint Retrospective are to:
"- Inspect how the last Sprint went with regards to people, relationships, process, and tools
...
The purposes of the Sprint Retrospective are to (select three): - ANSWER The purposes of the Sprint Retrospective are to:
"- Inspect how the last Sprint went with regards to people, relationships, process, and tools;"
"- Identify and order the major items that went well and potential improvements; and,"
- Create a plan for implementing improvements to the way the Scrum Team does its work.
This Scrum event supports daily inspection and adaptation - ANSWER There is only one daily event in Scrum: the Daily Scrum. The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours. This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work. The Daily Scrum is held at the same time and place each day to reduce complexity.
A Servant leadership role includes - ANSWER One of the ways that the Scrum Master, as a servant leader, protects the team is by shielding it from interruptions.
A cross-functional team in Scrum consists of what types of team members? - ANSWER The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all the competencies needed to accomplish the work without depending on others who are not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity. The Scrum Team has proven itself to be increasingly effective for all the earlier stated uses and any complex work.
The Product Owner and Scrum Master may be the part of the Development Team - ANSWER It's OK for the Product Owner and the Scrum Master to be in the Development Team
Who is responsible for managing the Product Backlog in Scrum? - ANSWER The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
The Scrum Master as a Servant Leader is in service to which of the following? - ANSWER Scrum Masters are servant leaders and coaches for an Agile Team and for an organization. They help educate the team in Scrum, Extreme Programming (XP), Kanban, and SAFe, ensuring that the agreed Agile process is being followed. They also help remove impediments and foster an environment for high-performing team dynamics, continuous flow, and relentless improvement.
The optimal size of the Development Team is: - ANSWER Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and result in smaller productivity gains. Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful. The Product Owner and the Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
How should a Product Backlog item be refined before its development begins? (choose 2 answers) - ANSWER In a way that it's clear enough for the developers. In a way that it can be "Done" in the timeboxed duration of one Sprint.
"Items at the top of the Product Backlog need to be small enough to fit into one Sprint. They also need to be clear and detailed enough; but not too detailed (e.g. not with all the tasks identified), as it would be upfront planning. Tasks are created gradually during the Sprint."
Product Backlog items require multiple expertise, and usually done by multiple developers. Therefore, they are not assigned. Tasks, however, are assigned to the individual developers, while everyone stays accountable.
Who creates the Sprint Goal? - ANSWER The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.
The Scrum Master shouldn't allow the Development Team to start developing without having the tasks identified and assigned. - ANSWER There are two problems with this statement:1. The Scrum Master doesn't manage people and cannot forbid team members from doing something and cannot order them to do certain things. S/he should always "convince" them to do the right thing by training and coaching.2. The Development Team identifies the tasks and assigns them gradually, throughout the Sprint. We don't do it upfront, at the beginning of the Sprint.
Which of the following describes the definition of "Done"? (choose 2 answers) - ANSWER "When a Product Backlog item or an Increment is described as ""Done"", everyone must understand what ""Done"" means. Although this may vary significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the definition of ""Done"" for the Scrum Team and is used to assess when work is complete on the product Increment."
The Product Owner and the Scrum Master cannot tell the Development Team how to build the product. - ANSWER The Development Team is self-organized and finds its own way instead of receiving orders.
How should developers deal with non-functional features? - ANSWER Non-functional features are usually part of the Definition of Done and should be considered for every Product Backlog item and every Increment. Sometimes, some non-functional features that address a very particular part of the software can be added as separate items in the Product Backlog.All Sprints are the same. There's no Sprint zero, hardening Sprint, release Sprint, integration Sprint, etc.
The Product Backlog is only refined during the Sprint Planning and Sprint Review. - ANSWER Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner's discretion.
Which of the following is the most important opportunity for capturing lessons learned? - ANSWER Lessons learned are always captured, but the main purpose of Sprint Retrospective is capturing and planning for lessons learned.
The purpose of the Sprint Retrospective is to:
"Inspect how the last Sprint went with regards to people, relationships, process, and tools;"
"Identify and order the major items that went well and potential improvements;"
Create a plan for implementing improvements to the way the Scrum Team does its work.
Which one of the following statements is correct when multiple Scrum teams are working on the same product? - ANSWER There's only one Product Backlog for Scrum Team. "One" project and "one" product has only "one" Product Backlog and "one" Product Owner. Otherwise, prioritization and accountability would be difficult.
Pick 3 activities that are the accountability of the Development Team - ANSWER Designing the software is part of the development and should be done by the developers. They are self-organized and make technical decisions. Estimation is the responsibility of the developers because they are the people who will develop the item. The rest is done by the Product Owner.
How should the Product Owner forecast the completion date? - ANSWER Using a trend line in the burn-down chart can help (if the team is using that chart), as well as simple or complex formulas such as the one mentioned above. But all of these are just guides for the Product Owner and s/he should consider all factors and come up with a reliable completion date forecast.
There should be a release for every Sprint. - ANSWER Every Increment should be potentially releasable, but you don't have to release it every Sprint
Who is the most important stakeholder that the Product Owner should satisfy? - ANSWER Considering the end users as the most important stakeholder helps increase value.
In their journey to deliver products of the highest business value, what factors will enable the Scrum Team to balance creativity, flexibility and productivity? Select all that apply - ANSWER There is no team leader in Scrum Team and it is impossible to reward only part of Dev Team in Scrum
How complete should the Sprint Backlog be at the end of the Sprint Planning meeting? - ANSWER "Not all tasks are identified in the Sprint Planning; just enough to show what the development team is going to do in the next few days. The rest of the tasks will be created during the Sprint."
Hardening Sprints are helpful for defect management and integration. - ANSWER There are no hardening Sprints in Scrum. All Sprints are the same and create Increments."Hardening" is done during all Sprints.
Which item is NOT an attribute of the Product Backlog? - ANSWER Each Product Backlog has a description (e.g. in the "user story" format), a business value used for ordering, and an estimate of the amount of effort.
Is Sprint Review a formal meeting? - ANSWER Sprint review is a formal event, but informal meeting
Who determines when it's time to update the Sprint Backlog during the Sprint? - ANSWER The Sprint Backlog includes the items selected from the Product Backlog and the tasks created by decomposing the items. Only the tasks are updated during the Sprint, and it's the Development Team's responsibility to do so.
Who's in the Scrum Team? (Choose multiple answers) - ANSWER The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master.
Which of the following is done in the first Sprint? - ANSWER There's no difference between the first Sprint and the next ones. The main purpose is creating Increments.
A Development Team member should own each Sprint Backlog item. - ANSWER The Development Team owns the Sprint Backlog, not separate members of the team.
The Product Owner does not have to be one person, and the role can be played by a committee. - ANSWER It's possible to have a committee responsible for product ownership, but only a representative of that committee would be called the Product Owner. There's always one Product Owner for a product, even if there are multiple teams.
The Product Owner wants to be informed of the progress in the middle of the Sprint. How can she or he get this option? (select all that apply) - ANSWER No one should not report to the Product Owner the status of the Sprint. So, if the Product Owner wants to know to be informed about the Sprint works, he or she should at least attend the Daily Scrum or check the task board
How are stakeholders external to the Scrum team involved in the Daily Scrum? - ANSWER The Daily Scrum is only for the Development Team. Others can attend, but they won't participate.
The Development Team is free to change its engineering practices whenever they want. - ANSWER "The Development Team is self-organized and cross-functional; they have to decide how best to handle their development, and this decision can evolve during the project, as more is learned about the needs.This is about their development and doesn't have to be constrained by the Sprints. The elements that shouldn't be changed during the Sprint are those required for keeping them focused on their development."
How can the size of items on the Sprint Backlog be compared to the average size of Product Backlog items? - ANSWER Often (In most cases) Product Backlog Items are split and get smaller over time before they reach the Sprint Backlog. Due to this, in general Sprint Backlog items are smaller than Product Backlog items.
"However, a Sprint Backlog Item can be seen as a Product Backlog Item plus a plan for implementing it. In that sense it is additive to, and thus ""larger"" than, the selected Product Backlog Items."
But, as we think the first case is related to PSM 1 exam.
When forming multiple Scrum teams, which two of the following are the most important considerations? - ANSWER All teams should be cross-functional, with optimal size 3 to 9 members. Also, it is very important for teams to avoid dependencies on each other as much as it possible.
What is the best description of the job of a Product Owner? - ANSWER All items are less or more applicable, but remember that the main responsibility of the Product Owner is to maximize value, and "working with stakeholders to identify the most important requirements" is the closest answer to "increasing value".
What are some consequences if a Development does not have a consistent Definition of Done from Sprint to Sprint? - ANSWER All answers are correct
The Product Owner actively asks for stakeholder input into the Product Backlog However, a Product Owner is the only person who is responsible for Product Backlog he - ANSWER she actively asks for stakeholder input into the Product Backlog
Which of the following are optional in Scrum? (choose 2 answers) - ANSWER Velocity calculations and the use of burn-down charts are common and recommended, but not mandatory. The rest are Scrum artifacts. All Scrum roles, events, and artifacts are mandatory.
Non-functional requirements must be captured in Definition of Done - ANSWER It Is a good practice but this is not mandatory. Non-functional features are usually part of the Definition of Done, and should be considered for every Product Backlog item and every Increment.
Product Backlog Items should always be expressed as User Stories - ANSWER User Stories are very popular in Scrum, but they are not mandatory
Which list below includes the attributes of a good User Story - ANSWER "A good user story should be INVEST: - ""I""ndependent (of all others)- ""N""egotiable (not a specific contract for features)- ""V""aluable (or vertical)- ""E""stimable (to a good approximation)- ""S""mall (so as to fit within an iteration)- ""T""estable (in principle, even if there isn't a test for it yet)"
The Product Owner can delegate the ordering of the Product Backlog to the Development Team - ANSWER The Product Owner can delegate the ordering of the Product Backlog to the Development Team, however, the Product Owner remains accountable.
Which statement is not true about the Scrum? " - ANSWER A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. If a product exists, its Product Backlog also exists. Due to this requirements cannot be static"
Which of the following is not a prioritisation technique? - ANSWER Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used to estimate effort or relative size of development goals in software development. In planning poker, members of the group make estimates by placing numbered cards face-down on the table, instead of saying them aloud. The cards are revealed, and the estimates are then discussed. By hiding the figures in this way, the group can avoid the cognitive bias of anchoring, where the first number spoken aloud sets a precedent for subsequent estimates. Planning Poker is not a prioritisation technique
Software dependencies can influence how the Product Owner orders Product Backlog items - ANSWER "Software dependencies may really influence PBI ordering. It doesn't mean the Product Owner must always order the PBI by referring to software dependencies, but the question is ""can"" instead of ""must"". Maybe it is not very good practice but it is up to the Product Owner to decide if this factor is important for ordering the items or not. So it can be one of the reasons to re-order the item. This is one of many so-called ""confusing"" questions in the real exam."
Development team members sign up to own Product backlog items at the Sprint Planning - ANSWER The only one owner of the Product Backlog (include Product Backlog items) is the Product Owner
A new task to complete the Sprint Goal is identified after the Sprint Planning. When will this task be added to the Sprint Backlog? - ANSWER The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum. The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.
How complete should Sprint Backlog be at the end of the Sprint Planning meeting? - ANSWER "Sprint Backlog should be complete enough to ensure there is work for the first 1-2 days of the Sprint at the end of the Sprint Planning meeting. Not all tasks are identified in the Sprint Planning; just enough to show what the development team is going to do in the next few days. The rest of the tasks will be created during the Sprint."
Scrum ensures the exception of technical debt - ANSWER Scrum cannot ensure the exception of technical debt.
What is a Product Backlog? - ANSWER "The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. A Product Backlog is never complete. The earliest development of it lays out the initially known and best-understood requirements. The Product Backlog evolves as the product and the environment in which it will be used evolves. The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful. If a product exists, its Product Backlog also exists."
In Scrum, the Product Owner is accountable for ..... - ANSWER The Product Owner is
[Show More]
