Establish a "Things That Matter" Matrix

Establish “things that matter” (TTM) matrix to help steer discussion toward complexity.

This is a simple tool to help explore the complexity of the story and so assist in properly establishing the estimates relative size. A TTM Matrix consists of a list of technologies (or any other issue such as “complex testing”) that are needed to deliver the story. The technologies are list at the top of the matrix so that there are entries for each user story. For each user story, the team fills in the box under the user story if there that technology is involved in the implementing the user story. This could be as simple as an “X” or a more complex “L, M, H” type rating.

The theory is that a user story which only has a couple of boxes filled in would be less complex to implement than one that crosses a lot of things that matter and so would warrant a higher relative estimate.

Teams today are trained to use this concept so this should be a reminder. Stabilize estimates by establishing team guidelines for size. This is a modification of the Establish Points Guidelines for Each Point Value for each point value and leads to more discussion based on the important things to consider.

Use the following URL for manually sending trackbacks:
establish_points_guidelines_for_each_point_value, 2016/06/16 09:35 (Trackback)
Establish Points Guidelines for Each Point Value The idea here is to keep some degree of consistency as you go from sprint to sprint by setting up definitions for each Story Point value that the Scrum Team understands and can work to. The definition should be general enough to work with just about any kind of User Story. The alternative is to have different definitions for different types of work and then map the 2's, for example, for each of these definitions to each other.
You could leave a comment if you were logged in.
  • /home/hpsamios/
  • Last modified: 2016/07/03 13:38
  • (external edit)