Chloe Boreham November 6, 2020 Project Management
In addition, the schedule provides project teams with a map for project execution and offers a baseline for tracking progress and managing changes. It can be used as a checklist to make sure that all necessary tasks are performed. If a task is on the schedule, the team is committed to doing it. In other words, the project schedule gives the means by which the project manager brings the team and the project under control. The visual representation of a schedule is a timeline chart. It is created such that it depicts the tasks of the projects, the duration and the sequencing of them, and the major milestones of the project. The Gantt chart is the most popular timeline chart.
A detailed schedule is one of the best tools that a project manager can have. By scheduling yourself in advance to do all of the necessary management tasks, you stay much more organized throughout your project. You know exactly what you need to do to get started, what you need to do for the planning stage, and so on. Plus, before you commence work on your project, you can ask yourself: how often do I want to meet with my team? how often do I want to conduct project reviews? and schedule yourself to do these periodic tasks.
The business requirements document should accurately, and in detail, describe the purpose of the project. It states what is needed to achieve that goal i.e. what is in-scope, what is out-of-scope, any assumptions that have been made, any constraints that have been imposed and expected timescales. The document will form the definitive description of the aims of the project and, as such, can be used to manage the expectations of the stakeholders. It will also include acceptance criteria that will ultimately be used to judge whether the project was a success.
Most larger organisations have well developed and run IT departments. They usually have formal project offices with established plan templates and standards, with project office staff and automated plan analysis systems (for example seeking orphan tasks / missing dependencies and so on to measure overall `plan quality`). Smaller organisations - for example, `IT solutions houses` - may lack this level of sophistication but will certainly use detailed project plans.
The production and agreement of the business requirements is a substantial part of the overall project schedule and may take many iterations before it is finally approved. The project manager usually works with other departments or teams to put the document together. They will probably use Brainstorming and Interviewing techniques to help with this process and may even build a prototype
To start we will be clear that we are not going to deal here with repetitive implementation / rollout projects where a template plan has been refined over a series of projects and becomes a standard checklist for project management (for example for COTS - commercial off-the-shelf software). This article is about those one off (or initial template try-out) projects. These projects may be within organisations small, medium and large.