A refresh to one of my more popular posts…
Now more than ever companies are exploring ways of measuring and visualizing how their teams are doing (KPI’s; ROV’s, NPS, etc.,)
The general idea being ya can’t improve what ya don’t measure. And without some sort of systemic approach with clear visualization – things would very much be a guessing game.
Years ago that I had a bit of fun on a train commute. Remember those? Trains, planes and automobiles to get to work… Mind you, I was in the “quiet car,” so it was not a raucous karaoke kind of fun. More inside-my-own-head kind of fun. I built a personal …
While a team can rollback a code push that didn’t go well, refactor a feature that didn’t hit the mark, the one thing they can never recover is lost time. Use this retrospective technique to expose the thieves of time pestering your team,
Has the team’s daily stand-up lost a bit of freshness? How might you know? See if you can detect any of the following indicators:
No one seems to be listening to anyone else
Someone is giving waaaaaay too much detail
People are just reporting status: “I’ve been doing my job”
Lack of peer accountability
General dearth of energy
What exactly is bikeshedding? A recent conversation brought a renewed vigor to my use of the term “bikeshedding.” The term was coined c. 1957 by C. Northcote Parkinson to illuminate a discovery he made – that groups of people tended to make a futile investment of time and energy on disputes over …
