in the implicit vs explicit agreement discussion, it should be mentioned that implicit does not really mean you can not follow an agreement when it doesn't make sense while explicit means you must. You can just add to your explicit agreement - only do this when it makes sense. 1/
you might also add "when you don't do it, let someone know because it might make sense to improve the agreement."
Implicit merely means we've not explicitly discussed what we're doing. Why would you not want to explicitly state the groundrules of you working together? 2/
Implicit merely means we've not explicitly discussed what we're doing. Why would you not want to explicitly state the groundrules of you working together? 2/
the idea that explicit means written down or hard to change is one of the great misunderstandings of Kanban still in the Scrum community. Explicitly stating how a team works together is one of the cornerstones of Lean. 3/
You don't follow the agreements - they represent what the team thinks is the best way of working. Explicit agreements foster collaboration. It is a core mindset of Lean that's not in Scrum, but can be a significant improvement. 4/4
@threadreaderapp unroll
see Why DA FLEX Suggests Having Explicit Workflow and Agreements portal.netobjectives.com/pages/books/da… for more.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
