Question

Write a two page overview of the Scrum/Agile project management methodology. This should describe a description of the way Scrum/Agile is used and the roles of the people involved. Additionally, provide a description of common applications of this type of methodology and how it contrasts to the project management techniques we've reviewed so far in class.

Answer 1

Scrum is an agile project management methodology involving a small team led by a scrum master, whose main job is to clear away all obstacles to the team completing work l. Work is done in short cycles called sprints and the team meets daily to discuss current tasks and roadblocks that need clearing. Simply put, scrum is a method for managing projects that allows for quick development and testing, especially within a small team.

Scrum is an approach to managing complicated projects that may have to adapt to changes in scope or requirements. By emphasising productivity, focus and collaboration , scrum team builds high quality deliverables quickly and can more easily adapt to changes.

The process

When a customer comes to the team with a certain need final product is broken up into individual chunks. (Traditionally this has been a software need, but the process also works for any project , that is comprised of multiple stages and pieces such as a marketing launch). The pieces are prioritized and tackled in a series of short bursts called sprints. Teams can determine their own sprint length, provided it's less than one week. At the end of each sprint the team delivers a product increment- essentially a version of a product that could be shipped if necessary. Transparency is a key principle in scrum, so teams and stakeholders review the result of each sprint together. This ensures everyone one the same page about priorities and deliverables, and any adjustments can be made right away.

Teams promote internal transparency through daily standups. During these brief, 15 minutes meetings, everyone reports what they accomplished yesterday. What they plan to work on that day, and any current impediments. This visibility helps uncover problems and bring them to the forefront quickly, so the team can tackle and overcome them together.

Scrum Roles

There are three main roles in scrum: the product owner, the scrum master, and the development team.

Product Owner

Product owner represents the customers interests. They decide what the team will work on next. So the teams efforts stay focused on high priority tasks that create the most value. The product owner must always be available to provide inputs or guidance to the development team, although its important to note that product owners are not managers - scrum teams self organize.

Scrum Master

The scrum masters first goal is to help the development team be self sufficient. Scrum masters intercept and remove barriers to team progress and act as a buffer between the team and any outside forces that might interfere with productivity. He/she leads daily standup meetings , so while the product owner is responsible for what the team will produce, the scrum master oversees the how.

Development Team

Development teams are made up of cross functional team members, so the group has all the necessary skills to deliver the final product. The team focuses on only one project at a time; members don't multitask or split their effort between multiple projects. Once the project owner makes an ordered list of what need to done, the development team decides how much they can complete in a single sprint and plan accordingly.

Core Values

As an Agile framework, scrum shares the values Agile manifesto. But it also create its own guidelines. These are the five golden rules in scrum:

Openness

Scrum sees collaboration as the most effective way to create the best possible product. So teamwork and transparency are essential. Rather than anxiously downplaying problems, scrum team members are open about their progress and any roadblocks they encounter.

Focus

With scrum, multi tasking is out. Since productivity is key, splitting the teams attempting across multiple projects or redirecting their efforts midsprint by shifting priorities, is avoided at all cost. Instead, teams concentrate on the task at hand for the highest velocity and best quality product.

Courage

Teams must have the tenacity to commit to an ambitious amount of work for each sprint. Scrum masters must also be able to stand up to stakeholders if necessary, and the product owner must guide the development team with authority.

Committment

Each sprint itself is commitment: teams must agree on what they're going to accomplish and stick to it. This value is reflected in each teams unique Definition of Done, a list of criteria to determine whether a feature or deliverable is truly finished- that it's not only fully functional but meets teams standards for quality.

Respect

In the service of true collaboration, roles and responsibilities are transparent. Each member of the team is respected equally, regardless of job description , seniority or status. The development team must honor the product owners authority in deciding what the team works on, and the product owner needs to respect the team's need follow whatever work process is best for them.