Week 4 assignment
josaca
week_3_assignment_1.xlsWBS Outline
| Work Breakdown Structure Outline | |
| Project Initiation | |
| 1.1 | Develop Project Charter |
| 1.2 | Define Scope |
| 1.3 | Define Requirements |
| 1.4 | Finalize Charter and Gain Approvals |
| 1.5 | Hold Review Meeting |
| 1.6 | Revise Project charter |
| 1.7 | Gain approvals |
| Planning | |
| 2.1 | Preliminary project scope development |
| 2.2 | Project Team Determination |
| 2.3 | Project Team meeting |
| 2.4 | Develop project plan, schedule, and budget |
| 2.5 | Submit project plan |
| 2.6 | Project plan approval. |
| Execution | |
| 3.1 | Project Team meeting |
| 3.2 | Assignment of Tasks |
| 3.4 | Area visits and tests |
| 3.5 | Design system |
| 3.6 | Procure the hardware and softwere needed |
| 3.7 | Testing phase |
| 3.8 | Install the live system |
| 3.9 | User Training |
| Control | |
| 4.1 | Initiate risks management strategies |
| 4.2 | Project evaluation |
| 4.3 | Project Status updates |
| 4.4 | Risk identification |
| 4.5 | Constant update of project plan |
| Close out | |
| 5.1 | Audit project |
| 5.2 | Document all the findings |
| 5.3 | Update files and all the relevant records |
| 5.4 | Gain formal acceptance |
| 5.5 | Archive all the files and documents related to the project |
Assignment One
| Activity Name | WBS ID | Name | Precedent Task | Start Date | Finish Date | # Days Duration | Resource | % Completion |
| Initiation | 1.1 | Develop project charter | 29-Mar | 30-Mar | 1 | 100 | ||
| 1.2 | Define Scope | 1.1 | 30-Mar | 30-Mar | 0.5 | 100 | ||
| 1.3 | Define Requirements | 1.2 | 30-Mar | 30-Mar | 0.5 | 100 | ||
| 1.4 | Gain Approvals | 1.3 | 31-Mar | 2-Apr | 3 | 100 | ||
| 1.5 | Hold Review Meeting | 1.4 | 3-Apr | 3-Apr | 1 | 100 | ||
| 1.6 | Revise Project charter | 1.5 | 3-Apr | 3-Apr | 0.5 | 100 | ||
| 1.7 | Gain approvals | 1.6 | 3-Apr | 4-Apr | 1 | 80 | ||
| Planning | ||||||||
| 2.1 | Preliminary project scope development | 1.6 | 5-Apr | 6-Apr | 1 | 0 | ||
| 2.2 | Project Team Determination | 2.1 | 6-Apr | 12-Apr | 7 | 0 | ||
| 2.3 | Project Team meeting | 2.2 | 14-Apr | 14-Apr | 0.5 | 0 | ||
| 2.4 | Develop project plan, schedule, and budget | 2.3 | 14-Apr | 14-Apr | 0.5 | 0 | ||
| 2.5 | Submit project plan | 2.4 | 14-Apr | 14-Apr | 0.5 | 0 | ||
| 2.6 | Project plan approval. | 2.5 | 14-Apr | 16-Apr | 2 | 0 | ||
| Execution | ||||||||
| 3.1 | Project Team meeting | 2.6 | 18-Apr | 18-Apr | 0.5 | Human assets | 0 | |
| 3.2 | Assignment of Tasks | 3.1 | 18-Apr | 18-Apr | 0.5 | Team members | 0 | |
| 3.3 | Area visits and tests | 3.2 | 19-Apr | 22-Apr | 4 | 0 | ||
| 3.4 | Design system | 3.2 | 19-Apr | 22-Apr | 4 | 0 | ||
| 3.5 | Procure the hardware and softwere needed | 3.2 | 19-Apr | 22-Apr | 4 | Finance | 0 | |
| 3.6 | Testing phase | 3.5 | 25-Apr | 29-Apr | 5 | 0 | ||
| 3.7 | Install the live system | 3.6 | 2-May | 4-May | 2 | 0 | ||
| 3.8 | User Training | 3.7 | 9-May | 13-May | 5 | Relevant workers | 0 | |
| Control | ||||||||
| 5.1 | Initiate risk management strategies | 2.6 | 18-Apr | 20-Apr | 2 | 0 | ||
| 5.2 | Project evaluation | 3.8 | 14-May | 17-May | 3 | 0 | ||
| 5.3 | Project Status updates | 2.6 | 18-Apr | 20-May | 32 | 0 | ||
| 5.4 | Risk identification | 2.6 | 18-Apr | 20-Apr | 2 | 0 | ||
| 5.5 | Constant update of project plan | |||||||
| Close out | ||||||||
| 5.1 | Audit project | 3.8 | 14-May | 16-May | 2 | 0 | ||
| 5.2 | Document all the findings | 5.1 | 16-May | 18-May | 2 | 0 | ||
| 5.3 | Update files and all the relevant records | 5.2 | 18-May | 19-May | 1 | 0 | ||
| 5.4 | Gain formal acceptance | 5.3 | 19-May | 20-May | 1 | Management | 0 | |
| 5.5 | Archive all the files and documents | 5.4 | 19-May | 20-May | 1 | 0 |
