have a team of developers who keep adding "cool" extra features that weren't in the scope. While the features are great, they are eating into our budget reserves. How do you handle this "Gold Plating" without demoralizing the creative team?
3 answers
Gold plating is a silent budget killer. To handle this, you need to reinforce the "Definition of Done." In our standups, I make it clear that anything beyond the acceptance criteria is actually a risk, not a benefit. I don't want to kill their creativity, so we created a "Future Enhancements" backlog. If a developer has a great idea, we log it there instead of building it now. We tell them that if we finish the core project under budget, we will spend the final week working on the top-voted features from that backlog. This keeps them focused on the immediate goal while respecting their input.
Are you using a strict Change Control Board (CCB)? Sometimes developers gold plate because they don't realize that even "small" changes have a massive cumulative impact on testing and documentation costs.
Educate the team on "Opportunity Cost." If they spend time on unrequested features, they are delaying the features that the customer actually paid for and needs to launch.
Exactly, Nancy. It's all about focus. The best code is the code that fulfills the requirement and stays within the financial boundaries set by the client.
We don't have a formal CCB since we are a mid-sized firm, but I think I need to implement a mini-version of it. Brian, do you think requiring a "Budget Impact Statement" for every new feature request would be too much red tape for a fast-moving team?