Outcomes not Ouputs
Recently I posted 5 simple changes you can make to transform organisations. Let’s unpack the 1st, “Outcomes not Outputs” An outcome is defined as “direct, tangible results of activities or processes” and I’ve personally experienced lots of teams are great at measuring them. Velocity; number of user stories delivered; or heaven forbid, the number of lines of code written (please don’t do this). But story points mean nothing (one team’s 100 could be another teams 20) and that means also that velocity is also meaningless especially when comparing between teams....