AIoT Product Viewpoint: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
Image:2.2-v-ProductViewpoint.png|800px|frameless|center|AIoT Product Viewpoint | Image:2.2-v-ProductViewpoint.png|800px|frameless|center|AIoT Product Viewpoint | ||
rect | rect 698 59 2421 430 [[AIoT_Business_Viewpoint|Business Viewpoint]] | ||
rect | rect 702 485 2425 859 [[AIoT_Usage_Viewpoint|Usage Viewpoint]] | ||
rect 702 911 2433 1281 [[AIoT_Data_and_Functional_Viewpoint|Data/Functional Viewpoint]] | |||
rect | rect 706 1337 2440 1715 [[AIoT_Implementation_Viewpoint|Implementation Viewpoint]] | ||
rect | rect 2468 55 3122 1711 [[AIoT_Product_Viewpoint|Product Viewpoint]] | ||
rect 4 1581 296 1743 [[Product_Architecture|Product Architecture]] | |||
rect | |||
rect | |||
desc none | desc none | ||
Revision as of 16:43, 6 June 2021
Product Viewpoint
The Product Viewpoint must map the other elements of the Product Architecture to the key elements of an agile product organization.
Story Map
A story map is organizing user stories in a logical way, in order to present the big picture of the product. Story maps help ensuring that user stories are well balanced, covering all important aspects of the planned solution in a similar level of detail. Story maps provide a two-dimensional graphical visualization of the Product Backlog.
Backlog
The Scrum page in Wikipedia defines the product backlog as a breakdown of work to be done and contains an ordered list of product requirements that a scrum team maintains for a product. Common formats include user stories and use cases. The requirements define features, bug fixes, non-functional requirements, etc.—whatever must be done to deliver a viable product. The product owner prioritizes product backlog items (PBIs) based on considerations such as risk, business value, dependencies, size, and date needed.
The most common way for a Scrum team to express features on the agile product backlog is in the form of user stories. User stories are short and concise descriptions of the desired functionality told from perspective of the user. User stories are often expressed in a simple sentence, e.g. as follows:
As a [persona], I [want to], [so that].
The 'persona' tells us who this feature is built for. The 'I [want to]' describes what the persona is trying to achieve (independent of the specific implementation). The '[ so that]' describes how the feature is fitting into the bigger picture.
Many modern development support tools such as Jira support automatic visualization of the product backlog with user stories as a story map.