Listen Now
Subscribe on iTunes
Check out the podcast on Google Play Music

The Software Process and Measurement Cast 442 features our essay on capability teams. The use of teams to deliver business value is at the core of most business models.  Capability teams are a tool to unlock the value delivery engine of teams.

Gene Hughson brings his Form Follows Function Blog to the cast this week to discuss his recent blog entry titled, Systems of Social Systems and the Software Systems They Create. We live in a complex world and just focusing on social systems or software systems misses the point!

Our third column is from the Software Sensei, Kim Pries.  The entry this week is titled, Software Quality and the Art of Skateboard Maintenance. This entry is an homage to Robert M. Pirsig the author of Zen and the Art of Motorcycle Maintenance, who recently died.

Re-Read Saturday News

And welcome back!  For those who are interested, The Frederick Half Marathon last weekend was great.  I met my goals: I crossed the finish line, collected my medal and got to hang out with my family in Frederick.  This week, we begin Part Two of Holacracy: The New Management System for a Rapidly Changing World by Brian J. Robertson published by Henry Holt and Company in 2015.  Part Two is titled Evolution At Play: Practicing Holacracy.  In my opinion, Part Two provides readers with the nuts and bolts needed to use Holacracy.  Chapter 4, titled Governance, takes all of the building blocks from previous chapters and starts to weave them together. (more…)

Advertisements

 

The terms ‘long-lived team’, ‘stable team’ or to a lesser extent ‘capability’ can evoke an almost magical reaction. The problem with a magical reaction is that it switches off our ability to think about the consequences of the attributes and assumptions that need to be true for these types of the team to function effectively.  When any concept takes on a magical aura, conflict and disaster follow.  Long-lived teams sometimes don’t always make sense in every situation. (more…)

14955864_10154768928297276_8000508545464981060_n

There are those who believe that implementing a capability team is as easy as identifying a group of people, putting them together, and then doing a few team building exercises. Instant team! In the simplest terms possible – they are wrong.  There are four complicating factors that have to be addressed. (more…)

Not Exactly A Capability Team, But Close!

One of the holy grails of Agile in software development and other business scenarios is how to organize so that stable teams are efficient, effective and safe. The great preponderance of organizations use some variant of an organizational model that groups people by specialty and then allocate them to project teams.  This creates a matrix in which any practitioner will be part of two or more teams, which, in turn, means they have two or more managers and serve two or more masters.  People, like desks, chairs, and laptops, flow to the area of need, disband, and then return to a waiting pool until needed again.  One of the basic assumptions is that, within some limits, people are fungible and can be exchanged with relative impunity.  This approach has problems.  Ariana Racz, Senior Quality Assurance Analyst, provided a great summary of what is wrong with the idea that people are fungible in her response to Get Rid of Dynamic Teams: The Teams.  Ariana stated, “A resource on paper is not a resource in application.” In most circumstances, dynamic/matrixed teams reduce the productivity of knowledge workers. (more…)