Why Requirements Change Mid-Project: A Common Phenomenon

When embarking on a project, it's essential to understand that requirements can shift mid-stream due to various factors such as changing stakeholder needs, new information becoming available, or unforeseen circumstances. This unpredictability can be particularly challenging for project teams, who must adapt quickly to these changes while ensuring the project remains on track. As a result of these shifting requirements, it's not uncommon for projects to experience scope creep, where additional features or functionalities are added at the last minute. This can lead to delays, increased costs, and a higher risk of project failure if not managed effectively. To mitigate this risk, it's crucial to have a flexible approach in place that allows for easy adaptation to changing requirements. This may involve regular stakeholder meetings, agile

Getting Started

Key Considerations

When requirements are subject to change mid-project, it is essential to adopt a flexible approach to ensure project success. The key consideration is to communicate effectively with stakeholders and team members to understand the reasons behind the changes and the scope of their impact. A thorough review of the current project plan and documentation is necessary to identify areas where adjustments can be made, such as revising timelines or resource allocation. It may also be necessary to re-prioritise tasks and adapt project deliverables to reflect the updated requirements. By embracing change and collaborating with all parties involved, organisations can mitigate potential risks and maintain momentum throughout the project.

Practical Steps

When requirements change mid-project, it's essential to establish a clear communication plan with all stakeholders involved. This includes updating project documentation, such as project plans, user manuals, and technical specifications, to reflect the changes. It's also crucial to involve team members in the revision process to ensure that they are aware of the updated requirements and can adapt their work accordingly. Additionally, consider implementing a change management process to track and record all changes, including the rationale behind them and the impact on the project timeline and budget. By taking these practical steps, you can mitigate the disruption caused by changing requirements and get your project back on track.

How to Put This Into Practice

1. Identify the reasons behind the changing requirement by reviewing project documentation and communication records to understand the context and rationale for the changes.
2. Communicate with stakeholders, team members, and affected parties to inform them of the changed requirements and gather their input on how to proceed.
3. Assess the impact of the changes on existing work, resources, and timelines to determine what adjustments need to be made to the project plan.
4. Prioritise tasks and allocate new or revised resources accordingly, taking into account any additional costs or dependencies that may arise from the changed requirements.
5. Document the updated requirement and its associated changes in a clear and concise manner, ensuring that all relevant parties are aware of the revised scope and expectations.

Worked Example

A local bakery had initially planned to supply 500 loaves of bread per week to a new supermarket chain, but after conducting market research, they discovered that the supermarket was expecting a higher demand for wholemeal bread. The bakery increased their weekly production by 25% and subsequently informed the supermarket about the change in requirements. To mitigate any potential delays or stockouts, the bakery offered to deliver the increased quantity over two days instead of one, ensuring that the supermarket's needs were still met within the agreed-upon timeframe. This proactive approach allowed both parties to adapt quickly to the changing requirements and maintain a positive working relationship.