A projects Work Breakdown Structure (WBS) and Gantt chart provide structure for a project. In this weeks assignment you develop both the WBS and Gantt chart for a fictitious organization. The Manage Your Health, Inc (MYH) scenario will be used in the weekly assignments for the rest of the course.

Review the Manage Your Health Scenario and follow the directions below for completing a WBS and Gantt chart.

Develop a work breakdown structure (WBS) for the project. Break down the work to Level 3 or Level 4 (do this for more than just one task), as appropriate. (pay attention to this, many skip this piece!)

Use the Work Breakdown Structure Template and Work Breakdown Structure example in this text as guides. (NOTE: these are guides and examples, make sure you create your own, original work here!)

Upload the WBS in list form. The WBS should be based on the information that would be in a project scope of this scenario. You can review your project plan from Week 1.

Create a Gantt chart using the WBS you developed

ulds Dala Review View Tell me X Calibri (Body) v 12 ' V = E a Wrap Text General Paste B I UB av Av Merge & Center $ % , N12 Xv fox D E F H 1 G Predecessors J K L Resources 1 2 3 Project manager Project manager/team members Project manager/team members Project manager Project manager/team members 6 7 Project manager 10 11 Project manager/team Project manager Project manager A A B C 1 Task Duration 2 MYH application 6 months 3 Planning 2 months 4 Analyze app 1 week 5 Meet stakeholders 4 days Defin 6 Define scope 1 week 7 Set goals for project 2 days Date 8 Determine deliverable 2 weeks 9 Create schedule 2 weeks 10 Coming up with estimate 1 day 11 Assign task 5 days 12 Risk assessment 2 days 13 Planning complete O days 14 Designing app features 2 months 2 15 Write down functions 2 weeks 16 research competitors 1 week 17 develop app for particular OS 1 week Drag and drop app builder 2 weeks 19 Figure out language to us 1 week 20 develop app 1 week 21 Testing 2 month 22 internal testing 1 month 23 External testing 1 month 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 13 Development team Customers/employees After doing this proiect, I realized waterfall mythology is the best method for me. It is easier for me to follow though, especially being that you can't move on to the next project at the prur I believe with an application you can't really move to the next project anyways until the previous is done An example can be coding. If you code on the app and it's an error, you won't be able to move on to the The project manager is responsible for planning out the project, organizing and directing until complete The project sponsor is responsible for many things in this aspect, this includes initiating success of the pr , The business analysis basically bridge the gap between IT and the business side of the company This is done from them using data analyties to access process. The preram manager overseas everything in the business They're responsible for coordinating many activities to different projects. This can happen without program Shoot1 + Ready no doo # % & $ 4 2 3 5 6 7