Once you have your project plan as a visual, communicate it regularly with your team, and make adjustments. The easiest way to do this and to see dependencies is to visualize them by creating a simple schedule in Excel or PowerPoint as shown in the example above. In the above example we can do the Workflow Planning Task simultaneously with the Installation Task, but we cannot start the Set-up Task until the Installation has been complete. It will be important to get the sequence of your tasks in the right order. Below is an example of our project plan for implementing a new ticketing system by September 30th. The end result will be a visual project plan that has been well communicated. Through that review process you will update your plan’s dates and dependencies based on resources, commitments and other variables. The chart you create will not be the final project plan, rather it will be the initial plan that you begin reviewing with stakeholders and your team. You can use Office Timeline as a planning tool to do this. Once you have completed the task dates, start adding dates for the sub-tasks. Starting with the kick-off date, begin adding dates for each task based on the estimated task duration. Work breakdown table Work breakdown chart Create a visual draft of your plan The tasks you identify will be used to create a visual project plan. Most often this is done on a list, but it can be more effective if you prepare something easier to visualize, such as putting your list into a table view or creating a work breakdown chart. Begin to decompose this deliverable into smaller more manageable tasks and further into subordinate tasks depending on complexity. Identify your major strategic deliverable that achieves the objective, in our case it is: implementing a new ticketing system. The objective does not describe your deliverables but it will help you define them, which is the next step. For example: The objective of this project is improving our average tech-support response time to under 1 hour, for all existing customers, by implementing a new ticketing system by September 30th. They are measurable and dead-lined statements that capture what the project is trying to achieve. Objectives are specific to Project Managers. Get clear around your project’s objective Your project may be one of many others that are collectively working towards achieving this bigger business goal, however, it is important to understand them because the goal will be a reference to the objective of your project. The goal of this project is to increase the product satisfaction level for all of our existing customers. Goals are un-measurable business statements that also define a benefit, for example: They are typically created as high-level business statements that give a PM perspective for what the project is trying to achieve. Goals are determined in the initial phase by management and stakeholders. Project managers need to understand the goals of the project they are executing. Here is a practical approach for creating a visual project management plan. If you have authorization to proceed and budget, the next step is to plan the project’s course. The project planning method need not be process-centric and document heavy. become the default reference document for all stakeholders.be the baseline to measure progress against.provide a sequence for delivering each part of the project.establish a timeline with deadlines for each part of the project.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |