• Home
• Store
• Past Posts
• Articles
  • Asking for a pay rise
  • Resignation
  • Asking for a Promotion
  • Getting a Green Card
• Contact us
• search

Subscribe

By N2H

Reasons for decomposing a project

If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting and have a nice day!

Projects large or small are normally broken down into smaller manageable phases and various techniques are used in the process. Some of these techniques include work breakdown structure (WBS), network diagram, PERT/CPM which are important to project success. The merits of breaking projects into phases and applying the techniques mentioned above are:

Project Coordination in that it activities or work to be carried out is clearly identified, the people responsible for the activity are also identified, thus the project is easily and properly coordinated.

Breaking a project into manageable phases also helps in allocation of resources. The project manager will be able to know what resources are available, how to allocate these resources to the different activities to ensure that the project is delivered on time, on budget and produces the desired results.

Communication within the project is another merit of breaking down a project into smaller more manageable phases. It helps in ensuring proper communication within the project by identifying the information needs of the of the different project activities, the job that needs to be done and duration  and who needs to do the work.

Performance measuring is another merit of breaking a project into smaller phases because the project manager and sponsors are able to indicate at what points do they need to see deliverables and what kind of deliverables and it also enables the project sponsors to create a performance baseline by which to rate the project status, project success and the project team.

Breaking a project into manageable phases also helps in project scheduling i.e managing project time by ensuring project activities are scheduled, sequenced, and controlled  manner so as to ensure the project stays on schedule.

This approach was helpful in the organization where I used to work because the organization was small and the  resources were very limited especially technical resources for IT projects. This technique allowed us to plan the work of the IT department on a day to day basis and also allowed us to handle incoming projects and complete them successfully.

Techniques such as work breakdown structure was also important in  our other departments e.g maintenance department since they were overburden by many projects being carried out simultaneously within the hotel, WBS enabled them to plan and know when to send their staff to what projects and what activities where to be handled within the projects.

 

Comments

• Recent Posts

  • TCP vs UDP
  • Rootkits
  • SQL injection attack
  • Security policy: standards, guidelines and procedures
  • Symmetric key Vs Asymmetric encryption
  • Intrusion detection system Vs Intrusion prevention systems
  • Factors influencing FAR & FRR in Biometrics
  • Authentication methods
  • How project scope contributes to project success
  • Reasons for decomposing a project