| Website | https://holub.com |
| https://twitter.com/allenholub | |
| Mailing List | https://holub.com/subscribe |
| Substack | nobook.substack.com |
Allen Holub
- 5K Followers
- 99 Following
- 3.2K Posts
For the moment, this account is mostly cross-posted tweets. Unfortunately, you won't be able to see any of the replies from Twitter so the conversation is split between two sites. (I'll obviously reply to comments on Mastodon on Mastodon.) Find me on Twitter at https://twitter.com/allenholub if you want to follow the conversation over there.
Restricting the work people are permitted to do until _after_ they've acquired the skills required to do the work is self defeating. You learn how to do the work by doing the work! Collaborative (e.g. mob/ensemble) working solves the problem nicely.
Jason Gorman (@[email protected])
Developers need the skills to do the work, but they learn the skills by doing the work. The average employer's response is to restrict the work they do until they have the skills. But that restricts their opportunities to learn. If you want them more skilled sooner, you have to give them more responsibility earlier. How do we square this circle? Low risk work with wide learning opportunities built in.
There's not a customer on the planet who cares that you deliver on time. They care that you solve their problems. Delivering fancy software on time & in budget that does not solve their problems benefits nobody. Time should not be the primary driver, even if it's a legit factor.
Yes! ✊
---
RT @leeloowrites
This energy. This is where I am. Done.
https://twitter.com/leeloowrites/status/1644483814188630023
---
RT @leeloowrites
This energy. This is where I am. Done.
https://twitter.com/leeloowrites/status/1644483814188630023
Interesting questions: Russ Ackoff (in his talk at https://youtu.be/OqEeIG8aPPk) says a "system":
(1) consists of parts, each of which can
affect its behavior or [the system's] properties, and 1/5
---
RT @ErcanKose_
@allenholub "...look to the system ...change the system so that similar defects cannot occur again" 🤔
What is system ? What is defect ? What is change ?
What is similar? and other crazy questions...
I think Agile-Lean guys…
https://twitter.com/ErcanKose_/status/1643331009574838272
If Russ Ackoff had given a TED Talk...
From SAFe 6.0 👇. I really wonder how literally anything in SAFe's definition of the "Value Management Office" has anything at all to do with value. "Talking to the customer to understand what's valuable" is NOT on that list anywhere!
---
RT @brecksvillean
@allenholub by "understanding, measuring, and improving the flow of value" - could be translated to "spying on people who do the work"...
https://twitter.com/brecksvillean/status/1643342820835577856
---
RT @brecksvillean
@allenholub by "understanding, measuring, and improving the flow of value" - could be translated to "spying on people who do the work"...
https://twitter.com/brecksvillean/status/1643342820835577856
When you find a defect, look to the system to understand why that defect was created, then change the system so that similar defects cannot occur again. Fixing the defect is the easy, and not the most important, part.