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/
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
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
 

Keep Current with Al Shalloway Proud to be part of the new PMI

Al Shalloway Proud to be part of the new PMI Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @alshalloway

9 Nov
i love it when i find the integration process of DA with FLEX finds errors (yes, something wrong) in FLEX and not just improvements to it. Finding what's wrong with your approach is something to look at.

1/
I tend to think of DA FLEX like I would a service. When I tell a service provider something's wrong I expect them to listen and say "oh, we'll fix that. Thanks for your input." 2/
I don't expect them to tell me "ah, you're just bashing." Or, "well we could do that, but then it wouldn't be our service."
The first means that they're not listening, the 2nd means i should look for another provider.

I view feedback on DA FLEX in the same manner.
3/
Read 5 tweets
9 Nov
When you hear people tout the simplicity of an approach, it is often an indication that they've lost sight of the goal - the effectiveness of the approach.

how something is defined and how something is used may be quite different 1/2
Things often start simple (1 gear car), turn more complicated (multiple gears), then become simple to use (automatic transmission).

Use a DA consultant to help you figure out what's simple for you. Then use that. A little foresight goes a long way. 2/3
Maybe the understanding in "simple to understand, difficult to master" is the wrong understanding. We need to understand what works for us. Then it's not so difficult. Choice is power. Choice is fit for purpose.
3/3
Read 5 tweets
17 Oct
when your problem is simple, basing a solution on specific practices may work. But when the problem is complex, more of a thinking and education approach is required.
our approaches should be about teaching us how to improve our results. Not presume following them provides us good results.
in '00 a framework within which to figure out what to do made sense because we didn't understand the theories under software development. Now we do. Using those theories directly is more effective. You can start with a set of often useful practices if you want to. then adjust
Read 4 tweets
17 Oct
timeboxing/iterations are practices. not inherent to Agile. When you require using them you liimit your choices. What you want is: quick feedback, managed WIP, visibility, quality workflow, cadence. work on those directly - lean/flow/ToC provide guidance.
nothing wrong w/ timeboxing. However, you shouldn't drive from it. Drive from flow. Timeboxing's a practice that provides discipilne &structure that may be needed. When build Scrum on flow you realize you want short cycle times for stories. Can eliminate timeboxing when useful.
most companies I talk to have more problem on missing, unclear, changing requirements than with their teams. Focusing on the teams and not portfolio/product management is like trying to put a gasoline fire out from a leaking pump without stopping the pump from leaking.
Read 9 tweets
11 Oct
an example of why we need more than empiricism. Imagine the theory underneath this about sub-atomic particles that you cannot observe. This theory is useful, but not observable - only (in)validatable with experiments.
1/2
Consider how this odd behavior can now be understood, how its implications (death by radiation poisoning) can be understood and dealt with (lead as a protective shield).
2/
Now, consider a Scrum team process. If you get wierd behavior what do you do? Without theory you just have to stick to Scrum practices or insert other practices. But, since Scrum creates a psychological barrier to stay within its sopce, you may never find a way out. 3/
Read 4 tweets
10 Oct
Trump's covid plan is apparently to let people get sick, and use his miracle cure. Of course, part of his plan is to eliminate insurance for people with pre-existing conditions. And he ignores the 10s of thousands of dollars in healthcare people are gong to have to pay.
this is a big issue. He's hoping all this fuss will have people ignore he owes almost half a billion dollars to people (likely the russians). And that he's trying to take away women's rights. Not to mention he's creating a white terrorist group to do his biding.
his gaslighting on ballots (no swing state sends ballots without request) takes our eyes of the GOP voter suppression. The environment, bounties, disrespect for our vets and many other things are being ignored due to cognitive overload.
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!