My team has a go-live/ production and monitoring phase. We are trying to create a checklist to standardize this process. Any recommendations on how to approach this? Saving Changes...
Any actual checklist will be highly dependent on the process itself. To develop one, first document what you think your process looks like, such as using block diagrams in Visio. Then you can review it in detail and document best practices and key requirements for each step, and also each transition between steps. In addition to reviewing each block (node) and connecting line (edge), you should also evaluate the sequence of steps. Are they logical? Are they consistent or flexible?
I would suggest reading up on Kaizen which is about continuous improvement of a process, but as Ono Taiichi said, "where there is no standard, there can be no kaizen". so first you need to document the process you wish to improve. Saving Changes...
To add to Keith's feedback, I'd suggest reviewing the issues logs from past production & monitoring phases to identify key risks which could be avoided proactively - those measures might be good content for a checklist.
Kiron Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
We used to call such a phase hypercare and provided extra development resources to solve upcoming problems quickly. It was scheduled for 1-3 months and
- took care about prty bug-fixing after GoLive
- supported the maintenance and production staff to become efficient
- supported end users as an extension of the change mangagement
- finetuned doucumentation Saving Changes...
