Sometimes when projects are not complex you need a simple project plan to track the progress. This excel based template is easy to use and encompassed within a single tab.
|Simple Project Plan Template|
About the Simple Project Plan Template
- Template contains Task No, Task Description, Owner, Start, Finish, Progress, Status, Risks/Issues and Comments columns. All the columns are free text so they can be changed as and when needed,
- Task No should be sequential 1 for the main and 1.1,1.2,1.3 for sub tasks.
- Task Description can the task name. Use short informative descriptions. If you need more information you can add in the comments column.
- Owner can be the name of the person or the team who owns this task.
- Start and finish are self-explanatory.
- Progress should have a % complete for the task.
- Status is the what is the status of the task. I will suggest the following statues – On Track(Green), Concern(Amber), Delayed ( Red), Complete (Blue), Pending is white.
- Risks/Issues column should be used to document issues related to that task. As a thumb rule any task that is in Concern or Delayed status should have something in risks/issues column to explain why the task is the current status.
- The comments column can be used to provide basic information about the task. Examples like “Funding Approved by Finance”, “ Reminder sent” etc.
About the Example Software Development Project Plan
- The example project plan included with this article is a generic project plan which can be used for software development.
- The plan has been divided into several phases – Project Initiation, Analysis, Design, Development, Testing, User Acceptance, Deploy and Go Live.
- The project initiation phase covers all the tasks required to get the project started. Tasks likes business case approvals, funding approvals, resource planning, schedule planning and arranging kick of meetings.
- The analysis phase contains drafting business requirement, functional requirement and technical requirement specifications which are required to ascertain the scope. Walk through and sign off tasks are required to make sure that everyone is in on the same page.
- In the design phase it is generally the architect who comes with the high level and low level design document to address the function and technical requirements as specified in the analysis phase.
- In the development phase you would generally have tasks which will be meant to build the system. A developer will start with the development tasks and will do the unit testing. At the end of development before starting testing integration testing needs to be done.
- The main objective in the testing phase of the project is to make sure the software deliverable are of good quality. Testing in a project involves creating a test plan and test cases. Execute the test cases and record defects. There should be some time allocated to fix the defects and then retest the defects.
- User Acceptance phase is required to make sure that the software developed is in line with business acceptance. In the use acceptance phase(a.k.a UAT) the business users will create test cases and test the system. Generally, the UAT is not as elaborate the testing or QA.
- Deploy or also known as implementation phase is used to deploy the software that was built. It involves planning, practicing and deploying applications into live or production environments.
- Go Live the step where the system is live and is being monitored to see if any issues arise due the latest changes. After the go live the project can be formally closed.