Identification of key delivery risks and mitigation
Content migration
Content migration and the generation of new content will be a significant element of the project.
We understand that much of this will be undertaken by the PLA team but Webheads can assist where needed.
Should you be saying something about cross referencing the content plan with the UX and design of the website. In other words making sure the content is really focussed on the goals of the project rather than just regurgitating what’s already in place.?
And add something about the training to add the content into the website as they do say in the RFP that they want to reduce the amount of people hours needed to maintain the site (could offer group training session) and minimise the need for IT support. Your training will do this.
Effective 301 redirects
Understanding what content is transferred and what content is being culled is vital as redirects will need to be in place so not to lose SEO value and to ensure users don’t land on broken pages. As well as enforcing HTTPS redirect so the entire site is secure.
Scope creep and time crunch
One of current issues is that we don’t have the full specification of the data feeds and all the requirements. So as discussed on our call – this is TBC during the Discovery Phase where we will create the Technical Specification document.
How to mitigate scope creep: Creating clear project parameters from the start will strengthen your project scope. Agreeing upon the project scope and communicating that vision with stakeholders from the beginning will leave less room for scope creep. Scheduling regular progress check-ins can also ensure the project stays in line with the original project scope.
How to mitigate a time crunch: To mitigate time risk we overestimate the time needed to complete tasks in the planning phase and build in time contingency.
We’ve identified the following risks associated with this project and outlined solutions to them below: