Please enable JavaScript.
Coggle requires JavaScript to display documents.
RSC risks (Resource availability (Only one FED - 90h of FED in Aug (Try a…
RSC risks
Resource availability
Only one FED - 90h of FED in Aug
Try a more agile approach with design feeding elements to Qas earlier
Currently all QA is to Emma - risk of overloading
Share QA with Marina
Current timeline relies on 2/3 devs working on this simultaneously
Scope
LCP removed from scope
Removed from forecast - potential to include later
More content to be loaded - some of it bizarre
It's on T&M and analysis will be booked in on all - especially the wackier aspects
Internal changes at RSC has potential to change scope drastically
Dan to keep project team up to date and RSC willing to accept risk of paying for rebrand
Changing PMs at Abacus and RSC
I'm leaving - will need to handover
Phil to attend start up meeting - Jack to build KANBAN board to support ongoing dev
RSC without PM - Frank stepping in
Risk is Frank is senior and therefore might kabosh sections of the project (as he has done with LCP)
Positive feature is he is senior so can (hopefully) get things done at pace
Customisation
High level of customization introduces risk of delay/budget depending on complexity
Extensive analysis period following on from a scoping period
QA to happen alongside build at key milestones to give early visibility of setbacks