Agile and Agile Mindset PRINCE2-AGILE-FOUNDATION-V2 Practice Questions (Page 6)

Questions 26–30

1. 26foundation · easy

   A team uses Scrum ceremonies and tools but does not embrace collaboration or flexibility. This is an example of:

   • ABoth being and doing agile
   • BBeing agile without doing agile
   • CDoing agile without being agile
   • DNeither being nor doing agile
   Reveal Solution Discussion Select an answer first
2. 27foundation · easy

   Which of the following best defines an agile mindset?

   • AA set of attitudes and behaviors that embrace flexibility, collaboration, and continuous improvement
   • BA collection of specific tools and software used to manage projects
   • CA focus on individual performance over team collaboration
   • DA fixed set of rules that must be followed exactly
   Reveal Solution Discussion Select an answer first
4. 28foundation · easy

   What is the key difference between 'being agile' and 'doing agile'?

   • ABeing agile means using agile tools; doing agile means having an agile mindset
   • BBeing agile is only for individuals; doing agile is only for teams
   • CBeing agile is about following a fixed process; doing agile is about adapting
   • DBeing agile refers to the mindset and culture; doing agile refers to using agile practices and tools
   Reveal Solution Discussion Select an answer first
5. 29foundation · easy

   Which of the following is a key characteristic of an agile mindset?

   • AIndifference
   • BRigidity
   • CSecrecy
   • DOpenness
   Reveal Solution Discussion Select an answer first
6. 30expert · hard

   A company is developing a new online banking feature. The product owner wants to release a Minimum Viable Product (MVP) after the first sprint to get early feedback. The development team is concerned that the MVP will not include critical security features and will damage customer trust. The project manager must balance the need for early feedback with the need for a secure product. What is the most appropriate action?

   • ARelease the MVP as planned, since the definition of an MVP is to be the smallest thing that can be released.
   • BRelease the MVP to a small group of internal testers only, not to the public.
   • CDelay the MVP release until all security features are complete, even if it takes several more sprints.
   • DDefine the MVP to include the essential security features required for a viable and safe release, and defer non-essential features to later iterations.
   Reveal Solution Discussion Select an answer first