Need help to define better user stories?
Check this book. Really good techniques, to help you creating stories, planning, discussing, splitting or managing delivery in iteration.
Free sample available here.
A nice overview of the key factors you should care of about to determine if your Agile implementation is successful.
This website also provide a great road-map template with clear activities articulated around 3 steps into your company journey: Introducing Agile, Developing Agile Capabilities & Continuously improving Agile.
More papers available here.
Job Stories is an alternative to User Stories. This article highlight where User Stories fail and propose an approach to implement them in team workflow. Job Stories are a different way of thinking about defining features, UI, and UX.
Project Managers will need to give up control
Product Owners will forgot product requirements documents
Developers will need to develop incremental design and architecture skills
QE engineers will move testing forward to largely overlap code development
ScrumMasters will be great leaders
The entire team takes ownership of requirements definition through testing
Dual Track Agile assume that there are two key tracks for agile product development: Discovery and Delivery.
Discovery to quickly generate validated product backlog items in collaborative sessions with engineers and designers.
Delivery to develop releasable software based on backlog items qualified and defined in Discovery Track.
You have long and frustrating sprint planning meetings? Check you backlog items! you’ll see they’re often not well defined, understood, or validated.
It is commonly estimated that between 70 to 90% of new product will fail. Working software is the primary measure of success for agile but without user adoption they provides no value!
People often assume that when something goes on the product roadmap, that the team has every intention of building and launching this.
This article explain why it’s a good idea to reposition the roadmap as the “opportunity backlog.”
The opportunity backlog is the prioritized set of opportunities for the product discovery team to explore in product discovery. The output of product discovery is the product backlog, which is the prioritized set of work (usually represented as user stories and prototypes) for the delivery team.
The opportunity backlog will help you to keep your product backlog “clean” and to focus on opportunity assessments. It is a great tool for Product Owners and UX designers.
Good article from Roman Pichler blog with whom i did my CSPO training.
This is about Scrum Master and Product owner roles, highlighting how important and complimentary they are. I liked the way expectations are clearly set and illustrate each role accountability (Product Success, Product Process).
Scrum Master is a key role for successful agile teams and require a good level of seniority to coach the team, the product owner and identify, implement necessary changes.