Quote stage
- Clear scope agreement ahead of time with organisational mapping
- Estimate number of man-days across development and implementation
- Estimate gross margin
Start of a project
- Create an ambitious but a realistic timeline. Don't move the timelines once the base line is set. Objective is to identify issues ahead of time so that we can prioritize it internally OR escalate issues to the customers
- Set deadlines (even if not fully known) and single owners for each task. Only add multiple owners if absolutely necessary. Owners must be individual names, not departments or organisations.
- All tasks should start with action verbs; otherwise, it is too nebulous what needs to be done.
- If you need to assign an action to a client, add individual names of Clients as “Labels” rather than People
- If you need to assign an action to a third-party, again add individual names of the third-party vendor as “Labels” instead of people.
- Only assign actions to “departments” or “organisations” (again as Labels) if an individual owner is unclear.
- Once the initial project plan is created and socialised with client, set baseline(s) so we can measure project progress against a historic baseline
- Always copy commercial stakeholders
- Setup weekly rhythm with customers
During the project
- Adjust dependencies automatically by shaking the top level task
- Always only enter comments on TeamGantt that you are happy for a client to see
- Assign RACI matrix on specific tasks
- Use milestones to spotlight important meetings, approvals, decisions, or deliverables.
- Share progress with the client or third-parties by a) filtering only for client/3rd party owners and b) giving them a View Only option. We recommend using the options settings below and sharing the respective URL with them (under Menu > Embed)Needs to be very tightly managed by
Other options
- Ability to create repeatable templates
- See multiple projects at the same time
End of the project
- Completion of the project from our standpoint is based on the following:
- We have delivered the software to the customer even if a) all the data has not been fully migrated, b) all the users or departments haven’t been fully onboarded with the software with training
- If there is integration with 3rd party applications involved and if the customer is not ready to setup, we should push for “delivery” for the purposes of invoicing and any outstanding integrations becomes a post go-live activity
- Going live for Hosted Solutions need to be on delivery of test software with some patient data
- Formal email should be sent to the customer notifying that the project is “live” from our standpoint. Click here for a Go Live Email Template.