Thoughts on technology and innovation
Ted Husted, Release Engineer
Every agile team wants to run faster than a speeding bullet and leap tall buildings in a single bound. In agile parlance, we all want to increase our true velocity -- the amount of work we accomplish in every sprint.
Being a skeptic by nature, I say "true" because it's easy to increase apparent velocity without really getting more done.
There's an old saying: "Time, Quality, Scope -- Choose any two." An easy way to reduce coding time is to minimize testing. But lowering quality leads to defects, and defects increase rework. If we slash scope and oversimplify a feature, many customers won't be able to use it. A feature that most people can't use is mostly useless.
In practice, there are three well-worn paths to increasing true velocity: (1) Optimize scope, (2) Enhance infrastructure, and (3) Reduce rework.
If your heartfelt answer to any of these points is "Not so much", then maybe it's time for a retrospective with the team, to discuss ways to work smarter and get more done.
Have you found other ways to increase velocity on your own team? If so, post a comment, and lets start the conversation!
Ted Husted is a Release Engineer for Nimble AMS. "My job is to make sure we ship everything that's done, but not before it's ready." For more about Enterprise Development on Force.com, visit DreamOps.org.