Well-written project documentation clarifies intent, documents decisions and results, and allows project managers to assess project progress (and report it, as necessary, to project stakeholders) at e

CMGT/410 v19

Work Breakdown Structure (WBS) Example Well-written project documentation clarifies intent, documents decisions and results, and allows project managers to assess project progress (and report it, as necessary, to project stakeholders) at e 1

Project estimate: 124 hours: Small Business Website Development

1. Research – 16 hours

1.1 Competitive analysis – 6 hours (approver)

1.2 Build requirements – 10 hours (technical writer)

2. Design – 24 hours

2.1 Prototype #1

2.1.1 Create first version of prototype – 8 hours (graphic designer)

2.1.2 Gather feedback – 4 hours (approver)

2.2 Prototype #2

2.2.1 Create second version of prototype – 8 hours (graphic designer)

2.2.2 Gather feedback – 3 hours (approver)

2.2.4 Get approval to move forward with prototype – 1 hour (approver)

3. Program – 80 hours

3.1 Feature coding – 40 hours (programmer)

3.2 Integration coding – 20 hours (programmer)

3.3 Add content – 20 hours (content creator)

4. Test – 4 hours

4.1 Component testing – 2 hours (programmer)

4.2 Full site testing – 2 hours (approver)