By the
Mind Tools
Editorial Team

Scheduling Simple Projects

© iStockphoto

Take simple steps to reach your goal.

Simple projects involve only one or a few people over a short time. Typically, simple projects will have few tasks dependent on other tasks, and will be relatively straightforward and easy to coordinate. Examples might be coordinating delivery of resources for a workshop session, implementing a small marketing plan, or delivering a simple software enhancement.

With simple projects, tools like Gantt Charts and Critical Path Diagrams may overcomplicate project scheduling and communication. Unless project team members are trained in their use, they can often 'blind people with science', leading to poor communication and muddled projects.

Appropriate timetables and Action Plans are often sufficient to coordinate and implement simple projects. These should be explained and negotiated with project staff to improve the plans and get staff understanding, input and buy-in.

Finding This Article Useful?

You can get 79 more project management resources like this by joining the Mind Tools Club.

Find Out More

It will often be enough to create a workback schedule, starting from the date by which the project must be completed, and listing all of the tasks in reverse order with due dates for each.

Key Points

Simple projects are often best run using simple timetables and Action Plans. These should be prepared and negotiated with project staff to improve plans and get buy-in.

During the project these will contain sufficient control points and deliveries to monitor project progress and take any appropriate remedial action.

This site teaches you the skills you need for a happy and successful career; and this is just one of many tools and resources that you'll find here at Mind Tools. Subscribe to our free newsletter, or join the Mind Tools Club and really supercharge your career!

Add this article to My Learning Plan
Comment (1)
  • Over a month ago Dianna wrote
    When a project is small or reasonably simple it's tempting to just dive in without a real plan. You figure the time you spend planning could be better spent "doing". If however you take just a bit of time upfront to plan your approach and make sure you have the resources and support required, the end result will be that much more satisfactory and there will far fewer glitches along the way. It seems that when I've neglected to plan is when the most issues arise so I've learned the hard way that it doesn't pay off to cut corners no matter how small the project.