AIoT Product Viewpoint: Difference between revisions
No edit summary |
|||
| Line 2: | Line 2: | ||
<imagemap> | <imagemap> | ||
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 512 23 1335 207 [[AIoT_Business_Viewpoint|AIoT Business Viewpoint]] | rect 512 23 1335 207 [[AIoT_Business_Viewpoint|AIoT Business Viewpoint]] | ||
| Line 10: | Line 8: | ||
rect 519 641 1345 818 [[AIoT_Implementation_Viewpoint|AIoT Implementation Viewpoint]] | rect 519 641 1345 818 [[AIoT_Implementation_Viewpoint|AIoT Implementation Viewpoint]] | ||
rect | rect 2 759 134 836 [[Product_Architecture|Product/Solution Architecture]] | ||
rect | rect 333 26 1156 205 [[AIoT_Business_Viewpoint|AIoT_Business_Viewpoint]] | ||
rect | rect 335 232 1160 412 [[AIoT_Usage_Viewpoint|AIoT Usage Viewpoint]] | ||
rect 337 437 1160 616 [[AIoT_Data_and_Functional_Viewpoint|AIoT Data/Functional Viewpoint]] | |||
rect 337 642 1162 821 [[AIoT_Implementation_Viewpoint|AIoT Implementation Viewpoint]] | |||
desc none | desc none | ||
Revision as of 08:55, 31 January 2021
Product Viewpoint
The Product Viewpoint must map the other elements of the Product Architecture to the key elements of an agile product organization.
Product Canvas
Roman Pichler describes the product canvas as A simple but powerful tool that helps you create a product with a great user experience and the right features. It combines Agile and UX by complementing user stories with personas, storyboards, scenarios, design sketches and other UX artifacts. It’s designed to work with Scrum, Lean Startup, and Business Model Generation. The canvas supports Lean UX by combining user centered design and agile techniques. As can be seen in the diagram below, the proposed Ignite AIoT product canvas combines elements from the previously introduced viewpoints. Depending on the complexity of the AIoT solution, the product canvas will cover the entire solution, or only selected sub-products.
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.