A project plan is a document created at the beginning of the project lifecycle that gives stakeholders and everyone else involved a clear idea of what the project will entail in terms of effort, time, cost, and anticipated results.

The methodology or approach the project manager plans to use to manage the project must be identified before the project plan can be created. Choosing a methodology is important because a methodology provides the frameworkthat is, an overall process and suggested documents and deliverablesthat will guide project development from beginning to end. Some project methodologies are more appropriate for some types of projects than for others.

Over the next few weeks you will develop pieces of a project plan. This week you will determine your methodology based on project requirements and the components needed in your plan.

Read the Manage Your Health Inc. Case Study and complete the assignment below.

(Manage Your Health, Inc. (MYH) is a Fortune 500 company that provides a variety of healthcare services across the globe. MYH has more than 20,000 full-time employees and more than 5,000 part-time employees. MYH recently updated its strategic plan; key goals include reducing internal costs, increasing cross-selling of products, and exploiting new Web-based technologies to help employees, customers, and suppliers work together to improve the development and delivery of healthcare products and services. Below is an idea the IT department has developed for supporting these strategic goals:

Recreation and Wellness Intranet Project: Provide an application on the current intranet to help employees improve their health. A recent study found that MYH, Inc. pays 20 percent more than the industry average for employee healthcare premiums, primarily due to the poor health of its employees. You believe that this application will help improve employee health within 1 year of its rollout so you can negotiate lower health insurance premiums, providing net savings of at least $30/employee/year for full-time employees over the next 4 years. This application would include the following capabilities:

• Allowing employees to register for company-sponsored recreational programs, such as soccer, softball, bowling, jogging, and walking
• Allowing employees to register for company-sponsored classes and programs to help them manage their weight, reduce stress, stop smoking, and manage other health-related issues
• Tracking data on employee involvement in these recreational and health-management programs
• Offering incentives for people to join the programs and do well in them (e.g., incentives for achieving weight goals, winning sports team competitions, etc.)

Assume that the project will take 6 months to complete and cost about $200,000.)

Consider the differences between Agile and waterfall.

Select 1 methodology to use for a project plan for this initiative.

Create a simplified project plan such as the examples listed in the Tips section below. Include, at least, the following criteria:

• Name of task
• Duration
• Predecessors
• Notes

After completing your simplified project plan, write a 175-word paragraph and complete the following:

• Define which methodology, Agile or waterfall, is most appropriate for this project. Why? Cite at least 2 sources to support your rationale.
• Describe the following roles for this project: project manager, project sponsor, business analyst, and scrum master or program manager.

You may create your simplified project plan using MicrosoftExcelor another software application of your choice.

• Researchadditional project plan examples online.
• Consider the application characteristics and requirements when building your project plan. For example, the app will require a search feature so employees can search for available programs, will require security to protect personal information, etc., which will help with the Work Breakdown Structure (WBS). Note: This information will be helpful in the Wk 2 Apply: Work Breakdown Structure assignment. implemented as MicrosoftExcelspreadsheets:

