When EXTRA features knocking on the door, what do I do? My client says: WE NEED THIS.... but My boss says: REMEMBER MARGINS SON.... Are you serious, who should I please first? lol :-) Here are a few things which can help: 1. Document Everything: Ensure all feature requests are documented. This includes the initial project scope, any changes requested, and the impact of these changes on the project timeline, budget, and resources. 2. Evaluate Impact: Assess how the new features will affect the project. Consider factors like additional time, cost, and resources required. 3. Prioritize Features: Work with the client to prioritize the new features. Determine which features are critical and which can be deferred to a later phase.

I would start with understanding the value they seek from the additional features. Engage the stakeholders to prioritize the new feature, by removing or pushing the less value feature. Assess the impact of the requested changes on the current project's scope, timeline, and budget. Log a Change request for the new feature requested. Assign a resource to build the new feature. Share the timelines and budget with stakeholder. Track the progress and communicate frequently on the progress of the deliverable.

Scope creep is a common challenge in project management, especially when clients request additional features. To handle this, believe in open communication and transparency. First, listen carefully to understand their needs. Then, explain how these changes might impact timelines, costs, and resources. Together, we prioritize and decide what can be added without compromising the project’s success. It’s all about balancing expectations while staying aligned with the project goals.

First of all, know your contract and understand how (sometimes if) it defines the change process. And in general terms, when you receive a change request, ask for formal instruction. Consider that, conditions may change, the client may waive their request and you have no entitlement to claim the hours your team spent to analyse the request. So, formal instruction is first. Then, analyse the change request within your change review board and prepare the cost and time impact. During that time, maintain transparent communication with your stakeholders. Consider, your analysis may take weeks and it may be better to even stop the ongoing works to limit the waste of resources.

Remind the stakeholders about their agreement on what the baselined requirements were. Remind them that they approved a change management process Oh, you don't have those? Ooops