Project Risk Assessment

profileJohn_matt
teams_wbs_document.docx

Executive Summary

This WBS is a detailed plan covering the analysis, planning, installation, operation, and maintenance of the information technology (IT) infrastructure for Dr. Bob Marley’s dental practice. This WBS will be tracked through the completion of major milestones. This documentation also includes a schedule that gives a timeline of work to be done each week and for every task within the project scope. A full understanding of the project’s cost and performance measures by the project team and the client are quintessential, and clarification will be provided when necessary. The planned schedule and milestones are provided within. The WBS will convert many complex requirements into smaller, more manageable pieces for accurate project estimation, planning and execution.

ITP-3 Questions - WBS Dependencies

1. Did your team discuss and/or divide up the major tasks before completing the individual WBSes?

The team did discuss the major tasks. This was done so as to get an understanding as to the subtasks that are be undertaken within the major tasks. It is always important to do the divisions to avoid cases of jammed up activities. The individual WBSes are important to the progress of the entire project as it does ensure that the sequential progress of the entire project. The subtasks are therefore a continuation of the work to be carried out. The WBS provides a structural view into the project and it is essential to develop the project schedule (ProjectManagementDocs.com, 2015).

2. How did your team “merge” the WBSes of individual teammates?

In order to merge the various WBSes of the individuals within the team, it was important to first of all check through the various tasks that each individual has presented. In so doing, the team identify the ground level tasks that moved throughout the entire project. After this was done, the team reviewed the tasks to ensure that they had all the tasks necessary for the purposes of completion of the project. The team did ensure that the tasks within the projects were in line with the needs of the client.

3. Were some teammates’ WBSes more thorough or complete than others?

Yes. This did happen. Some of the teammates’ WBSes were more thorough and received better scores as they did include more tasks. They did have a better grasp and detailing as to what the project entails. They had a deeper grasp as to the needs of the client. These ranged from the time allocated to each and every task. This narrows down to how fast the tasks are to be completed and on how the dependencies were espoused.

4. What was the most difficult part of this assignment?

The most difficult part of the entire assignment is on finding the right way of linking the various tasks. This is made difficult due to the fact that most of the subtasks could be done concurrently within the same structure. Another difficulty in creating an MS project WBS lies in coming up with the various tasks and making proper estimations on durations, however, the WBS has enormous strength and influence to convert complex requirements/scope into smaller pieces for project estimation, planning and execution (Murthy, 2014).

5. Did every teammate contribute to this WBS effort?

Each and every team member did contribute to the overall creation of this project. This was done in various ways. Firstly, the team members did agree within themselves to ensure that they all had a sketch of what the project requires. The team members all created individual WBSes and were greatly involved in sieving through them so as to get the final WBS.

6. Is your team still following the day-to-day schedule provided in the TPP-1?

Yes, the team is still following the schedule. The schedule does enable the team to follow through on our process plan and keep up with the many tasks from week to week. The schedule also ensures that all tasks are completed.

References

Project Management Docs. (2015). Work Breakdown Structure (WBS). Retrieved from http://www.projectmanagementdocs.com/project-planning-templates/work-breakdown-structure-wbs.html#axzz3zXXQBvAz

Murthy, A. (2014, June 17). Using Work Breakdown Structure (WBS) for Effective Project Estimation. Retrieved from https://www.projecttimes.com/articles/using-work-breakdown-structure-wbs-for-effective-project-estimation.html