You need the best of all worlds. You want granular small simple requirements that you can bite off sprint-by-sprint, but you also need to be able to capture complex details requiring rigor when you need to. Something that communicates and leaves a permanent requirements record, (for life beyond the development cycle) and that can handle the rigour needed when lives depend on your software. You need to turn on to Use Cases.
Need an agile requirements approach that can provide rigor where needed?
Do you need a better requirements solution?
- You need an easy and intuitive way to capture and organise requirements that is visual and obvious to your stakeholders. But it needs also to support the development teams desire for granular requirements, such as user stories, that can be developed iteratively.
- You also need an easy and intuitive way to specify the desired user experience, separating the responsibilities between the system and its users.
- You can’t leave the detail to chance, right? You need to capture it in a way that will allow those who need it to get to it quickly and easily.
Ok, so you probably agree that a requirements technique:
- that has an efficient and elegant way to describe complex requirements
- and that naturally and seamlessly integrates with other aspects of your endeavors, such as architecture, design, coding and testing
…is critical for the success of your product development
Then Use Cases are for you because…
- A place for everything and everything in its place! This rings totally true for use cases. Basic Flow, Alternative flows, Glossary Terms, Business Rules… Our approach provides an all-inclusive way to efficiently describe everything that is needed.
- People communicate using stories. Our Use Case approach promotes the creation of thin “stories” or slices through the use cases that stakeholders can relate to and that developers and testers can systematically work with.
- Use cases have a clever way to describe alternate behaviour and optionality. At this point, if this happens then what? The complexity often builds when certain conditions occur. Use cases expose these “gotchas” in an elegant and simple way.
- Testing slice by slice leads to reduced risk. Our use case approach describes a clear relationship between requirements and tests. This makes it easier to achieve test coverage, de-risking development for all stakeholders. In fact use cases are the hub of software development, acting as a catalyst for all aspects of an endeavor: UX, Architecture, Design and Coding etc.