AgileWoW - Agile Ways of Working

1. What is the primary purpose of Product Discovery?

Delivering product quickly. Understanding and validating user needs. Increasing product revenue immediately. Enhancing internal team efficiency.

2. Who is responsible for product discovery in an Agile organization?

Product Manager alone UX team alone Development team alone The entire team

3. Why do teams validate product ideas?

To justify budget usage. To reduce the risk of building unwanted products. To showcase team efficiency. To meet regulatory requirements.

4. What does a validated hypothesis tell you?

Exactly how users will always behave. The product will be profitable immediately. Your assumption is likely correct based on gathered evidence. The hypothesis is permanently valid.

5. What's the most appropriate first step when initiating product discovery?

Developing a high-fidelity prototype Launching a full-scale survey immediately Identifying and clearly stating customer problems Presenting a polished roadmap to stakeholders

6. Which of these best describes a "business problem"?

Technical issues reported by QA Internal disagreements among teams A measurable gap between expected and actual business outcomes Market competition between organizations

7. What tool helps align product strategy to user outcomes?

Technical architecture diagrams Project management plans Impact mapping Software development frameworks

8. Which practice helps ensure you're solving the right problems?

Extensive backlog refinement Continuous customer interviews and validation Automated testing Team velocity tracking

9. User outcomes primarily relate to:

Internal efficiencies Financial profit Company branding Specific goals or benefits experienced by users

10. What’s an effective technique for understanding customer problems?

A/B testing immediately Conducting open-ended user interviews Beta testing with unvetted users Technology infrastructure reviews

11. A good hypothesis must be:

Lengthy and detailed Specific, testable, and measurable Broad and flexible Solely based on team intuition

12. The main goal of hypothesis-driven development is:

To deliver quickly to market To validate assumptions with minimal risk To increase engineering speed To simplify the team's tasks

13. When should you discard a hypothesis?

When experiment data consistently invalidates it After initial team disagreements When the CEO suggests a new idea Once it's implemented in code

14. The Truth Curve helps you determine:

The fastest delivery route to market The appropriate level of investment versus evidence collected Team productivity metrics Long-term strategic business goals

15. Which method is best for early low-cost validation?

Full-feature MVP High-fidelity prototype Customer interviews Long-term beta testing

16. How do you prioritize experiments?

Start with high-value, high-risk hypotheses Randomly select experiments Always pick the lowest cost experiments Follow team preferences only

17. Wizard of Oz MVP is best defined as:

A fully automated product A large-scale beta launch Manually simulating automated functionality Comprehensive user manuals for products

18. Concierge MVP is primarily used to:

Test scalability instantly Automate customer service immediately Offer personalized service to validate user needs Provide technical support to early adopters only

19. What is a "Fake Door Test"?

Building a complete product rapidly Creating an interface element to measure user interest without the actual functionality Running extensive usability tests Comprehensive market launch with ads

20. The primary advantage of data-driven decision-making is:

Faster feature coding Team performance optimization Reduced uncertainty and improved outcomes Increased marketing opportunities

Product Discovery Knowledge Check