Project planning and preparing Simple Projects
 
Simple projects will have few tasks dependent on other tasks, and will be relatively simple and easy to coordinate. Simple projects involve only one or a few people over a short time. There are many examples for it. These examples might be coordinating delivery of resources for a workshop session, implementing a small marketing plan, or delivering a simple software enhancement.
 
The project team members are to be trained in the use of Gantt Charts and Critical Path Diagrams. Otherwise, it may lead to poor communication and muddled projects. And sometimes, these tools may overcomplicate project scheduling and communication. 
 
Applying the device:
 
 
1. Suitable Timetables and Action Plans are sufficient to synchronize 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.
 
2. It is enough to create a work back 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.
 
3. Ensure that you have agreed its scope with its sponsor (the person who wants it done) before you start planning whatever the size of your project. This will help you to resist changes to its scope (known as "scope creep"), which will seriously affect your plans, once you have started working.

Conclusion 
 
Simple projects are 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 corrective achievement.