Allen Holub @allenholub.bsky.social Profile Banner
Allen Holub @allenholub.bsky.social Profile
Allen Holub @allenholub.bsky.social

@allenholub

73,362
Followers
642
Following
1,090
Media
88,648
Statuses

I help ppl build software better: . DM is open. Upcoming-classes: .

Berkeley, CA
Joined February 2009
Don't wanna be here? Send us removal request.
Pinned Tweet
@allenholub
Allen Holub @allenholub.bsky.social
26 days
I've just scheduled a couple of public classes that cover pretty much the whole gamut of contemporary software development. "Stories to Code" looks at the user's story and how to start with conversations and end up with code that satisfies user needs. "Incremental Architecture"
1
6
24
@allenholub
Allen Holub @allenholub.bsky.social
2 years
If you're doing Scrum and estimating or breaking up stories into tasks, you may want to reconsider. From the horses mouth: 👇
Tweet media one
116
1K
7K
@allenholub
Allen Holub @allenholub.bsky.social
5 years
Public service announcement: Dear programmers, NOT LETTING ME CUT/PASTE A PASSWORD MAKES MY ACCOUNT *****LESS***** SECURE. There is a circle of hell reserved for you if you don't allow paste into a password field. Regards, Your Customers
99
2K
6K
@allenholub
Allen Holub @allenholub.bsky.social
4 years
😂
Tweet media one
132
808
6K
@allenholub
Allen Holub @allenholub.bsky.social
5 years
Educating a team slows you down for a week or two. Not educating the team slows you down forever. Time spent in learning is never wasted.
67
2K
5K
@allenholub
Allen Holub @allenholub.bsky.social
5 years
Words that DO NOT appear in the Agile Manifesto & Principles: sprint backlog product owner, scrum master release train story story points estimate velocity meeting Jira manager productivity utilization What should I add to that list?
180
1K
3K
@allenholub
Allen Holub @allenholub.bsky.social
2 years
The idea of a "full stack developer" is an insane fantasy, given the complexity of modern software. That's why we have full-stack *teams.* Every skill needed to get an idea into our customers hands is represented *on the team* by at least 2 ppl, & everybody teaches everybody else
175
339
2K
@allenholub
Allen Holub @allenholub.bsky.social
2 years
The argument that "we need to use microservices to get hard boundaries between components," is really "we are so undisciplined that we need to add considerable complexity to protect ourselves from ourselves." →
57
274
2K
@allenholub
Allen Holub @allenholub.bsky.social
1 year
Tweet media one
20
178
2K
@allenholub
Allen Holub @allenholub.bsky.social
1 year
Valve is one of the most agile companies I know of. No Sprints. No backlogs. No frameworks. No Scrum. No SAFe. Just pure agility built around iterative development and feedback. It's worth 15 minutes of your life to see how they work: 1/2
24
231
2K
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Do not use a TODO comments. Instead, add a test that fails because of the issue. That way, it might actually get fixed!
140
145
2K
@allenholub
Allen Holub @allenholub.bsky.social
3 years
Agile: • Work small • Talk to each other • Make people’s lives better That’s it. All that other junk is a distraction.
21
295
1K
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Not deploying on Friday is a huge red flag, indicating a seriously broken process—insufficient testing, for example, a lack of continuous integration and waterfall thinking (deploy many times throughout dev), and most importantly, no culture of quality. Fix all that.
298
224
1K
@allenholub
Allen Holub @allenholub.bsky.social
2 years
The purpose of TDD is to design/build the code, not test it.
Tweet media one
45
205
1K
@allenholub
Allen Holub @allenholub.bsky.social
1 year
Scrum solves problems that existed 30 years ago. If your organization is 30 years behind the curve, by all means, try it! If, however, you're not living decades in the past, there are now much better alternatives (and none of them are certificated/canned processes/frameworks).
40
156
1K
@allenholub
Allen Holub @allenholub.bsky.social
2 years
There is no such thing as a "DevOps Engineer." There are just engineers. They can develop. They can deploy the things they develop.
76
163
1K
@allenholub
Allen Holub @allenholub.bsky.social
4 years
Maintaining the monolith.
Tweet media one
45
228
1K
@allenholub
Allen Holub @allenholub.bsky.social
1 year
I find it interesting that PO/PMs at Atlassian don't use Jira. Just sayin'.
42
120
1K
@allenholub
Allen Holub @allenholub.bsky.social
4 years
The real "Spotify Model" is to continuously adapt your process and structure as you learn. People who are copying a snapshot of what Spotify was doing 8 years ago, which those ppl call the "Spotify Model," are clueless about how agile companies work.
16
198
1K
@allenholub
Allen Holub @allenholub.bsky.social
4 years
You can work for years to be more Agile at the team level, and the first time a CEO says "I need a solid estimate and roadmap & schedule for developing this product," 100% of that agiity is flushed down the toilet. It has to come from the top down.
45
316
1K
@allenholub
Allen Holub @allenholub.bsky.social
2 years
I do not do Scrum, so I have no need to estimate an increment/Sprint. I just work on the most valuable single story next. I pull that story, narrow it down to a set of <= 2-day stories, pick the most valuable (of the most valuable 😄), and build that. 1/3
44
125
1K
@allenholub
Allen Holub @allenholub.bsky.social
2 years
I think one of the most destructive myths in software is that it costs more or takes longer to develop higher-quality code. IME, the higher the quality, the faster the development goes. You cannot be fast if you can't trust your code.
53
219
951
@allenholub
Allen Holub @allenholub.bsky.social
2 years
No customer on the planet cares about how many points you completed in your Sprint. Just sayin'.
42
130
945
@allenholub
Allen Holub @allenholub.bsky.social
4 months
Rule #1 of Software Architecture: YOU ARE NOT NETFLIX! If you don't have 270M users, a quarter of which can be on the system simultaneously, you don't need the complexity necessarily to support that. Build exactly as much architecture as you need. Build it so that it can grow
18
152
935
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Bugs do not appear by magic. Somebody was paid to write them. Somebody was encouraged to work in a way that bugs would be created. The inevitability of bugs (beyond a very small number) is a myth. Their presence reflects the culture.
68
193
923
@allenholub
Allen Holub @allenholub.bsky.social
6 years
You can do Scrum until you're blue, but if you're fighting your code to make small changes, agility is impossible. Fix that first. Bad code costs real money and adds real delay. The cost of that delay often easily exceeds the cost of a rewrite.
23
485
909
@allenholub
Allen Holub @allenholub.bsky.social
4 years
Teach the testers to program. Teach the programmers to test. Testing is a skill, not a job title.
23
218
906
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Unnecessary complexity is probably the single biggest problem in the software industry. It spawns a host of problems. Write exactly what you need to write to solve the problem at hand, not one semicolon more.
44
167
896
@allenholub
Allen Holub @allenholub.bsky.social
3 years
"Do it in small pieces and talk to each other" That's pretty much what Agile is. It's not complicated.
23
199
899
@allenholub
Allen Holub @allenholub.bsky.social
3 years
You need PRs when: • You don’t trust the code • You don't trust the person writing the code • You don’t trust the process used to write the code • You don’t trust the system used to check in the code Maybe we should dump the PRs and work on that trust thing instead?
247
184
886
@allenholub
Allen Holub @allenholub.bsky.social
4 years
Deadlines (even end of Sprint) are an anti-pattern. With only a few legitimate exceptions (e.g. regulatory), they are nothing but a tool of manipulation used to exploit people into “working harder,” and they invariably lower quality. If you can’t finish “in time,” reduce scope.
35
248
811
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Best ways to speed things up: • Work on only one thing at a time. • Work as an ensemble, not as isolated individuals. • Get all the skills needed to do the work in one place. • Don't' waste time building things nobody wants/needs. • Trust people to do their work. 1/2
7
181
819
@allenholub
Allen Holub @allenholub.bsky.social
6 years
It’s highly doubtful that you’re an agile organization if every team in your company is using the same process. “Self-organizing teams,” are essential to agility, and if you’re told what to do and how to do it, you’re hardly self organizing.
17
451
782
@allenholub
Allen Holub @allenholub.bsky.social
2 years
I just came across somebody whose last name is Null. I cannot imagine the grief the poor guy is going through on a daily basis 😄
75
73
778
@allenholub
Allen Holub @allenholub.bsky.social
2 years
MVP is the: _M_inimum thing you can build that tests the _V_iability of a _P_roduct idea. It is a TEST, not a product.
24
153
765
@allenholub
Allen Holub @allenholub.bsky.social
3 years
The 8-hour day is an artifact of the industrial age. It’s how you get 3 shifts in a factory. They were 12-hours in the 19th c. IMO, 40-hour weeks, 8 hours/day, is not sustainable for knowledge work. 6 hours is about the max for any productivity. The other 2 is just punishment.
28
141
753
@allenholub
Allen Holub @allenholub.bsky.social
3 years
There is not a customer on the planet who cares how many story points you complete this Sprint 1/5
14
132
752
@allenholub
Allen Holub @allenholub.bsky.social
2 years
I'm a little shocked by the comments to this that say that the first one is better. We have a lot of work to do as a profession.
@Carnage4Life
Dare Obasanjo🐀
2 years
Nine times out of ten, clarity beats brevity when writing code.
Tweet media one
112
305
3K
92
75
738
@allenholub
Allen Holub @allenholub.bsky.social
5 years
Words that DO appear in the Agile Manifesto & Principles: individuals interaction valuable (software) collaboration change customer deliver…frequently conversation technical excellence simplicity self-organizing reflects on…effective adjusts
18
217
711
@allenholub
Allen Holub @allenholub.bsky.social
4 years
When you release high quality code every day or so, people stop asking for estimates.
34
169
699
@allenholub
Allen Holub @allenholub.bsky.social
2 years
OKRs are fine as far as they go, but I *really* dislike the requirement that the KR must be a metric—something measurable. Time for my periodic list of quotes on measurement! Goodhart's law: "When a measure becomes a target, it ceases to be a good measure". 1/6
28
110
688
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Every bug is really a missing test.
38
140
679
@allenholub
Allen Holub @allenholub.bsky.social
2 years
"Scaling Agile" almost always means "add bureaucracy to make this Agile thing look more like what we do now (and make sure middle managers keep their jobs)." Doesn't work that way. Sorry.
20
115
670
@allenholub
Allen Holub @allenholub.bsky.social
3 years
An MVP is an experiment that tests the hypothesis that something’s worth building. It is NOT Version 1 of a product.
38
158
673
@allenholub
Allen Holub @allenholub.bsky.social
2 years
I've yet to see a product that was improved because of estimates. I've yet to see a product that was delivered sooner because of estimates.
55
125
669
@allenholub
Allen Holub @allenholub.bsky.social
2 years
"Low performers" often become high performers when they move to another team. The team matters. A lot.
35
97
671
@allenholub
Allen Holub @allenholub.bsky.social
1 year
I HATE HATE HATE Microsoft Teams. I couldn't join a meeting today. Tried for 30+ minutes. There is no "Join a meeting" button. The links sent to me didn't work (got me to some worthless splash page). It insisted I log on (to what? with what account?) It's insanely bad.
102
16
664
@allenholub
Allen Holub @allenholub.bsky.social
6 years
"Agility at scale" is nuts. Scale the work down, not the process up. I've never seen an Agile process that was "scaled up" retain its agility. Can very large systems be built in an agile way? Sure. Should they be? Probably not. Build smaller cooperative systems instead.
16
223
652
@allenholub
Allen Holub @allenholub.bsky.social
2 years
The 8-hour day is a remnant of 19th c. industrialism. The factory ran 24x7 with three shifts. There's zero reason to keep that convention in software. We don't work shifts. Nobody can can do intense creative work for 8 hours straight, day in, day out.
22
111
652
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Agile software projects cannot be late, so "are we on schedule" and "will we meet our deadline" are meaningless questions. 1/7
27
116
646
@allenholub
Allen Holub @allenholub.bsky.social
3 years
I’m hereby introducing a new technical term: agilewashing. It’s the practice of putting a thin layer of Agile™ paint on a corrupt and rotting waterfall system and imagining that everything’s fixed. SAFe, for example, is a form of agilewashing.
21
124
651
@allenholub
Allen Holub @allenholub.bsky.social
2 years
No. Things don't take longer. Let's look at one way to make stories smaller. The image in the QT is the first step in breaking up a large story into many small ones. (Something they evidently didn't do.) A "workflow diagram" like that is the first step. 1/5
@alexxubyte
Alex Xu
2 years
This is the flowchart of how slack decides to send a notification. It is an excellent example of why a simple feature may take much longer. This might also explain why people don’t get notifications or clear the red dots sometimes. Img source: slack eng blog
Tweet media one
64
612
4K
13
104
646
@allenholub
Allen Holub @allenholub.bsky.social
2 years
When you scale shit, you just get a bigger pile of it.
Tweet media one
31
117
635
@allenholub
Allen Holub @allenholub.bsky.social
3 years
I think PRs are a _really_ bad idea. They make sense in an isolated-individual open-source model, but are an antipattern in most business-dev contexts where collaboration (e.g. mobbing) is possible, so code reviews aren’t needed. PRs just add dependencies, delays, & bottlenecks.
127
140
628
@allenholub
Allen Holub @allenholub.bsky.social
2 years
In general, it's a bad idea to ask customers what features they want, but it's a really good idea to ask them about their work and what's hard/frustrating/painful to do. It's your job to figure out the best way to fix that problem, not theirs.
18
130
631
@allenholub
Allen Holub @allenholub.bsky.social
5 years
Teams working on multiple projects is a huge red flag. There's been a lot of research in this area. You loose considerable productivity with each project. (At 5 projects, you loose about 80% of your productivity when compared to working on a single project).
27
256
625
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Conway's Law is the law, not a suggestion 😄 Brazeal: How your org predicts your CI/CD pipeline https://acloudguru.com/blog/engineering/cd-pipeline
Tweet media one
7
103
630
@allenholub
Allen Holub @allenholub.bsky.social
2 years
You don't ask a surgeon to track time by task to the minute as she operates, and if you did, what would that tell you about how successful the operation would be? How, exactly, is software development any different?
58
105
612
@allenholub
Allen Holub @allenholub.bsky.social
3 years
"Project managment" usually means: keep the project on time an in budget. "Product managment" is more: build the most valuable thing you can within the time/budget constraints we have. That makes way more sense to me.
15
121
619
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Agile orgs don't have QA teams, by and large. As Deming pointed out, you cannot inspect quality into a product. It has to be there to begin with. A separate QA team is an antipattern. Cross-functional teams have all the skills necessary to deliver an idea, including QA.
41
85
618
@allenholub
Allen Holub @allenholub.bsky.social
2 years
How do you estimate the team cost for a project? Don't. Create stable teams (a fixed cost). Replace project thinking w/ product thinking. What's the most important thing that moves the entire product forward? Do that. Bring work to the teams. Don't form teams to do the work.
15
112
611
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Tech debt is entirely about learning. You start by writing the best code you possibly can. Then you learn something that tells you that the code has issues (so fix them). Tech debt is inevitable if you're learning. I, at least, am always learning, so there's always tech debt.
21
119
606
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Conway's Law says the structure of the code reflects the structure of the org. When management arbitrarily reorganizes teams to work on "projects," they are also randomly & arbitrarily changing your architecture. No wonder monoliths in project-thinking orgs are such a mess.
21
122
602
@allenholub
Allen Holub @allenholub.bsky.social
3 years
If you can get a certificate in it, it’s not Agile. You can’t certify "do what works & if it doesn’t work, fix it." You can’t certify "talk to each other." You can’t certify "build small." You can’t certify "treat people with respect." You can’t certify "pay attention & learn."
12
159
602
@allenholub
Allen Holub @allenholub.bsky.social
1 year
If you're a "senior" on a team & think you'll have to do 50% of the work yourself, my advice is to do _none_ of the work yourself. Instead, spend your time helping the "juniors" do the work. You'll find the overall work will go much faster because everybody becomes better faster.
24
91
590
@allenholub
Allen Holub @allenholub.bsky.social
3 years
Was asked: "How do I stop the team from overcommitting story points every Sprint?" That's easy! • Stop committing. • Stop using story points • Stop using Sprints. Problem solved!
24
96
591
@allenholub
Allen Holub @allenholub.bsky.social
4 years
No, you won’t fix it later.
24
147
586
@allenholub
Allen Holub @allenholub.bsky.social
2 years
@SusanChappelle1 @BowmanNancy @tweetmommybop @Granikins Actually, not enough. Maybe you don't remember a few years ago when a pregnant teen was sent "congrats on your new baby" junk mail based solely on ad-tracking her normal browsing. You need to disable all ad tracking. Use Brave + Privacy Badger + a VPN. They _will_ sell this info.
7
33
567
@allenholub
Allen Holub @allenholub.bsky.social
2 years
If you think you must do something (e.g. Sprints, backlogs, story points, estimation, meetings, &c.) to be Agile, perhaps you don't fully understand what Agile is. It has nothing to do with rigid practices or frameworks. See
7
106
576
@allenholub
Allen Holub @allenholub.bsky.social
4 years
@AOC And ban from holding office in the future. And jail him while you're at it.
5
11
563
@allenholub
Allen Holub @allenholub.bsky.social
3 years
Agile has NOTHING to do with increasing output (or "velocity"). It has everything to do with building the right thing, however long that takes. Don’t know what "twice the work in half the time" is, but it’s not Agile. Building twice as much garbage in ½ the time benefits nobody.
20
143
574
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Several time recently, I've heard that "meetings are way too expensive when devs are present." The problem, ofc, is that they're even more expensive when the devs _aren't_ present, particularly when the devs build the wrong thing because they don't have the right info.
32
65
567
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Tweet media one
11
138
559
@allenholub
Allen Holub @allenholub.bsky.social
3 years
Agile is not a process. Agile is the ability to create your own process.
11
127
561
@allenholub
Allen Holub @allenholub.bsky.social
2 years
So, you're using Fibonacci story points? Here's the perfect tool! Estimate away.
Tweet media one
31
88
559
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Let me try once more. TDD == test-driven DEVELOPMENT. "Test-driven" is an adjective modifying the noun "development." It's is a dev technique (the noun), not a testing technique. The movie "The Bicycle Thief" is about a thief, not about bicycles.
32
63
550
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Any backlog that's so large that you need an electronic system (like Jira) to manage it is way too large. Instead of looking around for tools to manage that backlog, make the backlog small enough that you don't need tools. In fact, you don't really need a backlog at all.
51
72
551
@allenholub
Allen Holub @allenholub.bsky.social
4 years
A true "10x" programmer will produce code at the same rate as everybody else, but it's 10x simpler, 10x smaller, 10x easier to read, 10x more maintainable…. It has nothing to do with output.
21
95
544
@allenholub
Allen Holub @allenholub.bsky.social
2 years
This oft-cited picture is just wrong. We do not start with a skateboard and end up with a car. At no point did our customer request a skateboard or a bicycle. They'll reject that out of hand. 1/2
Tweet media one
83
98
546
@allenholub
Allen Holub @allenholub.bsky.social
3 years
If you're recognize anything in this picture, you're in deep trouble. Get some help. Please.
Tweet media one
22
152
544
@allenholub
Allen Holub @allenholub.bsky.social
11 months
User stories are supposed to be unclear. They're anything from a word to a sentence long with no implementation details. (They describe the user's work, not yours.) They are a reminder to have a conversation just before and during implementation. Fill in the details during Sprint
21
90
540
@allenholub
Allen Holub @allenholub.bsky.social
2 years
If a factory worked like a software development shop, the car would be redesigned continuously as it moved along the line. You'd have no idea what the car would look like until you delivered it, and every car you delivered would be different. We do not work in a factory.
43
106
543
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Yes, but all documentation is technical debt. You constantly have to update it. It’s always wrong. Consequently, you should write as a little of it as possible.
72
73
537
@allenholub
Allen Holub @allenholub.bsky.social
2 years
TDD "tests" are not tests. I wish we'd get over that. They are examples of how we want the code we are writing to be used, expressed in a test format so that we can execute them easily. As such, they are executable specifications—explaining how the code should work. Not tests.
34
102
534
@allenholub
Allen Holub @allenholub.bsky.social
2 years
A periodic reminder: Agile ≠ Scrum Thank you.
27
86
530
@allenholub
Allen Holub @allenholub.bsky.social
2 years
I do collaborative trunk-based dev. We commit/push every 10 minutes or so, and use feature flags to hide unfinished things. That way of working is very effective, and is impossible to do with a PR-triggered code review—a waterfall gate at its worst. Collaboration rules!
46
79
532
@allenholub
Allen Holub @allenholub.bsky.social
3 years
We need to unlearn lots of the things we learn in school: Helping each other is cheating, don’t question authority, don’t break rules, your beliefs are inherently wrong if they’re not aligned w/ the curriculum, be quiet in class, do what you’re told. An endless list.
19
124
517
@allenholub
Allen Holub @allenholub.bsky.social
2 years
I see no need to "scale Agile." You cannot become more agile by adding bureaucracy, which is what "scaling" almost always seems to mean. I've no interest in that. If huge orgs want agility, they need to become autonomous smaller orgs. Scale the work down, not the process up. 1/2
14
76
518
@allenholub
Allen Holub @allenholub.bsky.social
2 years
To me, the way to introduce agility into an org is to systematically remove the obstacles to agility. You don't force an "agile transformation" onto people. Instead, you stop doing the things that prevent agility, and the "transformation" takes care of itself. 1/1
26
75
527
@allenholub
Allen Holub @allenholub.bsky.social
3 years
Agile is easy. The hard part is getting rid of all the stuff that prevents it.
14
111
523
@allenholub
Allen Holub @allenholub.bsky.social
5 years
For those of you who imagine that it's expensive to test software:
@katie_brinker12
Katie Brinker
5 years
Today they dropped a plane from the gantry at work!
87
544
3K
10
247
521
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Backlogs are a symptom, not a tool. The very existence of a backlog tells you that you don't have the capacity to do the work, so you defer it. Replace the backlog w/ capacity. Improve processes. Don't work on non-value-add stuff. Minimize waste. Hire ppl. Do whatever it takes.
105
90
515
@allenholub
Allen Holub @allenholub.bsky.social
2 years
There is NO SUCH THING as a "technical *user* story." A user story is a story that your user tells to you. It describes your user's work, not yours. "Story" is not a code word for "some random programmer task." Tech is an implementation detail for a story, not itself a story.
41
96
517
@allenholub
Allen Holub @allenholub.bsky.social
6 years
Re. SAFe. Why does anybody on the planet think that adding bureaucracy, rigid process, and command-control hierarchy to Scrum will make anybody Agile?
41
196
515
@allenholub
Allen Holub @allenholub.bsky.social
2 years
When you look at failed-Agile orgs, the root problem is often that nobody on top trusts the people who do the work. If they'd understood that agility required giving up control, they'd have run in the other direction as fast as their little feet could take them.
16
90
515
@allenholub
Allen Holub @allenholub.bsky.social
3 years
Software development is a craft, not an assembly line.
19
101
507
@allenholub
Allen Holub @allenholub.bsky.social
3 years
"Simplicity—the art of maximizing the amount of work not done—is essential." And then we have Deloitte. Failure to grasp the concept on a grand scale.
Tweet media one
62
79
509
@allenholub
Allen Holub @allenholub.bsky.social
3 years
I prefer the metaphor of a sea chart to roadmaps. Chart your destination (strategic goal), current position, & hazards. You can't chart your route. That depends on the wind. Note in this chart, an estimate based on average travel/day is 10 days, not the 67 it actually took.
Tweet media one
24
118
511
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Re. "non-technical" Scrum Masters or coaches. We programmers, to be effective, need to understand the domain we're working in. Why does anybody think they can be an effective SM/coach without understanding the domain they're working in: software development? Learn to code.
39
70
507
@allenholub
Allen Holub @allenholub.bsky.social
2 years
Was asked what I don’t like about Scrum. Not much, really. Just: • Backlogs • Sprints • Daily Scrums • Sprint Reviews • POs • SMs • Commitments • Accountabilities • Standardization on an inflexible framework • Certs Just little stuff like that. The rest is okay.
34
78
502
@allenholub
Allen Holub @allenholub.bsky.social
3 years
Agile is a psychologically safe, people-centric, learning culture where teams are trusted to work iteratively towards strategic goals using small experiments. (How’s that for a definition?).
33
97
495