AIoT Product Viewpoint: Difference between revisions
Line 29: | Line 29: | ||
The [https://en.wikipedia.org/wiki/Scrum_(software_development)#Product_backlog 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 [https://en.wikipedia.org/wiki/Scrum_(software_development)#Product_backlog 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.'' | ||
Many modern development support tools | Many modern development support tools such as Jira support automatic visualization of the product backlog as a story map. |
Revision as of 20:42, 26 July 2020
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.
Many modern development support tools such as Jira support automatic visualization of the product backlog as a story map.