It's going to be heavily dependent on the thing being decommissioned. Shutting down a website isn't going to look even remotely similar to a hydropower dam.
...
1 reply by Patrick Dicey
Dec 10, 2021 12:34 PM
Patrick Dicey
...
Good answer... I'd suggest working with the project resources/system SMEs to create a plan. Include system users and stakeholders to ensure no impacts of the decommission.
Context counts including the specific industry and any regulations that apply for such decommissions as far as communications, data retention and so on.
Also, if you are referring to a true project plan and not just a schedule, this will be constrained by organization project management standards (assuming those exist).
Can you provide more details of the scope of the system, whether it is for internal use by your organization only or whether it involves external partners and what industry it is in?
Kiron Saving Changes...
Patrick DiceyManager, Customer Project Management| CentralSquare TechnologiesOrlando, Fl, United States
Dec 08, 2021 5:44 PM
Replying to Keith Novak
...
It's going to be heavily dependent on the thing being decommissioned. Shutting down a website isn't going to look even remotely similar to a hydropower dam.
Good answer... I'd suggest working with the project resources/system SMEs to create a plan. Include system users and stakeholders to ensure no impacts of the decommission. Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
I don't see decommissioning as anything other than a regular project requiring a plan. Same concepts apply the only difference being technical details and constraints which vary in all projects. I always start the plan by defining the deliverable (objective), analysing what has too be done to get there, laying out the road map to the destination, identifying constraints, engaging the stakeholders, establishing required resources and implementing. The plan should include all project management elements - scope, costs, schedule, communications, procurement, risk, quality, etc.
A project is a project even when applying the word decommissioning. Saving Changes...
Is the system being decommissioned already fully replaced, or does it need to run in parallel for a while? I've had to decom a couple systems and we would look at:
- Who uses it? - What do they use it for? - Do they need replacement functionality? - What reports come out of the system? Are they still needed once the system is gone? - Where is the data? - What data needs to be migrated? - What data needs to be retained? For how long? - What other systems does the system interact with? Are there interdependencies?
...and so on. It's not so much a template as discovering what is going away, what it is being replaced with, and what needs to be kept, then planning accordingly. Saving Changes...
Community Champion
