Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Organic Scrum

No description

Hugo Glagovsky

on 18 March 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Organic Scrum

Organic Scrum
Stacey Matrix for Complexity
Requirements: WHAT must be done.

Technology: HOW it must be done.

In both cases, it's relative to the individual/team/organization. How well do WE handle this technology?

Agile frameworks help in the complexity area between simplicity and caos.
Essential vs. Accidental Complexity (Brooks)
Accidental complexity is anything that adds unnecesary complexity to a problem:
-Relationship issues between team members
-Leaks of water in the ceiling
-Coffe machine not working
-Slow PCs
-Different time zones
-Bad processes

Accidental complexity is "process fat" to be removed.
Removing the fat
We get used to fat, we are anestethized to (organizational) pains.
Scrum slowly, in iterations, helps remove the anesthesia to bring back the pain... the only way to solve its root cause.

Most important artifact of the scrum framework: Retrospective meeting. It's the one meeting that's not about the product but about the process. What did we do wrong? What's the root cause? How can we fix it?
Scrum Cycle: Plan -> Do -> Rethink and Adapt
Empirism: do, then learn. Go from concrete to abstract.
Error-friendly environment: when dealing with complexity, need to take risks. Errors are part of the learning process.
Organic growth of the product and the process
Scrum Roles
Product Owner: Single funnel of stakeholders' requirements. Knows business VALUE of Product Backlog Items and thus determines their priority (the order in which PBI's should be picked by the team).

Team: Knows the HOWs (tactics). Responsible for time estimations (COST).

Tactic (team) is how to fight the battle; Strategy (PO) is choosing which battles to fight.
Full transcript