User Stories are the lifeblood of product and software development, and form the base unit of work for an Agile process. Hackernoon writes about them here., and Roman Pichler provides a nicely written 10 tips guide.
Vendor Tools – Identify Business Goals as Use Cases
Vendor tools can assist greatly with the process. For example Visual Paradigm offers this introductory article – How to Write Effective Use Cases.
- Creation of stories as UML use cases
- Storyboard and team collaboration
- Easily produce a report detailing their Technical Requirements
Business Architecture User Stories
The core ideal of Agile Business Architecture is one of ‘Business Architecture User Stories‘, meaning the use of the central feature of Agile practices: User Stories, with an additional factor of expanding these stories with additional information specific to Business Architecture.
This blends Agile User Stories with Business Architecture “fragments”, additional elements of data relevant to business transformation goals, with the scope limited only to that story of work.
Daniel Lambert provides an excellent article exploring this approach, highlighting:
- Defines how these stories can be built from Value Stream Mapping.
- A new business process can be defined as a BA User Story such that it models all of the impacted Capabilities, and thus involve the related teams in the transformation.
- Business Architecture enables clearer requirements definition and validation, framing them based on business strategies.
- The approach avoids requirement duplications across business units and deaprtments.