24.02 Agile Approach - Quiz

Check your understanding

1. What is the typical duration of an Agile sprint?

   • 1-4 weeks { data-correct }
   • 2-6 months
   • 6-12 months
   • Whatever time is needed to complete all features

2. Which ceremony occurs at the beginning of each sprint to plan the work?

   • Daily Standup
   • Sprint Review
   • Sprint Planning { data-correct }
   • Sprint Retrospective

3. What are the three standard questions asked in a Daily Standup?

   • What did I complete yesterday? What will I work on today? Any blockers? { data-correct }
   • What features are complete? What’s the timeline? Who’s responsible?
   • What went well? What went poorly? What should we improve?
   • What’s the budget? What’s the deadline? What are the risks?

4. What is the primary purpose of a Sprint Review?

   • To plan the next sprint’s work
   • To demonstrate completed work to stakeholders { data-correct }
   • To discuss team performance issues
   • To estimate effort for user stories

5. What is the correct format for a User Story?

   • As a [user type], I want [functionality], so that [benefit] { data-correct }
   • Given [context], when [action], then [outcome]
   • If [condition], then [system response], else [alternative]
   • When [trigger], the system [response], because [reason]

6. How long should a Daily Standup meeting last?

   • 5 minutes
   • 15 minutes { data-correct }
   • 30 minutes
   • 1 hour

7. What does “time-boxed” mean in the context of Agile sprints?

   • The sprint can be extended if more work is needed
   • The sprint has a fixed duration that cannot be changed { data-correct }
   • Work must be completed faster than estimated
   • Each task has a specific time limit

8. Which Agile ceremony focuses on process improvement and team reflection?

   • Sprint Planning
   • Daily Standup
   • Sprint Review
   • Sprint Retrospective { data-correct }

9. What makes a good User Story according to Agile principles?

   • It should be independent, negotiable, valuable, estimable, small, and testable { data-correct }
   • It should include detailed technical specifications
   • It should be written by the development team only
   • It should cover multiple user types in one story

10. What is the main goal of delivering a “potentially shippable increment” at the end of each sprint?

    • To reduce development costs
    • To provide working software that delivers value { data-correct }
    • To satisfy regulatory requirements
    • To keep the development team busy