-
Permalink
Mood 0
-
"the usefulness of velocity as a predictor of a team’s future story capacity in a sprint is an emergent property of a persistent team following an estimate and execute cycle"Permalink
-
"stability of velocity is what’s desirable, regardless of the magnitude"Permalink
-
"the 3-iteration rolling average of completed points becomes a useful velocity baseline for planning purposes"Permalink
-
"estimations are not meaningful as a standalone value outside the execution context of the team that made them"Permalink
-
"velocity becomes a useful metric for gauging predictability because it represents the whole cycle of estimation and execution"Permalink
-
"updating an estimate after the work has already begun ... even as a well-intentioned effort to get a “realistic” baseline velocity, [undermines] the emergent consistency in the pattern of estimation and execution"
-
"Outliers will always occur and are good discussion points, but it is the macro trends in under/overestimating that we should be looking for in order to refine our estimation skill as part of achieving a more stable velocity"Permalink
-
"We must be intentional about creating an environment of safety for a team, especially a new team, so that they feel comfortable being brutally honest with themselves about what is working well and where improvements can be made"Permalink
-
"A team should never feel like metrics will be weaponized against them"Permalink
-
"Just listening to what people have to say is important, but it isn’t enough; we must put time and energy into truly hearing what they mean and digesting what the implications may be"Permalink
-
"We must push ourselves to empathize with their circumstances, and not invalidate the impact that their lived reality has had on shaping whatever that perspective is"Permalink
-
"While you may not always be able to fully understand someone’s frame of reference, it is important to be aware of the biases of your own perspectives and how they may be influencing your response to a situation."Permalink