Research additional task lists or project plan examples online. Consider the project requirements when building your task list. Think about how the learning resources and their tacking will need to be integrated into the HR software. Read the 2 linked examples of project plans implemented as Microsoft® Excel® spreadsheets: Example Plan A and Example Plan B. Use these as guides in creating your own draft project plan. Notice the differences between these 2 examples. Part B: Write a 1- to 2-page paper on the following two topics: Differentiate between Agile and waterfall methodologies. In your paper, you should justify your selection of the methodology used for this project. Cite at least 2 sources to support your rationale. Describe the critical roles that are needed for this project to be completed successfully using the methodology you selected. The roles you discuss could include project manager, project sponsor, business analyst, scrum master, or program manager.

Summative Assessment= Choosing a Methodology

Part A

I will use the waterfall methodology

Detailed Task List for My Project

Part B

The Differences between Agile and Waterfall Methodologies

There are several differences between agile and waterfall methodologies. First, agile methodology separates the project development lifecycle into sprints, while waterfall methodology divides the project into various phases (Lawal & Ogbu, 2021). Furthermore, agile methodology adheres to an incremental approach, while waterfall methodology sticks to a sequential design approach. The incremental approach used in agile methodology dictates that the primary focus is on attaining critical business objectives while overlooking minute processes of the business (Lawal & Ogbu, 2021). On the other hand, the sequential design approach involves collecting data over two consecutive phases where the analyzed quantitative data influences qualitative data collection. The other difference is that agile methodology is known for its flexibility, making adjustments possible along the way. However, the waterfall methodology is a structured software development methodology that is usually relatively rigid.

The agile methodology may encompass a collection of different projects being executed simultaneously. On the other hand, the waterfall methodology is only used to perform one single task at a time. Completing one project may inform the start of another project without them running co-current. As a flexible methodology, agile permits changes to be made in the project development requirements even after the completion of the initial planning (Van Casteren, 2017). This is not possible in the case of waterfall methodology, as the requirements cannot be adjusted once the project development starts. The other variation is that an iterative development approach is followed in agile methodology. Some processes, like planning, development, and prototyping phases, may appear more than once in the project development cycle (Van Casteren, 2017). Interestingly, the waterfall methodology requires development phases like designing, planning, and testing to be executed once within the model. Whereas testing is performed concurrently with software development in agile methodology, the testing phase is only executed after completing the building phase in waterfall methodology.

The last variations between these methodologies relate to their mindset, coordination, and environment in which they operate. For instance, the agile methodology works effectively in a product mindset where the software is focused on satisfying the needs of its end users and changing based on customer demands. The waterfall methodology works effectively in a project mindset that focuses on accomplishing the project (Lawal & Ogbu, 2021). Regarding coordination, agile methodology prefers a small team that increases engagement in the execution of vital roles. On the contrary, the waterfall methodology may work with a large team since team synchronization may be required at only trim levels (Van Casteren, 2017). Finally, regarding the environment, the description of project details may change at any time in the SDLC process in agile methodology. In contrast, project descriptions in the waterfall are final, and no adjustments can be made.

The Rationale for the Selected Methodology

I selected the waterfall methodology because the project under consideration was only one– to enhance the skill set of employees within the organization. Furthermore, the rigidity of the requirements in the waterfall methodology would mean that the project would stick to the set timelines and costs. Also, collecting data in two consecutive phases ensures that the requirements developed are informed by research, reducing the need for future adjustments.

Roles of Key Stakeholders

Project Manager

The project manager performs various roles in a project executed under the waterfall methodology. First, the project manager must plan and develop the project idea. In this role, the project manager works with the company’s internal and external clients to develop a process that would necessitate the success of an idea (Levitt, 2016). The process includes but is not limited to developing a detailed project plan, defining the project scope, and assigning specific tasks to team members (Levitt, 2016). The other roles the project manager performs are to lead the dream team, monitor the project progress, and solve issues that arise during the project execution.

Project Sponsor

The project sponsor undertakes various roles as far as executing a project is concerned. For instance, one role of a p