INVEST guidelines for good user story
Last updated: January 03, 2023 Read in fullscreen view
Recommended for you
- 01 Aug 2024
The Standish Group report 83.9% of IT projects partially or completely fail 431/2194 - 13 Apr 2024 Lessons on Teamwork and Leadership from Chinese story book "Journey to the West" 103/1145
- 02 Nov 2021 What is Terms of Reference (ToR)? 69/1618
- 21 May 2022 "Fail Fast, Fail Often, Fail Forward" is the answer to Agile practices of software success 61/1081
- 10 Apr 2022 Agile self-organizing teams: What are they? How do they work? 60/561
- 03 Apr 2022 Microsoft Solutions Framework (MSF) 54/1340
- 27 Oct 2020 8 principles of Agile Testing 44/1339
- 03 Jul 2022 Manifesto for Agile Software Development 40/302
- 01 Jun 2022 How Your Agile Development Team is Just Like a Football Team? 38/255
- 02 May 2022 What Is RAID in Project Management? (With Pros and Cons) 34/854
- 16 Jul 2022 What are disadvantages of Agile Methodology? How to mitigate the disadvantages ? 32/407
- 28 Nov 2023 Scrum Team Failure — Scrum Anti-Patterns Taxonomy 31/281
- 20 Nov 2022 Agile working method in software and football 31/370
- 12 Aug 2022 What is End-to-end project management? 30/482
- 03 Jan 2023 Organizing your agile teams? Think about M.A.T (Mastery, Autonomy, Purpose) 29/408
- 07 Jul 2022 Managing Project Execution Terms 29/434
- 18 Dec 2023 The Cone of Uncertainty in Scrum & Requirement Definition 29/731
- 12 Oct 2020 The Agile Manifesto - Principle #8 28/513
- 23 Jun 2024 Best Practices for Managing Project Escalations 26/227
- 10 Apr 2024 The Parking Lot Method: Unlocking a Simple Secret to Supercharge Your Productivity 26/510
- 05 Jun 2023 Fractional, Part-Time (virtual) or Interim CTO: Who Will Cover Your Business Needs? 24/160
- 26 Sep 2024 Successful Project Management Techniques You Need to Look Out For 24/414
- 01 Dec 2022 Difference between Set-based development and Point-based development 23/370
- 18 Oct 2021 Key Elements to Ramping Up a Large Team 23/1239
- 13 Jan 2020 Quiz: Test your understanding project cost management 22/635
- 09 May 2022 Build one to throw away vs Second-system effect: What are differences? 21/331
- 22 May 2022 What are common mistakes that new or inexperienced managers make? 21/298
- 20 Jul 2022 Software Myths and Realities 21/928
- 24 Nov 2023 The project management paradox: Achieving MORE by doing LESS 21/238
- 17 Oct 2021 Does Fast Tracking increase project cost? 21/387
- 09 Oct 2022 Key Advantages and Disadvantages of Agile Methodology 21/720
- 07 Oct 2020 How To Manage Expectations at Work (and Why It's Important) 20/315
- 07 Dec 2023 12 project management myths to avoid 20/207
- 02 Nov 2022 Difference between Change Management and Project Management 20/246
- 14 Jun 2022 Example and Excel template of a RACI chart in Software Development 20/849
- 18 Feb 2026 "Hit and Run" Project Management: Balancing Speed with Sustainability 20/33
- 06 Jun 2022 Change Management at the Project Level 19/321
- 01 Mar 2022 Why Does Scrum Fail in Large Companies? 19/278
- 27 Jan 2020 Should a project manager push developers to work more hours due to mistakes of manager schedule setting? 18/446
- 02 Nov 2022 Frequently Asked Questions about Agile and Scrum 18/411
- 02 Dec 2021 3 Ways to Avoid Scope Creep in IT Consulting 18/223
- 30 Nov 2023 Project Managers, Focus on Outcomes — Not Deliverables 17/175
- 01 Aug 2022 Is planning "set it and forget it" or "set it and check it"? 16/294
- 10 Oct 2022 Should Your Business Go Agile? (Infographic) 15/138
- 21 Oct 2022 Virtual meeting - How does TIGO save cost, reduce complexity and improve quality by remote communication? 14/198
- 01 Mar 2024 10 Project Management Myths 14/158
- 02 Jun 2024 Reviving Ancient Wisdom: The Spiritual Side of Project Management 12/245
- 15 May 2022 20 Common Mistakes Made by New or Inexperienced Project Managers 10/291
- 10 May 2022 Levels of Teamwork 9/202
- 21 Jun 2024 Dead Horses and the Escalation of Commitment 8/145
The INVEST criteria spell out how to create Agile user stories that deliver valuable working software early and often. They show you how to specify your requirements in ways that follow the principles and values of Agile.
The INVEST mnemonic is designed to make it easy to remember what effective Agile user stories look like. With that in mind, we’ve put together a short, simple description of each of the criteria and an explanation of why it matters.
You’ll also get examples of user stories that do and don’t meet the INVEST criteria, find out how the criteria fit with the definition of ready and learn about the origins of the criteria.
Note: If you’re working on a non-software project, just replace the phrase “working software” with “working solutions”.
Under the INVEST criteria, good user stories are:
- Independent
- Negotiable
- Valuable
- Estimable
- Small
- Testable
Independent
The story is not dependent on other stories getting done.
Why it matters: Dependencies cause delays. You don’t get user-ready working software until both or all dependent stories are complete.
Negotiable
The story prompts but doesn’t prescribe a solution.
Why it matters: Treating the story as an evolving conversation between product owner and development team builds a shared understanding and harnesses everyone’s expertise: the product owner knows the benefits you’ll bring the users and the development team knows the best way to do this. And accepting that the story may change lets you adjust what you deliver as you learn more.
Valuable
The story makes clear the benefit it delivers the users.
Why it matters: In Agile, your goal is to deliver valuable working software. So your user stories need to explicitly state the value they’ll bring. What user needs does it meet, what risks does it mitigate, what costs does it save, what learnings does it allow? How does the story help you achieve your vision for the product?
Estimable
The story gives the development team enough detail to estimate the size of the story.
Why it matters: You need to know the size of the stories so you can plan an iteration that will deliver working software. Plus, product owners need to know the size so they can prioritise the stories that give the most value for the least effort.
Small
The story is the smallest piece of work that will deliver useful software.
Why it matters: Agile works in short iterations so you can get fast feedback from your users. If you want to deliver working software each iteration, short iterations necessarily require small stories. The smaller the story, the more likely it will be delivering value by iteration’s end.
Testable
The story is clear enough that you can assess if the story is done.
Why it matters: If there isn’t a Yes or No answer to the question, “Have each of the acceptance criteria been met?” then developers can’t write automated tests and the product owner can’t check the story when it’s up for acceptance.
Explore more on these topics
Guest Blogging: The Definitive Guide
Top Trending Topics
Share This
Link copied!
Recently Updated News