AIoT Business Viewpoint: Difference between revisions
No edit summary |
|||
| Line 21: | Line 21: | ||
[[File:2.2.-bv-VacuumCanvas.png|900px|frameless|center|ACME:Vac Business Model Canvas]] | [[File:2.2.-bv-VacuumCanvas.png|900px|frameless|center|ACME:Vac Business Model Canvas]] | ||
== <span id=" | == Quantitative Planning == | ||
== KPIs == | |||
== Milestones / Timeline == | |||
== Story Map <span id="StoryMap"></span>== | |||
It is best practice in the agile community to break down a larger body of work into specific work items by using a hierarchical approach. Depending on the method applied, this hierarchy can include themes, epics, features and user stories. | It is best practice in the agile community to break down a larger body of work into specific work items by using a hierarchical approach. Depending on the method applied, this hierarchy can include themes, epics, features and user stories. | ||
| Line 33: | Line 39: | ||
When starting to break down the body of work, one should first agree on a set of top-level epics, and ensure that they are consistent, not overlapping, and covering everything that is needed. | When starting to break down the body of work, one should first agree on a set of top-level epics, and ensure that they are consistent, not overlapping, and covering everything that is needed. | ||
[[File:2.1-Example-Story-Map.png|800px|frameless|center|Example: Initial Story Map]] | [[File:2.1-Example-Story-Map.png|800px|frameless|center|Example: Initial Story Map]] | ||
Revision as of 13:36, 5 July 2021
Business Viewpoint
The Business Viewpoint of the AIoT Product/Solution Design is building on the different artifacts created for the Business Model. As part of the design process, the business model can be refined, e.g. through additional market research. In particular, the detailed design should include quantitative planning, KPIs and a milestone-based timeline. Finally, an agile story map should be created to capture the high-level requirements. This is the main interface between the Business Viewpoint and the Product Viewpoint.
Business Model
Quantitative Planning
KPIs
Milestones / Timeline
Story Map
It is best practice in the agile community to break down a larger body of work into specific work items by using a hierarchical approach. Depending on the method applied, this hierarchy can include themes, epics, features and user stories.
The AIoT Framework is assuming the following hierarchy:
- Epic: A high-level work description, usually outlining a particular usage scenario from the perspective of one of multiple personas
- Feature: A specific feature to support an epic, which is further broken down into user stories
- User Story: short requirements written from the perspective of an end user
Depending on the complexity of the project and the agile method chosen, this might have to be adapted, e.g. by further adding themes as a way of bundling epics.
When starting to break down the body of work, one should first agree on a set of top-level epics, and ensure that they are consistent, not overlapping, and covering everything that is needed.