G Notes 2/1/2016 2/1/2016 2/3/2016 2/9/2016 2/9/2016 2/10/2016 2/10/2016 2/10/2016 2/10/2016 2/10/2016 2/10/2016 2/10/2016 2/12/2016 2/16/2016 2/17/2016 2/26/2016 B Duration 34 days 7 days 2 days 4 days 1 day 0 days 6 days 0.5 days 0.25 days 0.25 days o days 5 days 2 days 2 days 1 day 1 day 1 day 15 days 0.5 days 0.25 days 0.25 days o days 7 days 2 days 2 days 2 days 1 day 1 day 7 days 0.5 days 0.25 days 0.25 days O days 6 days 2 days 2 days A 1 Name 2 Mobile app plan 3 Project set-up 4 Define project processes 5 Set up working environment 6 Determine initial sprint velocity 7 Project setup complete 8 Sprint 1 UI 9 Sprint 1 plan 10 Select sprint 1 user stories 11 Assign user stories 12 Sprint 1 plan complete 13 User Interface 14 Design User Interface 15 Build User Interface 16 Test User Interface 17 UAT of UI 18 Correct Issues From UATUI 19 Sprint 2 reports 20 Sprint 2 plan 21 Select sprint 2 user stories 22 Assign user stories 23 Sprint 1.1 plan complete 24 Client Specified Reports 25 Design Reports 26 Build Reports 27 Test Reports 28 UAT of Reports 29 Correct Issues From UAT of Reports 30 Sprint 3 Platform 31 Sprint 3 plan 32 Select sprint 3 user stories 33 Assign user stories 34 Sprint 3 plan complete 35 Cross Platform Support 36 Design Cross Platform Support 37 Build cross platform Sunnort D Predecessors Resources 3/17/2016 2/9/2016 2/2/2016 project manager, product owner 2/8/2016 3 technical administrator 2/9/2016 4 lead developer 2/9/2016 5 2/17/2016 2 2/10/2016 2/10/2016 product owner 2/10/2016 9 product owner, lead developer 2/10/2016 10 2/16/2016 2/11/2016 UX developer 2/15/2016 13 UX developer 2/16/2016 14 test engineer 2/17/2016 12 test engineer, product owner 2/26/2016 25 UX developer lead developer 19 lead developer 20 2/18/2016 2/18/2016 2/18/2016 2/18/2016 2/18/2016 2/18/2016 2/22/2016 2/24/2016 2/29/2016 3/8/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/3/2016 2/18/2016 2/18/2016 2/18/2016 2/18/2016 2/26/2016 2/19/2016 2/23/2016 2/25/2016 2/29/2016 3/8/2016 3/9/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/8/2016 3/2/2016 3/4/2016 reporting developer 23 reporting developer 24 test engineer 22 test engineer, product owner reporting developer 17 lead developer 30 lead developer 31 technical administrator 34 technical administrator G Notes 2/1/2016 2/1/2016 2/3/2016 2/9/2016 2/9/2016 2/10/2016 2/10/2016 2/10/2016 2/10/2016 2/10/2016 2/10/2016 2/10/2016 2/12/2016 2/16/2016 2/17/2016 2/26/2016 B Duration 34 days 7 days 2 days 4 days 1 day 0 days 6 days 0.5 days 0.25 days 0.25 days o days 5 days 2 days 2 days 1 day 1 day 1 day 15 days 0.5 days 0.25 days 0.25 days o days 7 days 2 days 2 days 2 days 1 day 1 day 7 days 0.5 days 0.25 days 0.25 days O days 6 days 2 days 2 days A 1 Name 2 Mobile app plan 3 Project set-up 4 Define project processes 5 Set up working environment 6 Determine initial sprint velocity 7 Project setup complete 8 Sprint 1 UI 9 Sprint 1 plan 10 Select sprint 1 user stories 11 Assign user stories 12 Sprint 1 plan complete 13 User Interface 14 Design User Interface 15 Build User Interface 16 Test User Interface 17 UAT of UI 18 Correct Issues From UATUI 19 Sprint 2 reports 20 Sprint 2 plan 21 Select sprint 2 user stories 22 Assign user stories 23 Sprint 1.1 plan complete 24 Client Specified Reports 25 Design Reports 26 Build Reports 27 Test Reports 28 UAT of Reports 29 Correct Issues From UAT of Reports 30 Sprint 3 Platform 31 Sprint 3 plan 32 Select sprint 3 user stories 33 Assign user stories 34 Sprint 3 plan complete 35 Cross Platform Support 36 Design Cross Platform Support 37 Build cross platform Sunnort D Predecessors Resources 3/17/2016 2/9/2016 2/2/2016 project manager, product owner 2/8/2016 3 technical administrator 2/9/2016 4 lead developer 2/9/2016 5 2/17/2016 2 2/10/2016 2/10/2016 product owner 2/10/2016 9 product owner, lead developer 2/10/2016 10 2/16/2016 2/11/2016 UX developer 2/15/2016 13 UX developer 2/16/2016 14 test engineer 2/17/2016 12 test engineer, product owner 2/26/2016 25 UX developer lead developer 19 lead developer 20 2/18/2016 2/18/2016 2/18/2016 2/18/2016 2/18/2016 2/18/2016 2/22/2016 2/24/2016 2/29/2016 3/8/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/3/2016 2/18/2016 2/18/2016 2/18/2016 2/18/2016 2/26/2016 2/19/2016 2/23/2016 2/25/2016 2/29/2016 3/8/2016 3/9/2016 3/1/2016 3/1/2016 3/1/2016 3/1/2016 3/8/2016 3/2/2016 3/4/2016 reporting developer 23 reporting developer 24 test engineer 22 test engineer, product owner reporting developer 17 lead developer 30 lead developer 31 technical administrator 34 technical administrator