Agile Calories
Posted by Christophe on May 5, 2010
Displaying calories on the menu is about to become mandatory for restaurant chains with more than 20 locations.
The idea is simple: showing a 700 calorie burger will get people to eat better, and will decrease obesity.
The reality?
Unfortunately, a recent study shows calorie display has extremely low to no impact on the consumers. While critical, this information doesn’t curb old habits and bad behaviors.
What’s that to do with agile?
I know most people swear by them. They ensure things happen; they guide the team day after day; they promote decision making.
Really? Is your iteration burn down working that well?
or is it suffering the same problem calories on the menu have?
Scary information, not much action?
Ulf Rask said
For me software engineering skills, scrum, burndowns and retrospectives is key to identifying your weaknesses just like nutrition skills and calory count is required info for correct eating behavior.
All of this is wasteful if you either don’t know how to change behavior or don’t want want to.
In short – learn to shape your habits. Start small and stick to desired behaviour. Easier said than done? Yes! Impossible? No!
Tweets that mention Agile Calories « Running Agile -- Topsy.com said
[...] This post was mentioned on Twitter by Paulo Rebelo, Christophe Louvion. Christophe Louvion said: Agile Calories http://bit.ly/aWD0mU [...]