The 7 product dimensions (by Ellen Gottesdiener) help to think to discover options of product and to create pieces of values.
In any context, objectives (or outcomes) are important as they give guidance or direction; instead of only focusing on solutions.
(Solutions in the broad meaning: a product or service, an improvement, a feature, a functionality, …)
Quite often, solutions are proposed or defined without an objective in mind. To reach a certain objective, multiple solutions are possible. We want to track progress with respect to objectives, not only solutions.
When teams are given an objective, teams have the possibility to think for themselves what are possible solutions, and which solutions fit the best in the current environment (system, product, service, …). In general, teams who own part of the problem statement and the solution space are more motivated, more focused, more creative, as they feel ownership.
OKRs = Objectives + Key Results
It is a method of defining and tracking objectives and their outcomes.
- Objectives are what the organization or individual want to accomplish, and are typically subjective, qualitative. Objectives can be ambitious, can be challenging.
- Key results are concrete, specific, and measurable. They describe how you will accomplish the related objective, and measure whether you accomplished the objective or not.
The clue is that Objectives Key Results can be defined on several levels in the organization: for example executive management, departments, products or services, teams.
I’ve been researching on user stories and wanted to share a list of useful resources:
- User stories and user stories examples (by Mike Cohn)
- Epics and user stories (by Roman Pichler)
- 10 Tips for Writing Good User Stories (by Roman Pichler)
- Conference video on User stories (by Mike Cohn)
- User story lifecycle (by Charles Bradley)
- User story mapping (by Jeff Patton)
- Agile Non-Functional Requirements (“Constraints”) (by Roman Pichler)
- 14 user story traps (by Charles Bradley)
- User story splitting (by Richard Lawrence)
- Splitting user stories: the hamburger method (by Gojko Adzic)
- Organizing a Large Product Backlog (by Daniel Zacarias)
- Can You Replace User Stories with Use Cases? (by Paul Raymond)
- 50 quick ideas to improve your user stories (by Gojko Adzic)
- Discover to Deliver (Ellen Gottesdiener)
- User Stories Are Placeholders for Requirements
- Writing User Stories for Back-end Systems (by Mike Cohn)
- Not Everything Needs to Be a User Story: Using FDD Features (by Mike Cohn)
- Adding Decorated User Roles to Your User Stories (by Mike Cohn)
- The purpose of User Stories in Scrum (by Christiaan Verwijs)
If you would like to suggest one to be added to list, please do so 🙂
(last update: July 2017)