February 4, 2012

BigVisible Blog

Failure is good, really!

I think most of us have heard the story about Thomas Edison a few hundred times:

When asked about why he failed to create a light bulb in 1,000 attempts, Edison allegedly replied, “I have not failed 1,000 times. I have successfully discovered 1,000 ways to NOT make a light bulb.”

Regardless of how many times I hear it, I always wonder the context it is being employed in and by whom. I am not always sure that the right insights are drawn by some of those quotes. One instance comes to mind in a conversation I had with someone while attending the Agile Coach Camp in Montreal 2011 (great fun!). Somehow the conversation made it from empiricism to efficiency and over to effectively managing people to make them more productive (!) before I could comprehend it all. I think my listening skills glitched for a minute; I never even saw this line coming. [Read more...]

Greenshifting and Redshifting within Projects

I’ve been thinking recently about the various roles project stakeholders play, and how they may distort the environment around a project until that distortion in turn impacts the reality of the project. Let me offer two key examples. The first, coined by Scott Ambler, is known as greenshifting. In this case, the further information moves from the team, the better – hence “green” on a status report – the project looks. This is a common dynamic, one that most people have experienced first hand. The team members report out numerous challenges, which the project manager – who is there to make sure problems don’t emerge of course – puts as positive a spin on it as he can. This may get filtered up through any number of managers who need to present their work in the best light, such that a project under serious duress will appear to be in perfectly good shape. [Read more...]

What’s in a Sprint Goal?

Based on the results from last month’s poll, it seems many people are finding themselves in a situation where some of their work is not fitting within their sprint. Indeed, nobody reported that they were consistently delivering all work, and nearly a third were reporting that half or more of the committed work was bleeding over into the proximate sprint. This ultimately begs the question: should a team always be meeting its sprint commitment? Is missing a goal a good thing or a bad thing? [Read more...]

Teams over Projects

Thanks to Derek Huether for bringing up the excellent topic of bringing projects to teams instead of spinning up a new team for every possible need within an organization. Having looked at numerous organizations trying to balance the demands of running too many projects, this is very good advice. However, I think there’s more to this than simply bringing projects to teams. It does not yet answer the root cause of why we try to run too many projects, nor does it answer the key question when that executive responds, “well, Agile’s great, but I would need 5 times my current staff to run all my projects as Agile projects” [Read more...]

Coaching is Not Letting Your Teams Fail

Failure is not always bad.  We learn through our failures.  So why not first let your team fail?  It is almost like TDD – set a goal, watch the team fail to achieve it, and then show them how to achieve it.  Poetic, no?  No.  People are not lines of code.  Teams first discovering Agile need more than education – they need guidance.  Guidance means leading the team on the right path; showing them the pitfalls to avoid; warning them of impeding hazards.  A coach’s job is not only to teach a team how to do Agile, but rather to help them achieve success.

[Read more...]

Why a ScrumMaster is like a Quarterback

The other night as I was taking my evening break from the Agile World, I was confronted by 2 aliens who were very upset with our regard for sports in general, the Human Race overall, and for some reason me in particular.  In fact they were so irritated they didn’t try to put a probe in me.  I was crushed.
[Read more...]

Collaborative Play to Solve Problems

Most people within the Agile community seem to be firmly committed to the use of games and interactive exercises for training. I fondly remember first being introduced to the XP Game as a powerful way to demonstrate the values and principles of Agile Software development. While the use of games and play is growing in popularity, I fear that many people hit a roadblock. They frequently see games & play as limited exclusively to the “fun training” domain and don’t appreciate just how powerful it can be for actually solving problems. Indeed, the more I explore this domain, the more I realize that collaborative problem solving is their most valuable use! [Read more...]