The document outlines a work breakdown structure (WBS) for a project to develop a TrashTracker application. The WBS includes 5 main levels - initiation, planning, execution, control, and closeout. It details 20 specific tasks across these levels, assigning them to team members like the project manager, system analyst, UI/UX designer, software tester, and documentation. It also includes estimated durations for each task and identifies predecessor tasks.
The document outlines a work breakdown structure (WBS) for a project to develop a TrashTracker application. The WBS includes 5 main levels - initiation, planning, execution, control, and closeout. It details 20 specific tasks across these levels, assigning them to team members like the project manager, system analyst, UI/UX designer, software tester, and documentation. It also includes estimated durations for each task and identifies predecessor tasks.
The document outlines a work breakdown structure (WBS) for a project to develop a TrashTracker application. The WBS includes 5 main levels - initiation, planning, execution, control, and closeout. It details 20 specific tasks across these levels, assigning them to team members like the project manager, system analyst, UI/UX designer, software tester, and documentation. It also includes estimated durations for each task and identifies predecessor tasks.
Aqilah Putri Alifah (1203210049) Dara Ilma Deudoena (1203210063) Nabila Pangastuti (1203210037) Nadine Fatimah Az Zahra (1203210008) Arviasotya Aghna Nareswa (1203210051) Work Breakdown Structure ( WBS )
LEVEL 1` LEVEL 2 LEVEL 3 PIC DURATION PREDECESSOR
1.1.1 Evaluation & Recommendation Project Manager 2 - (A) 1.1 1.1.2 Determine Project Team (B) Project Manager 2 A Initiation 1.1.3 Develop Project Charter (C) Project Manager 3 B 1.1.4 Project Charter Approved (D) Project Manager 1 C 1.2.1 Project Team Kickoff Meeting ALL 1 C 1.2 (E) Planning 1.2.2 Develop Project Plan (F) ALL 2 E 1. Aplikasi TrashTracker 1.2.3 Submit Project Plan (G) ALL 1 F 1.3.1 Create an SRS document that defines the software requirements System analyst 10 F specification. (H) 1.3 1.3.2 Define existing procedures in System analyst 10 F Execution the system. (I) 1.3.3 Create flow documents, flow System analyst 5 I systems. (J) 1.3.4 Create User Persona (K) System analyst 3 J 1.3.5 Analyze suitable design UI/UX Designer 1 K methods (L) 1.3.6 Creating the interface of the UI/UX Designer 20 L system (M) 1.3.7 Prototype the application (N) UI/UX Designer 5 M 1.3.8 Create a test plan for system Software tester 5 N implementation. (O) 1.3.9 Control alignment and System 1 O completeness of all documents. (P) Documentation 1.3.10 Create a software user guide System 3 P information systems. (Q) Documentation 1.4.1 Project Management Project Manager - - 1.4.2 Project Status Meetings Project Manager - - 1.4 Control 1.4.3 Risk Management Project Manager - - 1.4.4 Update Project Management Project Manager - - plan 1.5.1 Audit Procurement Project Manager - - 1.5.2 Document Lessons Learned ALL - 1.5 1.5.3 Update Files/Records ALL - Closeout 1.5.4 Gain Formal Acceptance (R) Project Manager 3 Q 1.5.5 Archive Files/Document (S) Project Manager - A-R