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.
The amount of work it takes to create a framework/approach is often inversely proportional to the ease of use, fit for purpose & quality of the framework/approach. Not unlike that building high quality, easy 2use products often takes more dev time than those of lesser quality
true, people who teach & coach these approaches, must put in more effort. But the benefit to the practitioners is great - they get more skilled people presenting something that's more fit for purpose. You want your coach to be more than just 2 days of training ahead of you.
this is one of the philosophies of Disciplined Agile. The quality / simplicity is not measured in how easy it is for a professional trainer/coach to learn it, it's how easy is it for their students, mentees to learn it.
While DA is not simple in and of itself, it can be presented simply to those who are about to use it.
Also, since it's based on the theories of flow, lean and ToC, people's experience with these matches it. This enables experienced people to pick it up reasonably quickly.
flexible products/services are more likely to be fit for purpose than preset ones. If you're a pracittioner looking for something "simple" look for someone who can devlier what's simple to you - may not be the same as what's simple to someone else.

• • •

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

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
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
9 Oct
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.
@WoodyZuill wanted to make sure you saw this.
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/
Read 7 tweets
29 Sep
@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.
Read 7 tweets
27 Sep
Random thoughts about Scrum Guide Based Scrum.
portal.netobjectives.com/pages/books/da…
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.
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!