Scrum: Introduction
Scrum is a simple framework for managing complex projects.
When we have projects where the technology and requirements are well defined, we can use waterfall methodologies. However, when we know less about the requirements, the technology and more complex, scrum is adopted.
Scram has 3 fundamental pillars:
- transparency: of processes, delivery requirements and status.
- inspection: constant of everything that is being done.
- adaptation: both process and product.
Fundamental practices
Product Owner and the central point with leadership powers over the product and in what order it should be done. And he who prioritizes the backlog items.
Scrum Master is responsible for helping all individuals to
understand embracing scrum values and practices.
Dev Team are the project developers, in the project they are
who decide how things will be done.
Scrum dynamics
It all starts with the product vision, and whoever proves it is the Product owner.
Afterwards, this project vision must be broken down into functionalities that
we call it the Product Backlog.
The Scrum master assists the Product Owner.
The features are divided into priorities:
- essential
- important
- it would be nice to have
This prioritization and responsibility of the Product Owner.
Scprints
The project is planned in sprints, which are periods of time
All sprints must respect a duration that must be
2 to 4 weeks.
Before each sprint starts, Sprint Planning must be done.
What is a sprint planning meeting, in sprint planning
the sprint backlog will be created.
Every morning, a meeting is held with each member of the team.
It asks 3 basic questions.
- What did you do yesterday?
- What will you do today?
- Do you have any impediments?
Sprint Review
The objective of this activity is to validate and adapt the product that is being
being built. And check that what is being done is
as expected. Here is the presentation of what was done in the sprint, and here that the changes can appear, to
the product backlog will be updated.
Retrospective
It aims to verify adaptation needs in the process
Here it will be seen:
- what was done
- What hasn't been done
- What should improve
- What should stop doing.
Top comments (5)
I attended a scrum course for students for a week, I liked it really much. The goal was to learn to estimate accurate, learn from each other. Maybe this only works if there is no manager to impress. So maybe the problem isn't scrum but project managers.
That sounds more like micro-management. And an absolute awful environment for programming.
A typical problem with religions. People want the benefit, but not to pay the price.
Scrum and agile are different?
Agile (as in the Manifesto for Agile Software Development) is a set of 4 values, and 12 principles. Pretty simple, and straightforward.
In my opinion, Scrum is a lightweight management process. It is considered one of many agile methodologies, although I consider it to be a lightweight management process that may-or-may-not also incorporate agile. I have never done Scrum by the book, even though the book is short (20 pages) and free. Scrum is simple, but it ain't easy. Kelly Waters How To Implement Scrum in 10 Easy Steps gives an easy step-by-step guide on how to adopt Scrum.
There are lots of other agile methods.
