|
||||||||||||
| profiles | |
services | |
clients | |
careers | |
ideas | |
contact us | |
|
|
||||
| overview | ||||
| At the end of every project it is paramount
to monitor and review the impact of the project. Post launch services
feed back into the Innovation phase, where future plans stand to benefit
from current project learnings. Post Launch services include: » Issue Tracking & Analysis » Post Mortem Review » Cycle Time Improvement Issue Tracking & Analysis Issue Tracking & Analysis requires a formal structure (terms, definitions, guidelines) in order to classify issues along a severity rating. The Sonik model follows basic project issue classifications based on project experience: a severity scale of 1 - 5 is often used for engagements. However, in many cases, the client has pre-defined issue classifications which are deferred to instead. Issue Tracking is a fundamental requirement throughout the project lifecycle. The Sonik model, however, illustrates the importance of issue tracking and analysis activities at this stage. Once the new process or application is launched, each issue is examined to determine if: (a) the issue requires immediate resolution for the current release, (b) the issue becomes an enhancement request of the next release, and gets embedded into the product roadmap of the future release, or (c) the issue is insignificant (deemed not to affect customer needs or adversely affect functionality) and is archived. Issues also are one information input into the Post Mortem Review process. Severity one (or red flag) issues are normally highlighted as the conclusion of a project, and their resolution is documented for future learnings. Post Mortem Review A Post Mortem Review is undertaken by the project team at the conclusion of a project or initiative. The review is meant to take learnings from the existing project, and form recommendations to improve the project structure and execution in for future initiatives. The Sonik model calls for this review to be conducted in 3 general stages: Pre-Meeting Preparation, Project Team Meeting, and Post Mortem Project Report. Cycle Time Improvement Cycle Time Improvement is primarily used by managers seeking to improve their unit's day-to-day operations while maintaining their own management responsibilities. This process uses rapid learning to improve processes. |
|
