Member-only story
The Scrum concept
Scrum rules are written in several places, but — because Scrum is an American-style methodology — the concepts are not really distributed. This article summarizes what I think about the Scrum concept.
This article is a part of my Scrum series, see with free links (including to this article):
I like Scrum. The good Scrum.

You can pick two, but not all three!
There is a common wisdom in project management:
Fast, good or cheap — pick two.
There are several explanation of this consideration, for example:
- Good, Fast, Cheap: Pick Three?
- Fast, Good or Cheap — The Iron Triangle?
- Fast, Cheap, or Good. Pick one.
When I told it to optimistic or micro managers, they always got annoyed, because it means they cannot control everything. Scrum rules eliminate this kind of conflict.
Since the capacity (velocity) of the team is roughly constant, the 3 attributes are:
- Scope (selects the PO)
- Quality (decides the team)
- Deadline (derived)
Since the team selects the quality (code, test and deployment), depending on the expected “ilities” and PO selects the…