CS 250 Southern New Hampshire University Key Facets of Scrum Agile Approach PPT

User Generated

kran7389

Programming

CS 250

Southern New Hampshire University

CS

Description

Competency

In this project, you will demonstrate your mastery of the following competencies:

  • Explain the different methodologies and stages involved in the software development life cycle
  • Apply the stages of the software development life cycle within an agile development environment
  • Evaluate various software development methodologies and tools

Scenario

Chada Tech Logo

You work for ChadaTech, a company that specializes in custom software design and development for both domestic and international clients. For many years, the company has been developing their software using a waterfall development model. Recently, ChadaTech has considered shifting all of its development teams to an agile methodology that uses the Scrum framework. They think the agile approach will enhance their products and build a more cohesive corporate culture. However, before the entire organization makes this shift, ChadaTech has decided to pilot this process with one small team: yours.

Your team has been assigned to develop an application for SNHU Travel, a travel agency seeking to expand their client base with new tools for their customers. Your team will take a Scrum-agile approach to developing the application. Additionally, ChadaTech has asked you to lead a final Sprint Review and Retrospective of the development with your team. This will help your team think through the work that they completed and how the new Scrum-agile approach facilitated the development. Finally, you have been asked to present the lessons you’ve learned to the broader company to help them decide whether or not to shift all development teams to a Scrum-agile approach.

Important Note: You will not be working with an actual team for this project. Instead, during each week of the course, you will take on a different role on the team and produce artifacts related to those roles as you progress through the phases of the software development life cycle (SDLC). You will reflect on the work you did throughout the course during your Sprint Review and Retrospective.

Directions

Sprint Review and Retrospective
As would normally happen at the end of a Sprint or an incremental release, the Scrum Master will put together a Sprint Review and Retrospective. For this deliverable, you will take on the role of the Scrum Master and create a Sprint Review and Retrospective to summarize, analyze, and draw conclusions on the work you completed during the course of the development. In a paper, be sure to address each of the following:

  • Demonstrate how the various roles on your Scrum-agile Team specifically contributed to the success of the SNHU Travel project. Be sure to use specific examples from your experiences.
  • Describe how a Scrum-agile approach to the SDLC helped each of the user stories come to completion. Be sure to use specific examples from your experiences.
  • Describe how a Scrum-agile approach supported project completion when the project was interrupted and changed direction. Be sure to use specific examples from your experiences.
  • Demonstrate your ability to communicate effectively with your team by providing samples of your communication. Be sure to explain why your examples were effective in their context and how they encouraged collaboration among team members.
  • Evaluate the organizational tools and Scrum-agile principles that helped your team be successful. Be sure to reference the Scrum events in relation to the effectiveness of the tools.
  • Assess the effectiveness of the Scrum-agile approach for the SNHU Travel project. Be sure to address each of the following:
    • Describe the pros and cons that the Scrum-agile approach presented during the project.
    • Determine whether or not a Scrum-agile approach was the best approach for the SNHU Travel development project.

Agile Presentation
Finally, you have been asked to put together a PowerPoint presentation for the leadership at your company. You will start by explaining the key facets of the Scrum-agile approach. You will also contrast the waterfall and agile development approaches to help your leadership make an informed decision. You must use properly cited sources to support your points. In your presentation, be sure to address each of the following:

  • Explain the various roles on a Scrum-agile Team by identifying each role and describing its importance.
  • Explain how the various phases of the SDLC work in an agile approach. Be sure to identify each phase and describe its importance.
  • Describe how the process would have been different with a waterfall development approach rather than the agile approach you used. For instance, you might discuss how a particular problem in development would have proceeded differently.
  • Explain what factors you would consider when choosing a waterfall approach or an agile approach, using your course experience to back up your explanation.

What to Submit

To complete this project, you must submit the following:

Sprint Review and Retrospective
Your retrospective should be a 3- to 4-page Word document with double spacing, 12-point Times New Roman font, and APA formatting. Be sure to address all prompts. You are not required to use sources for the retrospective; however, any sources that you do use must be cited.

Agile Presentation
Your agile presentation should be a PowerPoint of at least 5 slides in length, including a references slide. Be sure to address all prompts. You must use properly cited sources in APA style to support your points.

User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

Attached.

Running head: SPRINT REVIEW

1

Sprint Review
Name
Course
Professor
Institution
Date

SPRINT REVIEW

2

How the various roles on your Scrum-agile Team specifically contributed to the
success of the SNHU Travel project
Various roles were involved in the scrum-agile team, and they include the development
team, product owner, and the scrum master (Adi, 2015). The three functions described significant
responsibilities on the team in the development of the software. The scrum's essence is selforganization, empiricism, and continuous improvement, which were the roles that kept the team
to deliver high-quality work. As a result, the team was able to take responsibility in their tasks
where they organized and improved themselves to ensure the work is done correctly. The team
involved in the software development was knowledgeable on the back-end system, technology,
and business domain: the skills needed for the team members included graphic developers, coders,
and graphic developers.

The daily scrum in software development helped with ensuring

transparency and allowed the team to remain dedicated. The development team ran the daily scrum
where they inspected and adapted to the work, hence guaranteeing the work was conducted
effectively. The product owners helped set the software's direction and ensured the team delivered
the required value by providing the right. The responsibilities of the agile helped in inspecting and
adapting to change.
How a Scrum-agile approach to the SDLC helped each of the user stories come to
completion
The user stories were used to describe the type of software developed, what the user
wanted, and why they wanted it to appear that way (Jacob, 2019). The user story utilized in the
development helped create a simplified description of the required description. The user stories
were recorded on index cards in the project management software. The software development team

SPRINT REVIEW

3

wrote user stories. The user stories helped to shift the focus from the idea into the actual work.
When the software requirement changed when the customers and the team got deeper into the
design as the project progressed, the user stories helped to keep the team on track as it made it
possible to replace the big upfront design. As a result, the time for designing the software was
reduced. The user stories also helped the team deliver significantly quality software preferred by
the customers.
How a Scrum-agile approach supported project completion when the project was
interrupted and changed direction

The Scrum-agile ...


Anonymous
Really great stuff, couldn't ask for more.

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4

Similar Content

Related Tags