Assume that we have an approved initiative, idea, or an epic. What follows next in SAFe’ Continuous Delivery Pipeline is its first element, Continuous Exploration (CE).
Use Case Driven Analysis: CE is our opportunity to analyze and flesh out the Minimum Viable Product (MVP) as described in the approved idea’s Lean Business Case.
Features are the artifacts of CE.. together with clearer vision of the product and a roadmap of features — could be laid out across multiple Program Increments (PI) — to make the product vision a reality.
Use UCM to delimit the system: Use Case Modeling (UCM) is a tool that we can use to flesh out the MVP… and to delimit the system. As we go through CE’s research and synthesis, and envisioning, the system border is set through Use Case (feature) Modeling and allocation of responsibilities to Actors (for whom or for which persona uses which Use Case).
This process is iterative… like modeling with clay… do not attempt perfection. Look for interesting Use Cases to model … Use Cases that deliver value. This is where the fun is… your creative hat is needed… put it on! Work with collaborators… don’t do this alone. Collaborate with product management, product owners, subject matter experts (SMEs), stakeholders, system architect, development and test teams, business analyst, etc.
Use Case Modeling also means describing Use Cases… so, again, collaboration is needed.
Single Use Cases can be simulated or animated based on their description.
In fact, User Interface (UI) Design can be envisioned based on Use Cases.
Validate the system in Analysis through the Use Case Model. Are we building the system right? Will the customer needs be fulfilled? Here is how : 1) review and refine — again, iteratively– the Use Case Model; 2) envision or prototype the UI
Use Case Models are not static … they are pliable and can change according to users’ needs and market demand. Just like in Lean Ux, we have the ability to create or mold a Use Case Model, Validate, pivot or persevere.
To be continued…