level. Once approved by the customer and relevant stakeholders, it becomes the basis for the work to be performed. For example, in planning an Exchange migration, the project definition should include the following: Project overview: Why is the Exchange migration taking place? What are the business drivers? What are the business benefits? Objectives: What will be accomplished by the migration? What do you hope to achieve? Scope: What features of Exchange will be implemented? Which departments will be converted? What is specifically out of scope? Assumptions and risks: What events are you taking for granted (assumptions), and what events are you concerned about? Will the right
hardware and infrastructure be in place? Do you have enough storage and network capacity? Approach: How will the migration project unfold and proceed? Organization: Show the significant roles on the project. Identifying the project manager is easy, but who is the sponsor? It might be the CIO for a project like this. Who is on the project team? Are any of the stakeholders represented? Signature page: Ask the sponsor and key stakeholders to approve this document, signifying that they agree on what is planned. Initial effort, cost, and duration estimates: These should start as best- guess estimates and then be revised, if necessary, when the work plan is completed. PROJECT WORKPLAN 2: Create a planning horizon After the project definition has been prepared, the work plan can be created. The work plan provides the step-by-step instructions for constructing project deliverables and managing the project. You should use a prior work plan from a similar project as a model, if one exists. If not, build one the old-fashioned way by utilizing a work- breakdown structure and network diagram. Create a detailed work plan, including assigning resources and estimating the work as far out as you feel comfortable. This is your planning horizon. Past the planning horizon, lay out the project at a higher level, reflecting the increased level of uncertainty. The planning horizon will move forward as the project progresses. High-level activities that were initially vague need to be defined in more detail as their timeframe gets closer. PROJECT MANAGEMENT PROCEDURES 3: Define project management procedures up front The project management procedures outline the resources that will be used to manage the project. This will include sections on how the team will manage issues, scope change, risk, quality, communication, and so on. It is important to be able to manage the project rigorously and proactively and to ensure that the project team and all stakeholders have a common understanding of how the project will be managed. If common procedures have already been established for your organization, utilize them on your project.
- Summer '16
- Project Management, project manager