You should do this at the same time that your manager is assigning you as the Project Manager. Ideally, they can provide you with these answers at the same time that you are receiving your assignment. But don't be surprised if they can't or if their answers are vague, because in many cases your manager may not have a clear picture of the project.
You can usually close any gaps in the answers provided by your manager by reviewing the key project artifacts. Ideally, your manager can provide these artifacts to you, but you may have to get them from other people. You will build a good understanding of your project and its context by reviewing these documents thoroughly.
Remember, you aren't looking for final answers. You just need enough information to build a basic understanding of your project and to know who the key players are. You will formally define the project during the Project Initiation phase. Project Discovery provides you with a systematic approach for getting a high-level understanding of your project.
And by completing this quickly, you will show your manager that you are ready to lead your project. Skip to content Project Documents An important clarification in the PMBOK is the distinction between the project management plan and the various project documents the project manager may utilize in helping manage the project. Just about every project manager has the need to develop a Use Case Document, this template is provided as a starting point from which to develop your project specific Use Case Document.
The Use Case Document ties the business needs of a system to the design and implementation of the Go To Template. A key document required for the success of a project is the training plan. This training plan template provides the framework for developing your project specific training plan. The System Design Document is a required document for every project. It should include a high level description of why the System Design Document has been created, provide what the new system is intended for or is intended to replace and contain detailed descriptions of the architecture and system components The Service Improvement Plan is a plan and road map for improving service levels; e.
It is based on service level review, and customer and Service Level Management Process improvement suggestions. The Security Policy is a statement of the types and levels of security over information technology resources and capabilities which must be established and operated in order for those items to be considered as secure. Define your Quality Metrics before starting your project.
Use a quality checklist to ensure quality is planned into your project. A lack of quality control makes it impossible to guarantee quality in your projects.
This easy to use proposal template provides an excellent starting point to write the small proposals that are usually required before performing work on a specific part of a project. Knowing exactly what your funding requirements will be, before you even get started, is extremely important to the overall success of a project. Use our project funding requirements template to plan ahead and avoid the often-dangerous last minute scramble for additional funding.
Playing the violin is an art form. So is managing a project. As a significant point or event in your project, all project milestones should be listed and tracked. Milestones are a good means to determine if your project is on schedule and a useful tool for reporting to management. A well executed meeting ends with prompt and clearly documented Meeting Minutes.
Resource Allocation Matrix. Estimate required resources by role and skill set. Discuss with the manager from each area involved to identify resource availability and gaps. Provide detailed explanation of the scope, cost, and definition of the project. This information is normally required when it is necessary to provide an explanation of the benefits that will be realized as a result of the project.
Larger or more complex projects usually require a Business Case. Request for Information. Conduct vendor research to see what technology is currently available in the market place. Consult with peers at other universities to determine potential solutions and their costs, benefits, and risks. During this phase, the Project Manager works with the project team to document high level functional and technical requirements.
The Project Manager defines high-level resource, cost and time estimates, and begins developing a project plan. This is also the time to develop a project management plan. The project management plan defines how the project is executed, managed, and closed. Requirements Document.
Project Schedule WBS. Document project tasks, deliverables, milestones, schedule, and resources. The project schedule will be modified as more is known.
Communication Plan. Familiarize the project team with the project, review key elements from the project charter, review project management processes risk, issue, change management and receive buy-in from all project participants.
Budget Tracking Spreadsheet. Org Chart with Roles and Responsibilities. Provide view of project team. Prepare high-level architecture diagram showing integration with other systems and internal technical structure. Assess each stakeholder group that will be impacted and their level of support for the solution. Traceability Matrix. Deliverable Alignment Matrix. Participate in TAC Review. Prepare Lens information in advance of the TAC review.
Participate in r eview of major technology decisions as they relate to overall IT architecture and facilitate approaches to integration, process, and skills. This phase is where the actual implementation or execution work begins. Project tasks and deliverables are completed and the project begins to realize the objectives and scoped defined in the Project Charter. Functional Design Specification. Provide a detailed description of each technical requirement to be implemented as part of the project.
Include a complete technical assessment of each customization object identified to be in scope. Define data structures, relational database models, choice of programming languages and tools, algorithms, etc. Test Strategy. Develop strategy to be followed for testing. Include detail in strategy when a simple test plan doesn't cover all of the areas of testing that need to be performed to ensure solution is working as planned.
Document sequence of steps or activities in order to drive individual, team or organizational transitions and ensure the projects meets its intended outcomes. Training Strategy. Develop Training Strategy. Create a strategy document when the training required to enable the use of new features is not straightforward or requires training at various levels. Build consists of developing or configuring project hardware, software, and business processes according to the agreed-upon specifications.
Test Plan. Build a comprehensive list of unit, string and integration tests and their overall status and testing dates. The Traceability Matrix should be referenced. Prepare for Cutover. Describe the activities to bring the system live and transition the business. Include an approach for a dry-run of system cutover process and deployment team activities.
Include the schedule of end user training courses, and specify the audience, when the training will take place and the location. System Retirement Strategy. Outline steps to be followed if the current system or function will be retired as a result of the successful completion of the current project.
0コメント