[Name]

[Class]
[Professor]
September 19, 2015
WORK BREAKDOWN STRUCTURE (WBS)
1. Create a Work Breakdown Structure (WBS) that lists all tasks required
for this project. Provide four levels of detail.
Below is the Work Breakdown Structure that lists all tasks required for the
Windows 7 Upgrade Project. Four levels of detail are demonstrated in the WBS as
instructed.
WINDOWS 7 UPGRADE PROJECT: UPGRADE 200 DESKTOPS IN THE
COMPANY TO WINDOWS 7
1.1. Initiating
1.1.1 Select project manager
1.1.2 Form project team
1.1.3 Develop project charter
1.2. Planning
1.2.1 Develop scope statement
1.2.2 Create a Work Breakdown Structure
1.3. Executing
1.3.1 Concept
1.3.1.1 Define minimum requirements for system upgrade
1.3.1.2 Evaluate current systems
1.3.1.3 Develop project plan
1.3.1.4 Brief Windows 7 upgrade team
1.3.2 Roll Out
1.3.2.1 Migrate users contents
1.3.2.2 Perform system backup
1.3.2.3 Install Windows 7 operating system
1.3.3 Technical Support
1.4. Monitoring and Controlling
1.4.1 Monitor system stability
1.4.2 Test systems periodically
1.5. Closing
1.5.1 Summarize total actual costs
1.5.2 Measure project benefits
Describe best practices in general for constructing a good WBS
After doing thorough research on the issue, I have discover several significantly
noteworthy practices in general for constructing a good WBS. First of all, the
work breakdown structure should be exhaustive. In other words, all deliverables,

including both internal and external deliverables should be noted in the WBS. As
the main purpose of the WBS is to help monitor a projects progress and results,
the inclusion of all deliverables will hep facilitate the control of the project.
Secondly, a WBS should be composed of deliverables instead of merely
chronological events. Essentially, the WBS should not be mistaken with a
chronological to-do list. The emphasis of a WBS is a projects deliverables, not
chronological events. Still, the WBS could be effectively constructed in a timebased manner using the project management process groups of initiating,
planning, executing, monitoring and controlling, and closing.
Thirdly, a WBS should be a product of collaboration among team members.
Preparing the WBS together will motivate the project team members to build
responsibility and commitment, actively participate and communicate among the
team while ensuring consistency during the execution of the project. Finally, a
work breakdown structure should be flexible and accommodate inevitable
changes that may occur during the execution of the project.