The Agile Awards Fallacy
A few days back, the Head of Products of a firm alluded to the plan of a new approach in their company. It would involve the employment of a credit point based objective assessment system. This methodology would be used to build a score board for agile product development teams; where each team could track their credit points earned during a sprint and compete for a Sprint Champion Award.
As a product manager, the questions to strike my mind were –
- what would be achieved?
- why even do this, in the first place?
Why do this?
The management had been thinking along the lines of building this concept to nourish overall healthy competition between teams.
What would be achieved?
Having driven products in parallel with completely divergent objectives, users, etc; the program got me thinking about the implications on the teams. I turned to the basics, referring to the Agile manifesto. One of the twelve principles says –
Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.
While the intent of the program sounded good, the finer details spelled a recipe for disaster. The plan sounded unfair to the teams who worked hard day in and day out despite being bombarded with a constant barrage of changes. They might not be able to achieve the award simply because of an issue that they might not be directly responsible for. Hiring the right people and then trusting them to the job is of paramount importance. The program seemed to undermine this key tenet of a product company.
Another of the principles says –
Our highest priority is to satisfy the customer
through early and continuous delivery
of valuable software.
From a delivery perspective, my thoughts centered around a dissimilar concept. Instead of rewarding teams on the basis of points scored, the champion award could be proffered to the team that ended up delivering something worthy of use. The value stream of the feature/product could be mapped towards either the client/customer/consumer. Walking down this path could definitely take time, in terms of measuring and justifying the champion, but the approach could be worth it’s grain of salt.
In conclusion, ideas like the above can tend to negate the purpose of the methodology. While agile as a framework has its benefits of allowing inflection points, which enable pivots for teams/products/companies; it needs to be used to provide a meaningful nudge to the teams, that strive hard to deliver true value.