CMGT week 2

re.bertyh.elpsfuben.t

cmgt410_v19_wk1_methodology_selection_and_rationale11.docx

Home >Computer Science homework help >CMGT week 2

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

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.

Both agile and waterfall methods are used while one is handling a software project. Agile is the most appropriate methodology when it comes loosely defined requirements and high risks since it permits going back to the previous step in case one an error happens unlike waterfall which does not permit going back to the previous phrase.

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

The most effective projects for agile are those that needs high quality and they need modification in future since it can modify the previous phases. Project manager in agile projects is involved in motivating the people to remain focus and modifying the work. On the other hand, project sponsor helps to define the vision, scope and set projects priorities (Patwardhan et al. 2016). Business analyst assists in setting priories and develop effective product roadmap. Furthermore, he is in charge of providing information within technology capabilities context. Finally, Scrum master facilitates the team for effective creativity and does his or her best to improve the efficiency of the development group. therefore he is mandated to manage the scrum process with coordination of scrum group.

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

Waterfall methodology has a project manager who is the critical person during the project and he is responsible for quality of the software as he manages the project and divide the tasks among other individuals. Moreover, Waterfall has business analyst whose roles is to make the software product popular in the digital market and therefore he writes business strategies. Program manager in waterfall methodology is change of creating the code and they must avoid bugs during their work.

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?

A project refers to an activity carried out to meet the creation of specific product or service. Project life cycle can be defined as the four-step process that is used by almost all project manangers when handling a project. It gives out a framework for managing any form of a project within a business. Software development life cycle refers to a framework that defines the task performed at each phase in the software development process (Balaji & Murugaiyan, 2012). Therefore, it’s a structure accompanied by a development team within the software organization. It has detailed plot of development, maintenance and replace of specific software. Project life cycle differ from software development life cycle since it’s not specific on the project its caarying out unlike software development life cycle one is aware that the cycle aims at coming up with a certain software.

References

Patwardhan, A., Kidd, J., Urena, T., & Rajgopalan, A. (2016). Embracing Agile methodology during DevOps Developer Internship Program. arXiv preprint arXiv:1607.01893.

Balaji, S., & Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC. International Journal of Information Technology and Business Management, 2(1), 26-30.