Skip to main content

Agoraphobia Meets Individual Genius

I read a really thought-provoking article from the Financial Post this week which was somewhat misleadingly titled "Innovation:  Group Dynamics Can Stifle a Great Idea."

I have to admit, I jumped right on this article, because in the Dark Days before I met Agile, I was one of those people (as perhaps you were) who always hated being forced to "work in teams."  Even today, I feel a slight twinge of fear when a speaker asks an assembly to "discuss [an idea] at your table," knowing this might be followed by a very awkward moment later on when some poor soul in each group will be forced to extemporaneously report on (or perhaps invent) it's "findings."  Perhaps some of you still fight off Fear of the Wisdom of Crowds sometimes too?

Of course the article does not actually say that "Group Dynamics" stifle "Great Ideas."  Instead, it points to research at Wharton which found that a group was best empowered to develop a great idea when some one individual, an "inventor" cast in the mold of an Albert Einstein or a Steve Jobs, had done significant thinking about the idea before laying it out in front of the group.  The study found that this hybrid approach worked better than group brainstorming alone.

We as agilists would add that the hybrid approach undoubtedly also works better than a command-and-control approach where the person with the bright idea orders a team to develop it exactly as invented, and then blames the team for failure to execute down the line.

Be that as it may, however, the Wharton research on the importance of individual brainstorming and initiative seems immediately applicable to many aspects of life on an agile team, particularly when it comes to the ideation and inception phases of a project, where the team first gets its overall sense of what the project is intended to accomplish.  Experience has shown again and again that we need a whole team to deliver a high-quality, valuable piece of software which will be robust for its normal life.

But in asking what the software should do and why, or even how, if a project is bringing innovation into an existing technology stack, we should not be too quick to insist that all ideas have to spring from the entire assembled membership of the group, and we should embrace our solo inventors.

Popular posts from this blog

A Corporate Agile 10-point Checklist

I'm pretty sure my few remaining friends in the "small, collocated team agile" community are going to desert me after this, but I actually have a checklist of 10 things to think about if you're a product owner at a big company thinking of trying out some agile today.  Some of these might even apply to you if you're in a smaller place.  So at the risk of inciting an anti-checklist riot (I'm sorry, Pez!), I am putting this out there in case it is helpful to someone else.

Here's what you should think about:

1.Your staffing pattern.  A full agile project requires that you have the full team engaged for the whole duration of the project at the right ratios.  So as you provision the project, check to see whether you can arrange this staffing pattern.  If not, you will encounter risks because of missing people.  Concretely it means that:
a.You need your user experience people (if applicable) and your analysts at the beginning of the project, as always, b…

The Agile Business Case

Many agile teams have never seen a business case, ever, and they may even be proud of it.

Our mantra is that we deliver "business value," not just "software," quicker, better, and faster, but if so, we certainly don't spend a lot of time reporting on value delivery, and in fact we may be scornful about "analysis paralysis."  As software developers, we consider ourselves to be doing quite well if we can deliver the software every two weeks (or continuously).  And this is particularly if we've enabled this frequent high-quality delivery through automated testing and automated build-and-release techniques.  We've reduced business risk by making results visible more often, and allowing the business to change direction more frequently.  We assert that along the way of course we're also delivering value.  But how would we prove it?

I've recently posited that we shouldn't even think of doing agile projects without capturing and recording s…

Requirements Traceability in Agile Software Development

One of the grim proving grounds for the would-be agile business analyst (henceforth "WBABA")  is the "traceability conversation."  Eventually, you will have to have one.  You may have seen one already.  If you haven't, you may want to half-avert your eyes as you read further.  It gets a little brutal.  But if you close them all the way, you can't read.
WBABA: in summary, we complete analysis on each story card, and then we support the developers as they build it that same iteration!Corporate Standards Guy:  but how do you do traceability in agile?  You have to have traceability.  It's broadly recognized as an important factor in building rigorous software systems. These software systems permeate our society and we must entrust them with lives of everyday people on a daily basis. [The last two sentences are an actual quotation from the Center of Excellence for Software Traceability website!] WBABA: [cowed silence]Corporate Standards …