Fifty Quick Ideas To Improve Your User Stories

value of an IT system is mostly in the outputs it produces, and that the inputs are just means to an end. Instead of thinking about workflows linearly, think about the outputs first.

you must have it, postpone the sign-off until after story discussions. Get each story signed off as you discuss it.

User stories imply a completely different model: requirements by collaboration. Hand-overs are replaced by frequent involvement and discussions.

Practices For Scaling Lean and Agile, Craig Larman and Bas Vodde

If the discussion about extremes leads to a dead end, then there is no shared understanding among the stakeholders about the potential value. This often means that things are too uncertain. In such cases, the next step should really be about reducing that uncertainty. Instead of deciding on the entire budget, plan incrementally. First decide on a budget for learning: this can lead to prototypes, low-fi interface testing with users, half-manual processes and skeleton applications, or even business people going back to the drawing bo

about extremes, for example ‘What is the least amount of money this has to earn to make any reasonable impact? How much would make everyone say that this was worth it?’ This often helps to open a useful discussion.

superhero who deals with all interruptions while the rest of the team focuses on customer-centric work. Introducing this role and rotating it to prevent burnout to any single individual was a huge boost to productivity in many teams we worked with over the last few years, mainly because the other team members didn’t have to switch context or deal with interruptions.
Don’t create two separate backlogs for external and internal items.

Ideally, learning stories should be tackled by cross-functional delivery teams who will later implement the conclusions, not by separate groups. This avoids the need to create documentation, hand work over or transfer knowledge.

Learning stories help stakeholders plan better. Earning stories help to deliver value to end-users.

Empathy: figuring out how to solve a real problem in a way that people will pay for
Stickiness: building the right product to keep users around
Virality: growing the user base organically and artificially
Revenue: establishing a sustainable, scalable business model with the right margins in a healthy ecosystem
Scale: growing the business