Sign up to save your podcasts
Or
Share Change Control
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Change Control
Send us a text
The discussion begins with light banter about the weather before shifting to the main topic: change control in projects. Change control is essential to keep projects on budget and on time. Uncontrolled changes can lead to an unlimited budget and indefinite timelines, ultimately preventing project completion.
Many clients don't fully understand the importance of change control, especially in data analytics and reporting, where visual changes are frequent. Early show-and-tell sessions can help manage expectations and control changes effectively. It's crucial to set expectations upfront about the iterative nature of good reports.
The change control process depends on the project methodology, whether agile or waterfall. Agile projects embrace change but require a process to review and approve changes to avoid chaos. A solid change control process involves documentation, a designated role to approve changes, and potentially a formal Change Advisory Board for larger projects. Tools like Jira can help manage this process.
Even minor changes, like visual tweaks, should be documented, especially if they were part of the original documentation. Every change introduces some risk and needs to be tested. Allocating a budget for change control is essential, often around 20-25% of the base budget, to cover unforeseen issues and changes.
Tools like Jira or DevOps are useful for tracking and managing changes. It's important to include changes in status reports and decision logs to ensure transparency and accountability. Excessive changes require a frank discussion with the client about expectations and capabilities. Setting realistic expectations about the tool's capabilities can prevent unrealistic demands.
Clients should be encouraged to think about long-term changes, understanding that reports and systems will evolve. Close collaboration and providing training are key, though clients often return for help. For managing change after project completion, tools like Jira can be used for ongoing change requests, maintaining an audit trail.
The discussion concludes with top tips for effective change control: manage and document all changes, no matter how small; ensure everyone in the project is aware of the change control process; and accept that change will happen, having a process to manage it. Allocating a change budget is crucial to avoid surprises.
You can download Power BI Desktop from here.
If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here.
To find out more about our services and the help we can offer, contact us at one of the websites below:
UK and Europe: https://www.clearlycloudy.co.uk/
North America: https://clearlysolutions.net/
View all episodes
By Clearly Podcasting
5
11 ratings
Send us a text
The discussion begins with light banter about the weather before shifting to the main topic: change control in projects. Change control is essential to keep projects on budget and on time. Uncontrolled changes can lead to an unlimited budget and indefinite timelines, ultimately preventing project completion.
Many clients don't fully understand the importance of change control, especially in data analytics and reporting, where visual changes are frequent. Early show-and-tell sessions can help manage expectations and control changes effectively. It's crucial to set expectations upfront about the iterative nature of good reports.
The change control process depends on the project methodology, whether agile or waterfall. Agile projects embrace change but require a process to review and approve changes to avoid chaos. A solid change control process involves documentation, a designated role to approve changes, and potentially a formal Change Advisory Board for larger projects. Tools like Jira can help manage this process.
Even minor changes, like visual tweaks, should be documented, especially if they were part of the original documentation. Every change introduces some risk and needs to be tested. Allocating a budget for change control is essential, often around 20-25% of the base budget, to cover unforeseen issues and changes.
Tools like Jira or DevOps are useful for tracking and managing changes. It's important to include changes in status reports and decision logs to ensure transparency and accountability. Excessive changes require a frank discussion with the client about expectations and capabilities. Setting realistic expectations about the tool's capabilities can prevent unrealistic demands.
Clients should be encouraged to think about long-term changes, understanding that reports and systems will evolve. Close collaboration and providing training are key, though clients often return for help. For managing change after project completion, tools like Jira can be used for ongoing change requests, maintaining an audit trail.
The discussion concludes with top tips for effective change control: manage and document all changes, no matter how small; ensure everyone in the project is aware of the change control process; and accept that change will happen, having a process to manage it. Allocating a change budget is crucial to avoid surprises.
You can download Power BI Desktop from here.
If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here.
To find out more about our services and the help we can offer, contact us at one of the websites below:
UK and Europe: https://www.clearlycloudy.co.uk/
North America: https://clearlysolutions.net/