Brigitte Werfel November 6, 2020 Project Management
A project in general is divided into many phases depending on the life cycle model used for it. In general, the methodology deals with the genesis of a scheme, controlling it and termination of the plan! Where it all begins! An organization begins on a project, by getting down the objectives of the customer. The requirement gathering report should be as unambiguous as possible. You do not want to give a two-story house when the client had actually asked for two storerooms in the house! Get the deal straight! Then a mandate is provided to the client, which is an official document stating the needs of the customer, for their verification.
An implementation can be a tough animal to tame depending on how you structure it. Having the right tools and methodology behind you to define and run a project can go a long way towards a successful deployment or development effort. Since a project can span several months and involve a variety of resources and skill sets, your role as a PM is to define the rules and manner in which the team will work under so the entire implementation does not falter.
The project schedule is the central part of the project plan and it is used to connect the tasks to be done with the resources that will accomplish them. It consists of a list of deliverables with intended start and finish dates. Deliverables are the lowest level elements in a schedule, which are not further subdivided.
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 team members often feel overwhelmed with the prospect of having to worry about timelines and tasks they need to accomplish over the duration of the work effort. Helping them to stay focused and organized is a key skill that a PM must bring to the table when running a project.
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.