Hacker News new | ask | show | jobs
by cocojumbo123 5021 days ago
Actually what the author describes is a natural path of evolution for that team. Scrum (as a process) contains the possibility of changing the scrum rules themselves - although it is strongly recommended one does that only after they get experienced (e.g. they actually manage to get shippable product each iteration).

When the focus is on the process itself and not on delivery there is something rotten in Amsterdam.

Scrum can be a micro-manager's dream (think of the visibility on who is doing what at almost hourly level) - case in which one can end up with focus on the process not on result.