What are two good ways for a Scrum Team to ensure security concerns are satisfied? (Choose two.)
According to the Scrum Guide1, the definition of ''Done'' is a formal description of the state of the Increment when it meets the quality measures required for the product. The definition guides the Development Team in creating a ''Done'' Increment. The definition of ''Done'' is created by the development organization (or Development Team if none is available from the development organization). The definition of ''Done'' may vary significantly per Scrum Team, depending on the context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of ''Done'' over time. Therefore, one good way for a Scrum Team to ensure security concerns are satisfied is to add security concerns to the definition of ''Done''. Another good way is to have the Scrum Team create Product Backlog items for each concern, as they are responsible for managing and refining the Product Backlog.
One of the Scrum events is the Daily Scrum. What are two intended outcomes of the Daily Scrum? (Choose two.)
According to the Scrum Guide, two intended outcomes of the Daily Scrum are a shared understanding of the most important work to be undertaken next to achieve the best possible progress toward the Sprint goal, and new impediments for the Scrum Master to take care of. The other options are not intended outcomes of the Daily Scrum, as they are either irrelevant (such as updating a Scrum board) or inappropriate (such as providing an update or a status report).
(Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder has just started using the product. The stakeholder is unhappy with the quality of the product, and the Product Owner agrees with the stakeholder's assessment that the quality is low. How should the Scrum Master respond to the Product Owner?
Choose the best two answers.)
The best answers are B and C because the Scrum Master serves both the Product Owner and the Scrum Team by helping address quality concerns in a constructive, transparent, and Scrum-consistent way. Quality in Scrum is not handled outside the team or delegated only to testers. When a stakeholder raises a concern about low quality, the issue should be made visible and addressed through the Product Backlog, the Definition of Done, and direct collaboration within the Scrum Team.
Option B is correct because quality expectations and stakeholder concerns should be reflected in Product Backlog items when appropriate, and the Developers need to understand those concerns clearly. Option C is also correct because the Scrum Master helps the Product Owner find an effective way to work with the Developers and address the issue empirically.
Option A is incorrect because acceptable quality standards are not solely for Developers to decide in isolation. Option D is incorrect because Scrum does not create a separate tester role responsible for quality. Option E is too passive and delayed. A significant quality concern should be addressed promptly, not simply postponed to the Sprint Retrospective.
What happens if the Development Team cannot complete its work by the end of the Sprint?
If the Development Team cannot complete its work by the end of the Sprint, then the Sprint length holds and the Development Team continuously learns what is actually possible to do within a Sprint of this length, as stated in [7]: ''If a Development Team determines it has overcommitted itself for a Sprint, one option is to collaborate with the Product Owner to negotiate removing or reducing scope. Another option is to simply work hard and do its best, without cutting quality or pressuring individuals. In either case, the Development Team learns from its experience and uses this learning when planning future Sprints.''
When is a Sprint over?
The correct answer is D, because the Scrum Guide states that ''a Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.'' Therefore, a Sprint is over when its time-box expires, regardless of whether all Product Backlog items or tasks are completed or not.
Sharon Thompson
12 days agoAdam Rogers
17 days agoTimothy Garcia
1 month agoEdward Morris
2 months agoHarold Gonzalez
2 months agoBrenda Rogers
1 month agoRebecca Martin
1 month agoRyan Roberts
1 month agoAmanda Stewart
2 months agoRuthann
2 months agoTeri
3 months agoAnthony
3 months agoSabra
3 months agoChristiane
3 months agoYolando
4 months agoLindy
4 months agoUna
4 months agoTawna
4 months agoRosendo
5 months agoLuann
5 months agoNovella
5 months agoHana
5 months agoLeatha
6 months agoSantos
6 months agoAja
6 months agoViola
6 months agoNoelia
7 months agoCandida
7 months agoShannon
7 months agoDottie
7 months agoJacob
8 months agoFelton
8 months agoHuey
8 months agoMi
8 months agoBrandon
9 months agoAshanti
9 months agoEun
9 months agoMarkus
9 months agoRebbecca
9 months agoAlida
12 months agoMargot
1 year agoGlendora
1 year agoTyisha
1 year agoReita
1 year agoKanisha
1 year agoRosalia
1 year agoFernanda
1 year agoPatria
1 year agoLauran
1 year agoClaribel
1 year agoJanessa
1 year agoLing
1 year agoDorothy
1 year agoJoseph
1 year agoMerrilee
2 years agoDolores
2 years agoLou
2 years agoVerdell
2 years agoLouvenia
2 years agoBulah
2 years agoLonna
2 years agoBenedict
2 years agoAndrew
2 years agoTamar
2 years agoArlette
2 years agoBen
2 years agoLoren
2 years agoPearlene
2 years agoLorriane
2 years agoNicolette
2 years agoLatricia
2 years agoAleshia
2 years agoAlecia
2 years agoChristiane
2 years agoFrancesco
2 years agoJamal
2 years agoMarge
2 years agoJennie
2 years ago