Mon 23 Nov 2009
Paper Clip Consulting

Clippy - the ultimate bearer of redundant information
Remember this guy? He used to pop-up when you least expected him and offered up information about something you already knew.
I’m sometimes reminded of Clippy when I hear the rhetoric from some in our Agile community.
We’re at an inflection point right now. The pragmatists and the conservatives are realizing the fallacy of large upfront planning.
As teams from these later adopters are striving to become leaner and more Agile, they struggle with the inertia that is inherent in large organizations.
- They know that co-located teams are more successful but they prefer an environment that extends the benefits of working from home.
- They know that it is much more efficient to work on one task at a time but someone way above their pay grade won’t let them have such a single minded focus. This is not a battle they can win right now.
- They know that value can be delivered faster if testing can be pulled forward yet they don’t have budget to buy the tools they need.
For such decisions Clippy always knows the right answers for everybody. But Clippy doesn’t have to walk in their shoes and it won’t be Clippy who gets fired for taking a risk.
Maybe Clippy needs to listen to Norm Kerth (from his book Project Retrospectives):
“Regardless of what we discover, we understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.”
or as my colleague Julie Chickering says:
“I think we need to acknowledge that there are parts of organizations that will be less agile than others while moving from traditional to agile projects. That the big ole ship can’t turn on a dime. To me this is part of being a trusted partner.”
As you strive to become leaner and more agile, you don’t need Paper Clip Consulting, you need a trusted partner. You need someone that will begin with the end in mind yet not seek to get there immediately. A trusted partner will take the time to understand your environment, accept that there are always constraints and help you establish a cadence of continuous improvement.
About the Author: Ken Clyne is a kayaker, Certified ScrumMaster and Agile Coach at Rally Software Development. Subscribe today to get free updates by email or RSS.
I’m sometimes reminded of Clippy when I hear the rhetoric from some in our agile community.
We’re at an inflection point right now. The pragmatists and the conservatives are realizing the fallacy of large upfront planning.
As teams from these later adopters are striving to become leaner and more agile they struggle with the inertia that is inherent in large organizations.
- They know that co-located teams are more successful but they prefer an environment that extends the benefits of working from home.
- They know that it is much more efficient to work on one task at a time but someone way above their pay grade won’t let them have such a single minded focus. This is not a battle they can win right now.
- They know that value can be delivered faster if testing can be pulled forward yet they don’t have budget to buy the tools they need. They understand very well the return on investment and to Clippy it’s a no-brainer but Clippy doesn’t have to walk in their shoes. Maybe Clippy needs to talk to the CFO.
Maybe Clippy needs to listen to Norm Kerth (from his book Project Retrospectives)
“Regardless of what we discover, we understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.”
or as my colleague Julie Chickering says:
“I think we need to acknowledge that there are parts of organizations that will be less agile than others while moving from traditional to agile projects. That the big ole ship cant turn on a dime. To me this is part of being the trusted partner.”

I always viewed Clippy as an integral part of the anti-Demo.
If you team’s Sprint Demo includes Clippy, chances are the focus is not on a working prototype :)
-David