Phase: Planning | Audience: Internal | Project: WEB-2026-01 Corporate Website Development
In simple words: The Work Breakdown Structure (WBS) breaks the whole project into smaller pieces of work called work packages, each with an owner and an effort estimate. The WBS Dictionary describes each package in detail.
Think of it like: Cooking a big dinner: instead of 'make dinner', you list starters, main course, dessert, and under each the dishes, who cooks them and how long they take.
When is it created? | Planning (9 Oct 2026) |
Who prepares it? | Project Manager with the team |
Who approves or uses it? | Part of the scope baseline |
What happens next? | Hours are costed in the Budget and dated in the Schedule |
Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.
Issued by: [Your Company] Technologies Pvt. Ltd.
Purpose: All project work broken into 5 phases and 20 work packages, with owner, output and effort for each. Total effort: 560 hours.
Item | Detail |
Document no. | WEB-2026-01/WBS |
Version | 1.0 |
Date | 9 Oct 2026 |
Owner | Project Manager |
Audience | Internal |
Phase | Planning |
Status | Approved |
WBS ID | Work package | Owner | Deliverable | Hours |
1 | Initiation and planning | 40 | ||
1.1 | Kickoff and charter | Project Manager | Charter, kickoff deck | 8 |
1.2 | Requirement study | Project Manager | Requirements summary | 14 |
1.3 | Sitemap and project plan | Project Manager | Sitemap, schedule | 18 |
2 | Design | 110 | ||
2.1 | Wireframes | UI/UX Designer | Wireframes for 7 page types | 30 |
2.2 | Home page visual design | UI/UX Designer | Home design, desktop and mobile | 30 |
2.3 | Inner page visual designs | UI/UX Designer | 6 page type designs | 35 |
2.4 | Revisions and design sign-off | UI/UX Designer | Signed design approval | 15 |
3 | Development | 280 | ||
3.1 | Environment and staging setup | Backend Developer | Staging site, Git repository | 20 |
3.2 | Theme development | Frontend Developer | Custom responsive theme | 120 |
3.3 | CMS configuration | Backend Developer | Page templates, custom fields, roles | 70 |
3.4 | Forms, analytics and integrations | Backend Developer | Working forms, GA4 events | 25 |
3.5 | Content upload and on-page SEO | Content Writer | All pages populated, SEO tags | 45 |
4 | Testing | 90 | ||
4.1 | Test planning and test cases | QA Tester | Test cases, UAT script | 15 |
4.2 | System and cross-browser testing | QA Tester | Test report | 35 |
4.3 | Bug fixing | Frontend Developer | Fixed defects | 30 |
4.4 | UAT support | Project Manager | UAT sign-off | 10 |
5 | Deployment and handover | 40 | ||
5.1 | Go-live deployment | Backend Developer | Live site | 18 |
5.2 | Training and user guide | Project Manager | Training, handover document | 12 |
5.3 | Hypercare (14 days) | Backend Developer | Support log | 10 |
Total | 560 |
WBS ID | Description | Acceptance criteria | Dependencies |
2.4 | Two rounds of consolidated client feedback on designs, then formal sign-off | Design Sign-off Form signed by Head of Marketing | 2.2, 2.3 |
3.2 | Build the custom WordPress theme from approved designs, mobile-first | Pages match designs at 360, 768, 1280 px | 2.4, 3.1 |
3.4 | Contact form with validation and email delivery; GA4 with enquiry event | Test submission reaches sales inbox within 1 minute | 3.1 |
3.5 | Upload client content, add titles, descriptions and alt text | All pages populated; SEO fields complete | 3.2, 3.3, client content |
5.1 | Deploy to production, switch DNS, verify SSL and forms | Go-live checklist complete | 4.4 |
Note: The WBS lists deliverables, not activities. The 100% rule applies: the 20 packages add up to all the work in the project, and nothing outside them is in scope.
WEB-2026-01/WBS · v1.0 · Internal. Bracketed items such as [Client Name] are placeholders.
Next lesson: 16. Project Schedule (Gantt)