If you want to fix these issues in the context of Scrum I suggest J. Coplien's "A Scrum Book". Or you can just read the patterns here: https://sites.google.com/

If you want to fix these issues in the context of Scrum I suggest J. Coplien's "A Scrum Book". Or you can just read the patterns here: https://sites.google.com/a/scrumplop.org/published-patterns/home https://sites.google.com/a/scrumplop.org/published-patterns/... - The book is a slightly reworked reprint of the pattern work done by that group of people. It follows the pattern work by Christopher Alexander [1]. The patterns form a cohesive interlinked language that provides context for each pattern. Here is what it says about the Daily Scrum: https://sites.google.com/a/scrumplop.org/published-patterns/value-stream/sprint/daily-scrum https://sites.google.com/a/scrumplop.org/published-patterns/... There some useful patterns that might even make sense outside of Scrum on there. Anyways, framing approaches and solutions in a cohesive pattern language is intriguing in its own right in my opinion. [1] https://en.wikipedia.org/wiki/Christopher_Alexander https://en.wikipedia.org/wiki/Christopher_Alexander