Basics
Scrum
A mechanism to optimize the value delivery system.
Scrum is used to drive the work and effort we take to deliver value in complex environments.
Is a way to help deal with complex problems.
Is a mechanism to guide changes.
So scrum is a agile framework that you can use as a foundation to work on complex problems.
Not a process.
Or technique.
Or methodology.
Or definitive method.
But it is a general-purpose that MUST be complemented given your domain.
Why scrum is a framework?
Because, it can be improved upon.
What is complexity
Can be defined with two dimensions:
What needs to be done.
(The "What" dimension)
How to do it.
(The "How" dimension)
Types of problems
Simple problems:
Easy to predict what it needs AND to develop.
Complicated problems:
Easy to define, but difficult to come to an agreement on how to solve it.
Or easy to solve, but hard to get to an agreement on what needs to be done.
Complex problems:
In a complex environment, you only know 1 thing for sure: You don't know everything.
You cannot early in the process predict if you are going in the right path. (You will have to change along the way)
Chaotic problems.
Types of Changes
There are two perspectives:
Effectiveness:
Delivering the right product. (The "What" dimension)
Efficiency:
(The "How" dimension)
Nonfunctional Requirements (NFRs)
Define system attributes such as:
Security
Reliability
Performance
Maintainability
Scalability
Usability
They serve as constrains or restrictions on the design of the system across the different backlogs.
There are ALWAYS nonfunctional requirements.
They should be incorporated into every Increment.
Some of them can be added to the Definition of Done.
Some of them can be added to the Product Backlog.
PMOs
In a company that uses Scrum and has PMO, the PMO proper role is:
Manages portfolios and programs and facilitates the application of techniques that complement Scrum.
Agile and Scrum relationship
Scrum is a way of implementing agility.
Studies show that 60% of the teams that claim to be agile, use Scrum as its core framework.
Scrum Definition in a Nutshell
Scrum requires a Scrum Master to foster an environment where:
A product owner orders the work for a complex problem into a product backlog.
The scrum team turns a selection of the work into an increment of value during a Sprint.
The scrum team and its stakeholders inspect the results and adjust for the next Sprint.
Repeat.
The scrum framework is purposefully incomplete, only defining the parts required to implement scrum theory.
How scrum works (Flow)
This iterative and incremental process is executed until work is done or budget is over and includes refining the product backlog as needed.
Product Backlog
It all starts with the product backlog, which contains all the work to be done, and describes what will fulfill the product goal.
It is maintained by the Product Owner (PO), who makes sure that the top items are the most important ones.
Sprint Planning
Events done for crafting a sprint goal, and for the developers to select the Product Backlog items to be developed during the Sprint.
The sprint goal and the selected items form the Basics.
Sprint Backlog
Also contains an actionable plan for delivering an Increment.
Sprint
During the Sprint which usually lasts at most one month, the developers conduct daily scrums to synchronize their work and maximize their chances of achieving the Sprint Goal.
During the sprints, the moment a Product Backlog item meets the Definition of Done, an increment is born.
Increment
Is a concrete stepping stone toward the product goal.
At the end of each sprint the scrum team conducts two events.
First they run a Sprint Review event in which the scrum team and the invited stakeholders inspect to produced increment, giving informed feedback that might adapt the product backlog.
Afterward the scrum team members run a Sprint Retrospective event, in which they inspect and adapt their interactions, processes, and the definition of done, which might impact the next sprint planning event.
Last updated