User Stories with INVEST and Agreement-Based Planning

Understanding User Stories and Their Origin
User stories, originally introduced by Ward Cunningham, aim to foster meaningful conversations between developers and customers. Cunningham’s use of “story” emphasizes dialogue over technical tasks, laying the foundation for Agreement-Based Planning, as detailed in Exploring Scrum: The Fundamentals. Reaching consensus on what “done” means is key to ensuring a shared understanding and a clear finish line for the work.

Who Invented: As a <> I want <> so that <>
The “As a <user>, I want <desire> so that <outcome>.” format for user stories was popularized by Rachel Davies in 2002 and later popularized by Mike Cohn and many others in the Scrum Community. This structure emphasizes the need to articulate who wants something, what they want, and why they want it, helping to ensure clarity and focus in defining user stories​ — aka voice of the customer.

INVEST: A Structured Approach
The INVEST acronym offers a structured way to enhance Agreement-Based Planning. “User” in “User Story” emphasizes intent and interaction, much like “use cases,” and both terms relate to functional decomposition—breaking down system interactions. A User Story is essentially a user journey toward a goal. The goal is to split work into manageable pieces, transforming complexity into simpler, agreed-upon tasks, using team discussions to talk through the INVEST criteria.

Anthropological Perspective On Stories
In this book, Harari explores the concept that storytelling is a unique human superpower. He proposes that the ability to create, share, and believe in stories has allowed humans to shape and change the world around them. Stories have the power to inspire belief and drive collective action, enabling societies to work toward making imagined futures a reality.

---

The Role of User Stories in Agile Development

User stories bridge the gap between the development team and stakeholders. They shape software design and implementation. However, creating clear, well-structured, and actionable user stories can be challenging. This is where INVEST comes in—a model to craft better user stories. Below, we’ll explore each of the INVEST criteria.

---

The INVEST Criteria Explained

• I – Independent: Each story stands alone, allowing the team to avoid dependency issues and prioritize effectively.
• N – Negotiable: Flexibility is vital. User stories should be open to discussion and change, helping the team and stakeholders collaborate and adapt to new requirements.
• V – Valuable: A user story must deliver value to the end-user. It should align with their needs and the team’s goals, ensuring the development of impactful features.
• E – Estimable: Each story should be clear enough for the team to estimate effort and complexity accurately. This transparency helps in planning and avoiding unexpected issues.
• S – Small: Keep stories concise, with a single objective. Smaller stories are easier to understand, implement, and track.
• T – Testable: Ensure user stories are testable, with clear criteria for validation. This reduces defects and improves product quality.

---

Applying INVEST to User Stories

By applying the INVEST criteria, teams can create user stories that are actionable, clear, and aligned with user needs. This method not only enhances communication but also minimizes risks, increasing the likelihood of successful project outcomes. Whether starting a new project or refining an ongoing one, INVEST serves as a valuable guideline to craft impactful user stories.

Conclusion: INVEST and Agreement-Based Planning

The INVEST criteria for user stories are a practical way to achieve Agreement-Based Planning in agile development. Agreement-Based Planning is a collaborative approach where the team and Product Owner come together to agree on the goals and deliverables of a sprint. It emphasizes negotiating stories based on their “doneness” rather than their size, which allows for a more realistic and adaptable approach to planning. This method focuses on reducing inventory, maximizing flexibility, and improving communication within the team by basing agreements on the most current information available.

By applying INVEST within Agreement-Based Planning, you encourage clear, testable, and valuable stories that drive the development process forward effectively. This approach strengthens the connection between planning and execution, ensuring that work aligns with the team’s capacity and the Product Owner’s priorities, all while keeping the focus on delivering valuable outcomes to stakeholders.

For further insights into how dialogue can shape the future of Scrum teams, check out our article on The Future of Dialogic-Driven Understanding on Scrum Teams: A 5-Year Outlook.

References:

• Cohn, Mike. User Stories Applied: For Agile Software Development. Addison-Wesley Professional, 2004.
  • A foundational book that dives into user stories, how they work, and how they can be applied effectively in an agile environment. Cohn’s work is instrumental in understanding the role of user stories and the INVEST criteria.
• Beck, Kent, and Cynthia Andres. Extreme Programming Explained: Embrace Change. Addison-Wesley Professional, 2004.
  • This book explores the core principles of Extreme Programming (XP), which closely ties into user stories and practices such as collaborative discussions and iteration, supporting the idea of using stories to drive development.
• Fowler, Martin. “Use Cases and User Stories.” (martinfowler.com, 2020)
  • A concise discussion on the relationship and differences between use cases and user stories, helping clarify their origins and purpose in software development.
• Cunningham, Ward. “A Conversation with Ward Cunningham.” (IEEE Software, 2001)
  • An interview with Ward Cunningham where he discusses the origins of user stories, providing context on why he coined the term and how it facilitates collaboration.
• Larman, Craig. Agile and Iterative Development: A Manager’s Guide. Addison-Wesley, 2003.
  • Larman’s book gives a broader look at agile methodologies, including user stories and iterative planning, aligning with concepts like Agreement-Based Planning.
• Leffingwell, Dean. Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Addison-Wesley, 2011.
  • This text explores how user stories are used across different levels.
• Rawsthorne, D., & Shimp, D. (2011). Exploring Scrum: The Fundamentals Book.
  • Agreement-Based Planning, building consensus around “done,” and structuring team collaboration effectively within agile methodologies.
• Harari, Yuval Noah. Unstoppable Us: How Humans Took Over the World.
  • This book discusses the power of stories from an anthological perspective.

Provides a practical overview of user stories in a Scrum context, including tips on how to use the INVEST criteria effectively.

SAW: Writing Stories and Agreement-Based Planning

For organizations seeking to refine their approach to value delivery and build a strong, adaptive backlog. This 1-day, on-site event is tailored to your company’s specific needs. It’s an applied 1-day tailored session aimed at helping teams tackle real-world challenges.