Advanced Coaching

To utilise advanced coaching tools and methods.

Coach effectively.

When task dependencies are identified, can they be automated to alert you during the project when they are completed or if they’re not progressing as planned?

As you begin to build your project plan you need to define a number of things to give you a clear picture of what it is you’re planning to do:

  1. Determine the project scope: It sets up the boundaries of the project and the responsibilities of each team member. It does this by determining and documenting specific project goals, deliverables, features, functions, tasks, deadlines and costs.
  2. Identify tasks milestones: tasks are small jobs that make up the project, while a group of related tasks in the project that signal the end of a project phase are called milestones. These milestones, indicated as diamond-shaped icons on your schedule, help you further break down the larger project into more manageable pieces.
  3. Quantify your effort: figure out how much of something you’ll need. You need to estimate which resources and how much of them are going to be required when you’re making a plan to come up with a feasible budget.
  4. Allocate the resources: get the project planning tools, teams assembled, vendors, etc. This is where you begin to take the disparate parts of the project and organize them.
  5. Make a schedule: take the above data and put it on a timeline. Here is where you can lay out all the tasks and milestones that mark the different phases of the project.
  6. List dependencies: link tasks that rely on one another. Task dependencies are then identified and can be automated to alert you during the project when they are completed or if they’re not progressing as planned.
  7. Document everything: always keep a detailed paper trail. You want to have all the paperwork for each step of the project plan. That includes contracts and timesheets for your team. At the end of the project these documents will be crucial to closing the project correctly.

Remember, you have already created a business case, which offers a general view of the project. The project management plan is where you take that view and drill down in greater detail. This project plan is not something you write and are done with. You will be revisiting it throughout the life cycle of the project, referring and revising it as you execute that project.

  • Correct
  • Incorrect
  • Task dependencies cannot be automated
  • Task dependencies are unidentifiable