FIRSTDRAFTAGILE.docx

CMGT/410 v19

Project Methodology Selection and Rationale

CMGT/410 v19

Page 2 of 3

C:\Users\djshirey\OneDrive - University of Phoenix\F_Drive\Style Guides\UPX Logos\Horizontal format\UOPX_Sig_Hor_Black_Medium.png
Project Methodology Selection and Rationale

Carolyne Muigai

10/29/2019

CMGT/410

Professor: Charles Selin

Questions

1. Which methodology, Agile or waterfall, do you think is most appropriate for a project characterized by innovation, loosely defined requirements, and high risk? Why? Be sure to cite at least two sources to support your rationale.

Today innovation is a bit of a challenge with different methodologies. According to my research Chin (2004) stated that agile methodology is considered the best, because its more used in highly innovative business that are pushing limits of current technology and thinking higher in terms of project planning and problem solving which makes it better. According to Katarzyna (2011) Water methodology are suitable for projects with very clear product requirements and where the requirements will not change dynamically during the project completion.

2. Which methodology, Agile or waterfall, do you think is most appropriate for a project characterized by comprehensively defined requirements and low risk? Why? Be sure to cite at least two sources to support your rationale.

I would choose Waterfall methodology because it is essentially a linear way of structuring the project schedule, with separate plans for risk mitigation, resourcing, budget and various other critical project functions. Grech (2015)

3. For the project you chose as a good fit for Agile, describe the following roles: project manager, project sponsor, business analyst, and scrum master.

For my Project I choose myself as the project manager. I will direct my staff and evaluate each cost of the project. I will also have a project sponsor to help with the procurement. Help fund the project and solve problems to oversees the projects.

4. Define project, project life cycle, and software development life cycle. How does a project’s software development life cycle differ from the project life cycle?

According to McAllister (2018), this is how this two different Project means that a planned work or task is carried out under the agreed time frame, cost and resources creating committed a product or service, usually with a specific goal. The Project is unique endeavor undertaking different timing, resources, procedures, and circumstances. The Project is executed by a teamwork and systematic operation internal and external organizations rather than individual work that is an integrated effort, planning, execution, controlling and monitoring, close-out and appraisal, and management.

Project Life cycle

The step-by-step guide for successful project delivery in today’s competitive economy. The Project Life Cycle refers to the four-step process that is followed by nearly all project managers when moving through stages of project completion. This is the standard project life cycle most people are familiar with. The Project Life Cycle provides a framework for managing any type of project within a business. Leaders in project management have conducted research to determine the best process by which to run projects. The Project Life Cycle is the standard process by which teams achieve project success.

References

Agile Project Management, Gary Chin,2004

McAllister, C.(2018) Traditional vs Agile Project Management for innovators.

Copyright© 2018 by University of Phoenix. All rights reserved.

Copyright© 2018 by University of Phoenix. All rights reserved.