Consolidated Project Plan

profileJohn_matt
itp-2i_-_wbs_wdurations.docx

MS Project: IT systems design

06/19/2016

Questions

1. All aspects of the WBS were included as outlined within the charter. This is in line with the promised deliverables for the said client. It is important to highlight that most of the deliverables revolve around the success of the IT system and in that respect, the outlines of the WBS are well in line with the deliverables. Most of the tasks in the WBS were not within the charter. These include aspects such as auditing protocol and the various determinations of hardware installations. The need for this is so as to ensure the scope is well outlined rather than leave project planning gaps.

2. The WBS does include various tasks that are important in addressing various management options. These include how to control, evaluate and manage the project as well as the project team. These help in ensuring that the project manager can have control as to the progress of the project and be in a position to analyse the various positions of the team members such as their moods.

3. A top-down approach usually does involve the formulation of the overview of the project. After this, the system is broken down to smaller categories which are to be followed to the letter until the completion of the particular project. A bottom-up approach involves the converse of the above. It does involve the knitting together of various components of a project in order to give the final and in most cases the complex version of the required result. The project in this particular exercise can be said to employ the use of the bottom-up approach as it involves the bringing together of design, installation, management, testing so as to ensure that the required IT system is completed.

4. Product-oriented WBS is basically one that is deliverable oriented. This can be seen in the case of the exercise herein as the WBS outlines what is to be done and thus has an inclination towards reaching particular objectives. A process-oriented WBS is modelled towards working on the various processes and subsequently outlining them in order to achieve the various deliverables of the project team.

5. I basically outlined the entire WBS on the MS Project and this remains the easiest way to input the tasks. It does allow for a direct establishment of the Gantt charts as well as making it absolutely easy to establish the project start date and task durations. I did not experience any challenges and thus did not have to rearrange the various tasks.

6. The approach was tabular; this makes it very easy to easily point out the tasks sequence. It is possible to have a WBS with all the tasks arranged in the form of an organisational chart. In this particular case, there is a hindrance. This hindrance arises from the lack in deliverables hence making it difficult to have a chart that will show all the task relationships.

7. I did work on my own in coming up with most of the major tasks. This was not a walk in the park by was hugely guided by knowledge in various IT systems as well as the outline of tasks to work around with that were provided in the instructions.