A new bank account holder who was surprised to find out his account was overdrawn. “I can’t be out of money,” he exclaims. “I still have checks left!”
Sometimes a development organization can forget that they, too, have their limits. Without good guidance, a group can mistakenly believe that planning should end only after all their top features get included. Much like the overdrawn banking customer, these groups realize much too late that they’ve ended up writing checks that their development organization can’t possibly cash.
It’s natural to want to get more done. We are an industry full of optimists at heart who want to deliver more and more value. That doesn’t make us bad people – it just makes us human. So how do we prevent ourselves from going too far? It takes a little forethought in identifying and establishing capacities.
In the Spring 2014 Release, VersionOne introduces capacity setting at two levels to help set limits that will guide our release planning and tell us when it’s time to stop. Teams can establish team- and release-level capacities to highlight just how much room is available when planning starts; keep track of how much room is left as they start to fill it up; and let everyone know when they get full. How about that… knowing where to stop even before you get started!
Other great additions such as the new Activity Stream, Agile Earned Value reporting and more are also included in this release. For more details, check out the release notes.