Mark Shead

Agile Roadmaps - Agile LnL - Mark Shead x.com/i/broadcasts/1…

Orange represents the cost of delay. Both of these charts show doing the same work, but one has massively more cost of delay than the other.

Developers: This feature is so simple, there is literally no possible way it can mess up or be used incorrectly. ... a short time later ...

@FavaMandies @allenholub Some learned how to repair transmissions and work on hydraulics, but many ended up moving to Chicago, Detroit, and other areas where factory jobs were available for people with their skill level.

@allenholub Farm hands replaced by tractors got other jobs eventually. But the farmer didn't hire them back to stand behind a plow. They found new jobs in new areas.

When I quoted: "Gartner predicts that by next year, half of the companies that fired workers for AI are going to hire them back," a couple of days ago, I got a host of "all AI is evil, so take that!" crowing, as if rehired _tech_ workers will be going back to using the manual processes they used before. They won't. Programmers will be using AI-assistance. The current generation of tools like Claude Code works too well not to use them. AI is not a panacea, but it's nonetheless a useful tool. Not using that tool is like deciding not to use wheels because dragging things around on sleds "works perfectly well." I think most of the tech-related AI hate I read comes from programmers who haven't used the current generation of tools (or, in many cases, any generation of the tools). Frankly, if you're not up to date with the tooling, your opinion is just noise.

How AI Changes Prioritization - Troy Magennis x.com/i/broadcasts/1…

When the variable name doesn't seem to match the way it is being used.

Don't forget: Agile Principle #9 - Technical Excellence - AgileLnL x.com/i/broadcasts/1…

What do you mean "is our code secure?" See that security framework right there? How could it not be secure?

Working atari 2600 flappy bird, by just asking chatgpt to directly output the raw bytes for a cartridge image

A visual representation of those developers who think writing tests is a waste of their time because their code is so good nothing can possibly go wrong.

When the developers find a really simple way to deliver the story that they thought would be long and complicated.

When you know that in theory you should be writing tests for your software, but this feature will probably be ok without them. What's the worst that can happen?

Features, Stories, & Tasks! Oh My! - AgileLnL - Mark Shead x.com/i/broadcasts/1…

Them: We are implementing SAFe! Me: So what is the desired outcome of this transition? Them: We will have implemented SAFe. Me: I mean what problems do you hope to solve. Them: The fact we aren't currently using SAFe.

When the Java class looks exactly like what you need, but it is named in a way that makes you think it might not be.

If you don't have any deployed code, you don't have a scaling problem. You have a we-haven't-created-any-useful-software problem.

You aren't actually saving any money by only hiring a single person to work at 100% capacity if it means 10 other people are going to have to wait on them for 4 hours each week. Organizations often optimize for being busy rather than economic efficiency.

If you want to make developers more efficient, decrease the time between when they finish coding and when they hear users talking about how awesome it is to be actually using the new feature in production.

When the person you trust for Agile coaching hasn't ever delivered an Agile project.

A: So you are kind of like Jiminy Cricket on this team? Me: The cricket in the book only lasted a few sentences before Pinocchio killed him with a hammer. A: Ok so maybe that isn't the best description for you.