Agile Product Management: ( Box set ) Kanban: The Kanban guide, 2nd Edition & Product Backlog 21 Tips To Capture and Manage Requirements with Scrum (scrum ... development, agile software development) by Paul VII

Author:Paul VII [VII, Paul]
Language: eng
Format: epub
Publisher: Pashun Consulting Ltd.
Published: 2017-01-12T08:00:00+00:00

The product attributes helps the team come up with a set of all possible solutions. Coming up with detailed balanced product attributes is a joint effort. As such, everyone should participate in the process. This is especially so because under-specifying attributes leads to a lack of guidance and direction while over-specifying product attributes leads to making decisions way too early and impeding the team’s creativity. Features can be described using; use case, personas and scenarios, and user stories (which i recommend).

Ideally, the items on a product backlog should be expressed with regard to the value it gives to the user (customer or business). Functional requirements are expressed as features while non functional requirements are put, for example, like this “The product needs to be faster by x minutes” or “We need to ensure the product is more secure in the following manor”.

All Generic operational qualities can often be captured as what is known asconstraint stories; visually describe the product or user interface design, for example, in form of mock-ups, sketches and screen shots. These aren’t features as such, but, they’re valid product backlog items.

The best way you can express features on the agile product backlog is in form of user stories. An example of a user stories would be “As a shopper, I want to review the items in my shopping cart before checking out so that I can see what I’ve already chosen.”(More about user stories later).

The fact that the bug describes something different a user wants, similar to a new feature, it’s also included in the scrum backlog. Technical work and research activities are also placed in the scrum backlog. For instance, technical work would be “upgrade all developers’ working stations to windows”. As for Knowledge acquisition, it could appear in the product backlog as an item about researching different types of JavaScript libraries and choosing the best.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.