« How to Build a Great Team
Beware of the Entitlement Fungus »

How To Prepare an Effective Daily Project Execution Plan

July 26, 2011 | Author: PM Hut | Filed under: Project Plan Development

How To Prepare an Effective Daily Project Execution Plan
By Atul Gaur

Importance of planning: A Project Manager needs to plan all the activities required to achieve project deliverables. The latest project planning software are a handy tool and can accommodate a never-ending list of activities. At times a Project Manager is required to have better skills in handling information generated by these software rather than demonstrate his core project management skills. These project management tools if used to generate just the required data in order to plan activities for the next day or two can make project execution more effective. A short duration plan with limited amount of data can make life simpler for any Project Manager. This article intends to guide Project Managers in preparing a daily plan that can help them take control of activities and channelize their efforts in meeting the milestones or project deliverables.

What is a Daily Plan? A daily plan is a consolidated list of activities and should be prepared at least a day in advance for the next day. It should include activities that are planned for the day, and are part of the baseline project plan; it should also include the list of activities that are a result of changes in project scope or backlogs. At this stage, the activities should be further broken down into smaller (measurable and quantifiable) tasks to have a better degree of control on the activities. Breaking the activity to smaller set of tasks will also help in better allocation of resources. Always start with the next most important milestone and work towards its accomplishment.

What should the daily plan include? The daily plan should include the following set of activities:

  • List of activities currently in progress
  • List of activities scheduled for commencement as per the updated project schedule
  • List of activities scheduled for completion as per the updated project schedule
  • Person responsible to achieve the target
  • List of activities that require coordination with other agencies/stakeholders
  • A measurable, quantifiable target against each activity
  • The status of the activity (whether achieved or not)
  • Reasons for not being able to achieve the planned target for the day

Review the plan: The daily plan should be prepared a day in advance and reviewed before implementing it. The review process should include the project team members, contractors, and supervisors who would be actually implementing the task. It is a good practice to consider the availability schedule and the resource calendar in order to stream line the plan. If an activity requires a linked coordinating activity and if it has not been carried out, it is advisable to include the coordinating task and not the actual task. For example if a weld setup has to be inspected by a third party quality inspector and he has not been informed, it is likely that he may not turn up and carry out the activity as per the plan. Such coordination tasks are generally not captured during the activity list development process and the daily planning is a good platform to incorporate such activities.

Implement the plan: The Project Manager should make use of the data filtering capabilities of the project management software or add a custom filter to automate the process. All team members should be informed about the plan by conducting a meeting; individual copies should be handed over or sent by email. The Project Manager’s ability to use database or spreadsheet can create wonders. Daily planning also increases the involvement of the people and makes them feel responsible for the project.

The Project Manager should brief his team early in the morning and reiterate the salient aspects of the plan. The Project Manager should dedicate time to personally monitor the activities and instruct the team members to tell him if any scheduled task is not being implemented as per plan. It is a god practice for any Project Manager to check the implementation of the plan at regular intervals. If the number of daily activities is large it can be delegated to the next most influential person in the team.

At the end of the day the Project Manager should review the plan with his team members. During the review process the actual state of the activities should be recorded and reasons for not being able to complete the task should be ascertained and recorded in the daily planning register/database. Any incomplete task should be incorporated in the next day’s plan or scheduled for a later date after analyzing the reason for non-completion.

Challenges during the implementation phase: This methodology is a test of leadership skills of any Project Manager. It is likely that project team members may be the first ones to oppose such a move. I did face a serious opposition while implementing the daily planning technique in a recently concluded project. The opposition could be on various grounds and it is Project Manager’s responsibility to prove the efficiency of the system. I had to personally demonstrate this methodology and proved it with data that if the daily plan is not implemented on a regular basis the backlog of activities increases and activity completion rates drops drastically.

Advantages: The practice of generating the daily plan can throw up some interesting data on various tasks, resources and even the individuals responsible for the targets. It can give reasons for not meeting the targets and they could be anything like delay in receipt of material, receipt of wrong material, lack of coordination, poor/lack of understanding of the design drawings or product specifications. It can also generate interesting data on rework and the database can be helpful in conducting re-work analysis. The Project Manager can use this data to better track his project. The methodology provides a greater visibility of information to the project team by giving details of what needs to be done the very next day and gives a better degree of control over the project as a whole.

Analysis of the data: The next most important step is analysis of the data generated by this process. Analysis of the data helps to streamline the efforts of a Project Manager. He gets inputs to channelize his resources in areas that are lagging behind. Some simple quantitative tools like pareto analysis can help in understanding the reasons for delay. Simple graphs like planned activities vs completed activities can display visual results of the activities that are lagging behind and that need to be expedited in order to achieve completion targets. Analysis can also set a benchmark on of number of activities that needs to be completed each day. A deeper drill down of data can reveal the exact reasons so as to why the daily targets cannot be achieved and their (their refers to the reasons) frequency of occurrence. The Project Manager can then develop a strategy to minimize the number of ‘No’ against each activity in the daily plan

Conclusion: Planning efforts never go to waste. A detailed project execution plan that is prepared and adhered to while keeping the overall schedule in mind can generate wonderful results for the project, professional satisfaction for the team members, and guaranteed ROI for the stakeholders.

Atul Gaur has aggregated over twelve years of professional experience and devoted more than ten years in the field of Project Management. He’s a Mechanical Engineering graduate from Manipal Institute of Technology (Manipal) and has Operations Management qualification from Management development Institute in Gurgaon. You can read more from Atul on his blog.

Share this article:
  • Digg
  • del.icio.us
  • Facebook
  • Google
  • blogmarks
  • LinkedIn
  • Reddit
  • StumbleUpon
  • TwitThis
  • Yahoo! Buzz

This entry was posted on Tuesday, July 26th, 2011 and is filed under Project Plan Development. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

No comments yet.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

The Stevens Enterprise Project Management Master's Program

Project Management Categories