Story mapping: Difference between revisions

From A Technological Wiki
Jump to navigation Jump to search
Added category manage objectives
Line 43: Line 43:
  <!-- From bodyContent 1543055.mraw -->
  <!-- From bodyContent 1543055.mraw -->


[[Category:manage objectives]]

Revision as of 18:51, 19 October 2025

When tackleling an objective it is necessary to make a good previous study

  • Have the objective clear
  • Define strategies to accomplish the objective
  • Make tactical materialization proposals

We must have a "model" for our application, in order to know which type of client are we dealing with and their main characteristics.

It is recommendable that proposal meets INVEST:

  • Independent: they can be implemented in any order
  • Negotiable: details can be discussed between all parts
  • Valuable: must provide value to the user
  • Estimable: it doesn't have an excessive complexity
  • Small: can be materialized in a short time
  • Testable: we can make tests to verify it works properly

All objectives must be measurable through KPIs.

Establish priorities

We must value the priority of the strategical and tactical proposals through ICE:

  • Impact: how much is it going to affect in the evolution of our project
  • Confidence: how confident do we have that it will be successful
  • Ease: complexity of their development

Each of them has a value of 0 to 10. Priority is obtained from the sumatory of them all. With this, we can establish a Minimum Viable Increment. The higher the value, the more a quick win it will be.

Three friends

It is referred to the 3 primary perspectives to examine before, during and after the development phase of an increment iteration.

  • Business: which new value I want to provide?
  • Development: How to build a solution for this requirement?
  • QA: given that new value, how can I test it? given that solution, what could happen?

We share an understanding of the requirement and we identify possible confusions and disagreements.