0% found this document useful (0 votes)
15 views1 page

Project Network Diagram

The document outlines a project for the website redesign of XYZ Corp, detailing the work breakdown structure with specific activities and their durations. Key activities include gathering requirements, creating wireframes, developing backend and frontend, conducting tests, and deploying the website. The critical path for the project is identified, emphasizing the sequence of essential tasks required for timely completion.

Uploaded by

ka085872
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views1 page

Project Network Diagram

The document outlines a project for the website redesign of XYZ Corp, detailing the work breakdown structure with specific activities and their durations. Key activities include gathering requirements, creating wireframes, developing backend and frontend, conducting tests, and deploying the website. The critical path for the project is identified, emphasizing the sequence of essential tasks required for timely completion.

Uploaded by

ka085872
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

1. Project Name: Website Redesign for XYZ Corp.

2. Work Breakdown Structure (WBS) Activities:


- 2.1.1: Gather requirements (Duration: 5 days)
- 2.2.1: Create wireframes (Duration: 7 days)
- 2.2.2: Develop mockups (Duration: 6 days)
- 2.3.1: Develop backend (Duration: 10 days)
- 2.3.2: Develop frontend (Duration: 8 days)
- 2.4.1: Conduct unit tests (Duration: 4 days)
- 2.4.2: Conduct user acceptance tests (Duration: 5 days)
- 2.5.1: Deploy website (Duration: 3 days)
- 2.5.2: Monitor website (Duration: Ongoing)
3. Sequencing:
- 2.1.1 (Gather requirements) → 2.2.1 (Create wireframes) → 2.3.1 (Develop
backend)
- 2.3.1 → 2.4.1 (Conduct unit tests)
- 2.3.2 (Develop frontend) → 2.4.2 (Conduct user acceptance tests)
- 2.4.1 → 2.5.1 (Deploy website)
4. Critical Path:
- 2.1.1 → 2.2.1 → 2.3.1 → 2.4.1 → 2.5.1

You might also like