Agile requirements are a key success factor for Scrum projects. Many people criticize the minimalist format of user stories, often forgetting that they are mainly a support for a conversation and don’t have the objective to fully document requirements. In this article, Paul Raymond discusses how classical use cases can be use to expand user stories during requirements elicitation in Scrum sprints.
This presentation discusses an experience with lightweight planning for a team in a big company. At the heart of it is a kind of story map, a single-page plan of sorts. It is a simple tool for discovery and continuous planning with stakeholders, including what’s a minimum viable first version to go live with.
Written by South African Agile coaches Samantha Laing and Karen Greaves, “Coach’s Guide to Agile Requirements” is a book on how to teach the concepts of Agile requirements. It provides a complete plan to run a workshop where people can learn how to elicit, refine and organize requirements in an Agile way.
Estimates are part of our daily live. Every single day we ask and answer questions like: “when will it be done?”, “how much does it cost?” and use that “data” to plan the future of our projects. Some of us using rigorously formalised processes with heaps of Excel sheets, some applying more agile methods like planning poker. While doing that, we do not realise how estimates could be harmful!
Technical Debt is defined as the consequences of poor software architecture and software development within a codebase. Carrying too much technical debt reduce the ability of software to change and evolve. In this article, Jurgen De Smet explains how to manage technical debt from a business perspective.