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
centuries ago ppl used empiricism to build bridges-result was failed &overly constructed bridges. Today we use theories that explain how to build them. More reliability, less complexlity.
10 years from now we'll look back at Agile based on frameworks way we look at waterfall now
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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.
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/
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.
Lean theory as to why Mob Programming works. Waste is directly proportional to the number of handoffs, handbacks and delays in workflow. Mob-programming eliminates all of these. The waste from these can represent 70-90% of the work being done.
to be clear. Mob Programming didn't come from Lean (I've had lots of conversations with @WoodyZuill) but it helps explain who understanding theory can help you learn new practices. 1/
@JoshBurdick72@PavelASamsonov which is part of why visibility is so important. and maybe, dare I say it, it might be useful to have a manager at a daily standup hearing "I'm blocked because I don't get enough time with a PO" Oh, but we can't do that - it'd be horrible.
@JoshBurdick72@PavelASamsonov what would have more impact to a manager?
1-hearing 3rd hand-via SM-that a team's having troubles or
2-seeing 1st hand a team is having troubles
this whole keep the manager out of the daily standup is an acccommodation to the fact that Scrum takes a negative attitude to managers
@JoshBurdick72@PavelASamsonov i'm not saying managers should be there either. I'm saying you have to do what works. and you can't prescribe that.
i was surprised to see an audio by Ken Schwaber on the Dangers of customizing Scrum.
Instead of espousing against modification you'd think there'd be a discussion on how to lower the risks.
will be writing a page on random thoughts regarding the difference between SG Scrum (Scrum guide based Scrum) and DA Scrum (Lean/Flow/ToC based Scrum).
The biggest one is Scrum being based on values and practices with no theory and DA being based on theory that enables choice.