Complete Readiness Checklist
Before you start a project, a Readiness assessment should be conducted to review various pre-requisite processes, enablement, environments are in place and to ensure you have other “must haves” are in place to create the conditions for a successful project. If you don’t start from the right place, you are likely to end up in the wrong place.
The objectives of this assessment are to:
- Assess the real picture of the current state.
- Evaluate of how prepared you are to start project work.
- Reduce budget creep while things are getting ready.
- Improve communication and transparency.
- Reduce project failure and schedule risk.
A Readiness assessment evaluates three core areas: People, Process, and Technology. It verifies whether the “nuts and bolts” are ready for project kick off and the start of the Build Phase. For example, you need to assess:
- What personas are needed for the project.
- What skills should these resources have.
- How can they be enabled.
- What tasks should be assigned for newly enabled resources.
- How to manage blended teams with local and remote resources.
- How do you structure strong governance, who should attend, sample meeting templates and agendas.
- How to onboarding new project team members.
- Readiness and templates for writing good user stories.
At this point in the project lifecycle, it is assumed that the MLP has already been defined. - see Creating Case Type Backlog for how to define.
You want to be sure that your team is ready and has enabled resources, and your environment(s) and the priorities are well-defined and understood before you initiate development. Conducting an organizational readiness assessment gives your project team and key stakeholders the knowledge and assurance that your project will be successful. It also provides early alerts for potential issues and the ability to address them before they become big problems as you move forward on the proposed project.
You complete a Readiness Checklist, identifying any gaps and preparing a remediation plan with target dates. You agree on the gaps which are on the critical path before you can engage the development team.
Published May 8, 2018 — Updated June 18, 2018