In this two-day (three-day when remote) course you will gain an in-depth understanding of the role use-cases can play in the agile evolution of software systems/business solutions and, in particular, how they can help improve the backlogs, architecture and team structures that are put in place.
You will learn how to use use-case models to shape and inform your backlogs whilst ensuring the balanced evolution of your system.
You will also learn how to create and use use-case models to scope your system, improve your impact analysis, track progress, shape your architecture, manage your test assets, establish traceability, organize your teams and teams of teams/ARTs, and provide the permanent record that communicates the fixed and variable aspects of your solution.
If you are struggling to understand what your system actually does, or even what it is intended to do, because your product backlog does not provide a coherent or consistent description of the system or because you have no permanent record of what you’ve done then this is the course for you,
This course is framework neutral but is of particular relevance for anyone using Large Solution SAFe or SAFe’s Solution Intent artefact.
Students taking this course will get complimentary access (free of charge) to our Use Case 2.0 e-Learning product as a primer study-aid! Instructions will be issued prior to the course to explain which modules of the e-Learning course are most applicable in this context.
After this course, you should be able to:
- Create effective use case models to define and scope your solution
- Connect use cases to the Features and Stories on your backlog
- Ensure balance across the requirement areas of your solution
- Organize effective Feature Teams and ARTS / Scrum of Scrums
- Perform impact analysis enabling better estimation and slicing of backlog items
- Establish traceability from Requirements to Test Cases
- Identify effective end to end testcases
- Effectively manage your test assets
- Evolve and maintain an effective permanent record of what your system does and how it works
- Use use cases to communicate knowledge of current and intended solution behaviour