
How to Avoid Being Stalked By Scope Creep: The Project Charter
Scope Creep. Sometimes it’s politically motivated. Sometimes it’s intentional. Sometimes it’s a misunderstanding. But it’s always painful.
As Geneca's CTO, Bob Zimmerman continues to build on his work as the driving force behind Getting Predictable, the requirements definition and project best practices that are the foundation of Geneca’s mission to make software development predictable. He continues to extend these best practices to leverage more value for clients and new growth opportunities for Geneca.
Scope Creep. Sometimes it’s politically motivated. Sometimes it’s intentional. Sometimes it’s a misunderstanding. But it’s always painful.
It’s not often, but I believe we have all experienced the meeting that goes too smoothly. There’s anywhere from four to eight people, trapped with each other for an hour, around our favorite conference table.
Recently, we’ve introduced Commitment Based Estimation to a couple of our software teams. Typically, this helps a team provide highly-accurate estimates. These teams go on to deliver successfully by meeting these estimates.
In this blog I usually write about best practices that help set teams up for success. That is really what Getting Predictable is about.
Recently a consultant asked me if I encourage teams to do a project postmortem or retrospective once a project is done. The goal is to review what worked well and what didn’t.
Every team needs a process they can embrace because they know that process will get them to the desired result.
In previous posts, I have discussed best practices around Change Control. Or, maybe I should say “lack of best practices” since so many organizations either fail to follow a defined process or simply don’t have one.