Skip to main content

Posts

Showing posts from May, 2013

Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?


We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
This is…

Verily, I say, 'tis what it's all about

The Hokey Pokey— by William Shakespeare

O proud left foot, that ventures quick within
Then soon upon a backward journey lithe.
Anon, once more the gesture, then begin:
Command sinistral pedestal to writhe.
Commence thou then the fervid Hokey-Poke,
A mad gyration, hips in wanton swirl.
To spin! A wilde release from Heavens yoke.
Blessed dervish! Surely canst go, girl.
The Hoke, the poke — banish now thy doubt
Verily, I say, 'tis what it's all about.


From a Washington Post Style Invitational contest, that asked readers to submit instructions for something (anything), but written in the style of a famous person. The winning entry was The Hokey Pokey (as written by Shakespeare), written by Jeff Brechlin, of Potomac Falls, Maryland.  Source.


Software Versioning Schemes - FAIL!

The software industry has created a knowledge and expectation of product versions.  Previously the closest industry to create this mindset was the automotive industry - they had the model year concept.  Typically they added nice to have "bells or whistles", but rarely added true features each iteration of the auto model year.

Software was a new paradigm, back in the 1980s, this industry started using a version numbering scheme (major dot minor). For example, Windows 3.1, the first version to truly work and deliver value to the customer.

What happens when a company moves back to the model year concept of versioning in the software industry?  Does it help customer to understand the expectations of value being delivered?  Does it create more cognitive load for decision makers?

Here's an example, you tell me; it is May of 2013, is this the best move for Company X.

Coming Soon: SharePoint 2010
The long-awaited upgrade to SharePoint 2010 will soon roll out in phases across Compa…