This is part one of my blog on scrum methodology.

What is Scrum?

Scrum is an agile project management framework, created by Ken Schwaber and Jeff Sutherland. The Agile Manifesto was created by these two along with unspecified others in the early 2000s. Scrum is lightweight and simple to understand but as with anything that require collaboration and organization, difficult to master. Scrum derives its name from rugby, which I would love to explain, but I know nothing of.

Agile vs. Waterfall

For the most part software development project management follows either agile or waterfall methodology. Waterfall is considered the traditional approach. It is linear, delivering a final project at the end of the waterfall. In waterfall each stage is completed before the next stage may begin.

Agile development is less traditional, and places focus on iterative development. In agile development a deliverable product is produced at the end of each sprint. This is not the final product but a functioning piece of the final product.

Scrum Roles

Product Owner

The product owner is a single person who is the only person responsible for the product backlog. Changes to the backlog may be changes by other scrum team members, but the end responsibility belongs to the product owner.

Development Team

The development team is made up of the people who do the technical development of the product. The development team is self-organizing. They are the ones who decide how long an increment will take this is not supposed to be dictated to them by the product owner nor the scrum master.

Scrum Master

The scrum master functions under the concept of servant leadership. They are there to make sure that everyone stays on the same page and that they are all practicing scrum correctly and efficiently. A big part of their role is removing obstacles for the development team and aiding in clear communication between all scrum team members. It is the scrum masters job to ensure that scrum does not become "flaccid". Flaccid Scrum is a term to describe scrum that uses scrum terminology but does not effectively produce incremented content at the end of a sprint.

Pillars of Scrum

Transparency

Scrum encourages transparency between scrum team members. Withholding information does not help productivity and so the backlogs are meant to be clearly visible and all goals are meant to be clearly understood.

Inspection

Inspection is meant to make sure the the scrum team is always checking in on themselves to discover what can be done better and what is going great. This is clear in the sprint retrospective.

Adaptation

Also a major pillar for scrum is adaptation. Scrum is meant to be agile and if something isn't working for your scrum team it can be changed,or improved upon. This is done during retrospective when the team members make commitments to changes. If your scrum team is more efficient with a every other daily scrum, the process allows for that change to be made.

Scrum Values

The scrum values are what it takes to have a successful scrum team.

Commitment

All team members must be committed to doing the work and achieving the goals of the scrum team.

Courage

Scrum team member need to have the courage to work through problems.

Focus

Everyone on the scrum team needs to be focussed on the end goal.

Openness

The scrum team agrees to be transparent about the work they are doing and where they are in the process.

Respect

Respect is the most important scrum value as the process does not work unless.
"Scrum Team members respect each other to be capable, independent people."

Come back next week for part two where we will further delve into scrum methodology.