The WBS from Payroll Project from Module 2 is attached.

Schedule Management Plan is needed based on your Payroll Project from Module 2.

A cost Management Planis needed based on your Payroll Project from Module 2.

Quality Management Planis needed based on your Payroll Project from Module 2.

The Project Plan Schedule is needed based on your Payroll Project from Module 2.

The Activity Durations and Resource NeedsPlan is needed based on your Payroll Project from Module 2.

Discuss tools and techniques for Quality Control.

Using the Project Schedule from question 4, Create a Network Diagram showing the durations on the diagram.

Explain what the cost performance measurement is that is used in cost management.

What are Gantt Charts. How are Gantt Charts used to report to your management team? What are some of the benefits of using Gantt Charts?

The team are employed by a very large organization (select your organization's name) that has traditionally used waterfall methodology to drive its development processes. However, they have reviewed the Agile methodologies and have decided to use an iterative process for this project. Project Overview: The Project Team will develop and implement a new time tracking and payroll system that will allow the staff to log in from anywhere on the network. The team will use Agile methodologies to run the implementation. Each section of the organization is determining how they gather their staff's time tracking. This will require an application that will collect the time information based on the time zone the employee is working in. The employee should track different types of time off, like personal time off, short-term disability, etc. There needs to be an option for a manager to correct information once the employee has accepted it. There needs to be security for logging in and a manager-level login. This time tracking information will feed into a payroll system. Project Start Date: Today Project Finish Date: 8 months from the start date Budget is $500,000 for software development Approach will be Agile Methodologies. There are many iterative processes but for this team project the team will use SCRUM. At the end of each chapter of the course the team will see there are references to the Agile process will help the team through the project, in addition there is information in Wysocki course material has a section on Scrum. Also, there is plenty of information about the Scrum process on the internet.

The team will need to create a Work Breakdown Structure (WBS) to start the project. Use your imagination on what the team thinks would be expected in an application. Each student should have already created the WBS in the homework assignment. The team will create a high level WBS and then start breaking each of the steps into smaller steps. During the course as the student, you will go through the Traditional Project Management (TPM) for the same project so that you and your team can correlate the difference in the styles. Organization dynamics: There are 39 development teams across the organization. All development falls under one division so the reporting lines all role up to Jayce Smithson. Jayce will be a key benefactor of the project because this will open the door to using an agile process for more projects. Jayce will be the sponsor of the project. In addition to the development division, there are 20 business units across the organization. These business units include marketing (1), product (6), operations (6), call center support (6), and project management (1). The primary impacted area to these teams will be the change on tracking time but this will also give the participants the opportunity to learn more about agile development process and the potential value it may have for the organization to bring products to the market quicker. Key stakeholders will be o Jayce Smithson from the development team will be the primary sponsor for the project. Jayce is the one that presented the project to the senior management and received the approval. The funding for the project is $500,000. The development team has never developed in any other process than the waterfall process and will be different going from managed too self-managed. Jayce has a concern over that the training on iterative development was months ago and the knowledge could have been lost over time. Jayce wanted the development team to run the project but is willing to let the project team run the transition. o Chelsea Morgan is from the marketing team. Chelsea understands the potential benefits for the quicker delivery but feels that this is too big of a change in the normal process. She has decided that it is not necessary to have anyone from the

marketing team actively participate in the project. She is not supportive at this time of the project and will be a distractor. o Randy Johnson is from the product team and will have two members from his product team joining the project team as subject matter experts (SME). These SMEs will provide support for changes needed with the product team. o There are four development managers that will be subject matter experts Sally Obrien, Joseph Kelly, Dhruba Gupa, and Allison Montgomery and will provide two developers from each of their teams to support the development. The development managers are all excited about the project however actually, Allison is not sure this is the right thing to do. o [Team] has been selected as the Product Owner for the project. Your manager is the instructor of this course and is here to help and support the team through this new project. Your manager transitioned a company from waterfall development to agile methodologies a couple of years back and is an excellent resource for team. The team will have to learn the difference in the role as a Produce Owner versus a Project Manager. o The team has been provided the complete overview of the project and will learn more as the team goes through the course.

1.1.1 Submit Project Charter 1.1 Develp Project 1.1.2 Review Charter Sponsers L.1.3 Charter Approval 1.2.1 Write Scope 1. Initiate / Plan Statement 1.2 Create Scope 1.2.2 Assign Teams 1.3.1 Submit Project Plan 1.3 Create Project Plan 1.3.2 Project Plan Approval 2.1 Verify User 2.1.1 Project Start Requirements 2.2.1 Procure Hardware / Software 2.2 Design System 2. Execute 2.2.2 Install Developed System 2.3.1 Progress Meetings 2.3 Project 2.3.2 Project Management Updates 2.3.3 RISK Management Payroll System 3.1.1 Test 3.1 Install Live 3.1.2 Control System 3.1.3 Monitor 3. Test 3.2.1 Examine System Features 3.2 User Training 3.2.2 Demo System 3.3 Go Live 3.3.1 Roll out to users 1.1.1 User feedback 4.1 Audit 4.1.2 Bug Reports 4.1.3 Document Findings 4.2.1 Update files 4. Closing and records 4.2 Document 4.2.2 archive documentation 4.3.1 Submit Final Release for approval 4.3 Acceptance 4.3.2 Closeout