4-2 Milestone 2

.docx

School

Southern New Hampshire University *

*We aren’t endorsed by this school

Course

435

Subject

Management

Date

Jan 9, 2024

Type

docx

Pages

5

Uploaded by BrigadierIbex3969

Report
4-2 Final Project Milestone Two: Approach Selection – Decision Paper Southern New Hampshire University QSO 435 Adaptive Project Management Professor Blair McKenzie November 19, 2023 Project Management (PM) Approaches.
When it comes to project management there are multiple approaches accessible, and they operate in accordance with the resources that are available and the magnitude of the project. One of the most important elements to think about is the particular type of outcome you aim to achieve with the possessions you have access to. There are over 12 different approaches when considering project management, and the most common consists of Waterfall, Agile, Scrum and Kanban. There are two widely recognized project management methodologies: waterfall and agile. Despite the fact that they are well known in the pm society they perform most beneficially on different kinds of projects. One of the biggest differences is that Agile promotes the team to work on many project stages simultaneously, whereas Waterfall is a linear working style that demands the team to finish one phase before continuing to the next (Hoory & Bottorff, 2022). The agile approach has exceeded Waterfall in favor of the most utilized project management approach. It is a concept that places emphasis on quickness, flexibility, cooperation, and iterative procedures rather than the rigid approach that the Waterfall style praises ( Agile methodology: Embracing flexibility, collaboration, and continuous improvement for effective project management 2023). Digging deeper into agile, Kanban and Scrum are two of the many agile frameworks that are popularly used. Kanban highlights minimizing work-in-progress and visualizing the workflow ( Kanban - A brief introduction 2023). This calls for complete transparency of the job, enabling collaborators to always view the status of every inch of work, and constant interaction. One way to provide this transparency and ensure adequte communication is through what we can call brainstorming meetings. Through a set of beliefs, principles, and practices, Scrum emphasizes helping teams’ structure and manage their work (Drumond, 2023). Additionally, motivates teams to obtain knowledge from experiences, self-organize while
tackling obstacles, and reflect on their achievements and misfortunes in order to keep getting better. Approach Selection To compete with the quickly changing digital savings marketplace, Valpak transitioned the entire IT organization to agile Scrum/Kanban processes with two-week sprint delivery cycles (Cobb,2015). Considering the goals that Valpak has set, an agile project style that incorporates the scrum and Kanban methods is encouraged. In addition to streamlining office administration, mobile and online sales tools, and order entry, Valpak's mission is to enhance value and delivery (Cobb, 2015). Despite the distinctions they share, both Scrum and Kanban offer their own benefits and drawbacks. With close examination there are several connections between the two approaches. Both of them promote self-motivated groups and constant growth in the pursuit of excellence and corporate objectives. Because Scrum is so flexible, you may begin a project with just a handful of possibilities and work to refine and expand those ideas over time to create an approach that works. On the other hand, Kanban employs a visual process for ongoing improvement in addition to gathering and implementing data to drive selections. Meetings are implemented by both Scrum and Kanban to go over the project's progress. Weekly visual sessions are used for Kanban and routine standups for Scrum (Drumond, 2023). Approach Analysis Valpak can keep going on their successful course by leveraging the shared characteristics between Scrum and Kanban. Agile follows a structure and iterative, while Kanban emphasizes effectiveness, work-in-progress limitation, and work visualization. Through the application of Kanban, the agile method's backlog process may be addressed and defined, since it becomes
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help