Project Completion Process
|
Step |
Action |
| 1 | Divisions or Shared Services department identifies task or process as potential CI project |
| 2 | Summary of the project is submitted to ci@advantus.com |
| 3 | CI/Project Manager logs project requests and meets with requestor to obtain necessary information for ranking the project (See Project Ranking Process for complete steps) |
| 4 | CI/Project Manager creates Project Folder and a copy of Report_form for proposed Project and saves it in the Advantus Continuous Improvement, Shared Services Projects folder.
|
| 5 | CI/Project Manager completes Process/Project, Department/Division, Initial Condition and Before section on the newly created Project Report Form.
|
| 6 | CI/Project Manager completes Originated by (requestor) and SME fields on the Report_form
|
| 7 | CI/Project Manager schedules kick-off call with identified SMEs to discuss the scope of the project, perform root cause analysis, and create lists of tasks required for the project completion |
| 8 | CI/Project Manager creates project tracking document to use throughout the project. Options of templates to use are in the Tool Kit folder on the Advantus Continuous Improvement SharePoint site. Saves project tracking document in the Project folder on SharePoint. |
| 9 | CI/Project Manager schedules recurring project meetings to review the progress and status of tasks. Updates project tracking template with all changes. |
| 10 | CI/Project Manager oversees all testing of the changes. Necessary corrections are requested and made. Testing continues until the desired outcome is achieved. The Validated by section of the Report_Form is completed.
|
| 11 | Implementation occurs. CI/Project Manager determines follow-up date and schedules meeting with requestor and SMEs. Completes Solution Description, Implementation date, and Follow up date sections on Report_form for project.
|
| 12 | CI/Project Manager conducts follow-up meeting. If any changes are necessary, tasks are added to the project tracker and the process continues until implementation is successful. Once no changes are needed, CI/Project Manager receives approval from the original requestor in writing. |
| 13 | CI/Project Manager completes After, Benefits Description, Approved by, and Transition Date sections on Report_Form
|
| 14 | After 30 days, CI/Project Manager conducts AAR meeting to confirm changes meet identified need. Collects observations of what went well and areas of improvement to be used in future projects or processes. |
