Documenting the Project Lifecycle

profilemackey66
Methodology_Selection_and_Rationale_Questions.docx

CMGT/410 v19

Project Methodology Selection and Rationale

CMGT/410 v19

Page 2 of 6

C:\Users\djshirey\OneDrive - University of Phoenix\F_Drive\Style Guides\UPX Logos\Horizontal format\UOPX_Sig_Hor_Black_Medium.pngProject 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.

It is important for the developers to select the best software methodology for the software product through the assessment of its requirements, risks associated, and innovation before the commencement of the development. Agile and waterfall methodology are the best method used by most developers to develop the best software products. Agile method is best for the projects characterized by their innovation, loosely defined requirements, and high risks because the project developers do not know the final products, and the errors experienced in the later phase has an impact on the whole project thus need for changes for the whole product.

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.

If the product has clearly defined requirements and has low risk, then waterfall methodology is the best. The methodology uses the requirements and develop the product using waterfall software methodology phases where the completion of one phase leads to the implementation and initiation of the next phase. Also, due to the well-defined requirements, the project developers know the outcome of the project and try as much as possible to stick to the client’s project requirements to come up with the anticipated project.

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.

There many stakeholders in the software development process with their distinct roles crucial for the overall project. Some of these stakeholders are project manager, project sponsor, business analyst, and scrum muster. The following are roles of each stakeholder.

· Project manager: He is responsible for the managements of the development of the entire process of the project development. He ensures that there is successful initiation, design planning, execution, monitoring, controlling and closures of the project the when the product has been assessed approved and released to the working environment (Haughey, 2019).

· Project sponsor: The project sponsor is another key stakeholder with interest in the outcome of the product. He responsibilities include initiation, approval, and establishment of series of key aspects related to the project (Schibi, 2015).

· Business Analyst: The business analyst is responsible for the assessing the product requirements and ensure that they are implemented. He assumes the role of the owners and figure out the development is effected to meet its requirements as a technical expert with solid understanding on what own the development and deployment of the software product (Stewart, 2018).

· Scrum master: He servers has the coach of the scrum team. He helps everyone in the team to achieve the highest level of performance (Cohn, 2019). He works by directing the team towards achievement of the overall project goals.

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

· Project Manager: The project manager manages the overall process of project development. He manages also the internal and external factors affecting the overall success of the project.

· Project sponsor: The project sponsor has interest on the final projects product. He funds the project development and monitors the achievement of the overall goal (Haughey, 2019).

· Business analyst: The business analyst has the all the understanding regarding the technicalities of the project and advices the owners on how the project will implement to meet it requirement and the optimum performance. He must consult with the owners and agrees on the implementation after the assessment of the requirements (Banerjee, 2016).

· Program Manager: The program manager is responsible for the development portfolio and the overall project delivery. He coordinates teams working on the various project, oversee all the project lifecycle process, defines the projects control, monitors the projects progress, manages the program budget, and managers the project risks (Bridges, 2018).

5. 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?

Definition

· Project: A project in software development contexts is an undertaking by the development team which is constrained by time, budget, and staff resources whose aim is to produce software solution to the problem.

· Project life cycle: These are sequence of stages followed throughout the development of the software project. The phases include initiation, planning, execution, and termination phase.

· Software development life cycle: This is the framework that guides the development team of the software project through one of the given methodologies (S, 2017). It states how the project is developed, deployed and maintained.

References

Banerjee, S. (2016, August 12). Role of a Project Manager in Managing Agile Projects. Retrieved from https://www.omicsonline.org/open-access/role-of-a-project-manager-in-managing-agile-projects-2167-0234-1000204.php?aid=78657

Bridges, J. (2018, March 26). Program Manager Responsibilities. Retrieved from https://www.projectmanager.com/training/program-manager-responsibilities

Cohn, M. (2019). Scrum Methodology and Project Management. Retrieved from https://www.mountaingoatsoftware.com/agile/scrum

Haughey, D. (2019). The Role of the Project Manager. Retrieved from https://www.projectsmart.co.uk/the-role-of-the-project-manager.php

S, S. (2017). A Study of Software Development Life Cycle Process Models. SSRN Electronic Journal. doi:10.2139/ssrn.2988291

Schibi, O., & Lee, C. (2015, October 5). Project sponsorship. Retrieved from https://www.pmi.org/learning/library/importance-of-project-sponsorship-9946

Stewart, R. (2018, May 9). The Modern Role of the Agile Business Analyst. Retrieved from https://www.agileconnection.com/article/modern-role-agile-business-analyst

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

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