Track Success by Design activities and progress
The FastTrack team has tools that they use for tracking activities, progress, and plans throughout an engagement. As you continue through your projects, it's a good idea to have your own plans to do this as well.
Workshop success measures
When evaluating each workshop, you will have many named measures of success. Your team should make an assessment for risk and preparedness for each that applies. Having a repeatable and straightforward unit of measure is important to the success of the project. Consider each measure listed in the following table, and then adapt the precise wording to suite your own team.
| Status | Meaning |
|---|---|
| Empty | Waiting for assessment |
| Red | Finding uncovered critical changes that need to be implemented in the project |
| Yellow | Finding uncovered changes that should be implemented in the project |
| Green | No relevant findings |
You can use the Success by Design workshops to guide you toward each success measure. The following table is an example of a matrix that tracks workshops and their relevance to different aspects of a project. A solution architect can use a matrix like this one to track progress with relevance. As you continue through the project, make sure that you keep a list of relevance and an overall assessment and risk analysis for each workshop by using the color coding that is mentioned in the previous table. Consider sharing the status with all stakeholders as often as possible to avoid surprises and potential delays.
| Category Group | Category | Solution Blueprint review | Cutover readiness | Solution performance workshop | Integration workshop |
|---|---|---|---|---|---|
| Architecture | Application extension | X | X | X | |
| Architecture | Business intelligence | X | X | ||
| Architecture | Data migration | X | X | ||
| Architecture | Data model | X | X | X | |
| Architecture | Functional | X | X | ||
| Architecture | Instance strategy | X | |||
| Architecture | Integration | X | X | X | |
| Architecture | ISV | X | X | ||
| Architecture | Performance | X | X | X | X |
| Architecture | Security | X | X | X | |
| Architecture | User experience | X | X | ||
| Competency | Customer | X | X | ||
| Competency | Partner | X | X | X | X |
| Fit for purpose | Presales | X | |||
| Fit for purpose | Product/solution fit | X | |||
| Fit for purpose | Under-licensed projects | X | |||
| Implementation | Application lifecycle management | X | |||
| Implementation | Business continuance planning | X | X | ||
| Implementation | Change management | X | X | ||
| Implementation | Continuous update | X | X | ||
| Implementation | Cutover | X | X | ||
| Implementation | Fit-gap analysis | X | |||
| Implementation | Rollout approach | X | X | ||
| Implementation | Testing | X | X | X | X |
| Other | External factors | X | X | X | |
| Product | Feature deprecation | X | X | ||
| Product | Feature gaps | X | X | ||
| Product | Product bugs | X | X | ||
| Product | Product performance | X | X | X | X |
| Product | Product reliability | X | X | X | X |
| Project governance | General governance approach | X | |||
| Project governance | Schedule | X | |||
| Support | Support | X | X |
When you start working on the project, and after you have conducted a workshop, you should immediately update the relevant success measures, particularly if any concerns arise. Also, make sure that you update and complete the appointment with time/attendees/status and any other notes.