Tag: agile
-
Making long-term projects more agile, less waterfall
Replace multi-year forecasts with real-time discovery of operational friction. Instead of a five-year requirement for a “targeting system,” identify the bottleneck–like a three-hour targeting approval process. Set a goal–like reducing the approval process to 30 minutes. And empower a team to solve it. In this Kessel Run example, the requirement was an outcome, not a…
-
Eight years of wanting, three months of building with AI lalitm.com/post/buil… When I was working on something where I didn’t even know what I wanted, AI was somewhere between unhelpful and harmful. The architecture of the project was the clearest case: I spent weeks in the early days following AI down dead ends, exploring designs…
-
one of the values of Pair Programming is that you have to regularly explain things to your pair. This is an important part of learning – for the person doing the explaining. After all one of the best ways to learn something is to try to teach it. 🔗 Fragments: February 4
-
Agile fails quickly if you don’t follow the practices.
-
Vibes, Code, Consequences
A selection from my weblog and elsewhere since last time… Original content Whitney goes to KubeCon – a cross-over episode from SDT: “This week, Whitney Lee joins us to discuss KubeCon news, Coding Assistants, and conference tips. Plus, vegan food and note-taking recommendations.” What is a platform? – Tony and I start a new weekly,…
-
What does Agile Smell Like? I tried to answer that question back in 2006 when I worked at RedMonk in the form of a PDF. This guide helps you sniff test how Agile an organization is. A “sniff test” is a quick way to establish a gut-feel about something. It helps you determine what to…
-
Platform Engineering Anti-Patterns
This is has some new material in it, not just the same old transformation discussion from agile and DevOps. So: thumbs up! 🔗 8 platform engineering anti-patterns
-
Seeing like a software company – When management meddling slows down the business because they need/want to measure and make decide. Also, good sub-plot on “the meeting for the meeting,” prep meetings and using the “back-channel” to get things done.
-
How to increase your surface area for luck – “One distinguishing feature I’ve noticed among people who are unusually successful is that they just try a lot of stuff – socially, intellectually, professionally. It’s the rate of experimentation, the number of shots on goal, that provides the magic, not the percentage of successes, which might…
-
Moral Deskilling: why you spend more time on admin than your actual job – I think what this is saying is: when you build a system of work where the people doing the actual work (“workers”) do not have quality control over their work, you mistrust them. Therefore you need more managers to oversee them.…
-
How Pair Programming Enhanced Development Speed, Focus, and Flow –
-
MCP Best Practices – Including unit tests!
-
GenX – working as designed
More on the Tanzu AI Stack As you may recall, along with several colleagues, I worked on the Tanzu annual update which came out last month. I’m sure you’ve watched the entire video, right? How else would you get to see my AAA skills at talking with my hands at the end? I mean, I…
-
Why Bro Culture Still Holds Teams Back at Work –
-
Augmented Coding: an Experience Report – Getting an app released requires so many things that humans will always find something to do, and more that can now be done better.
-
Tactical work in the age of layoffs – Once the company drops all the work/life balance stuff in favor of work harder or get fired, shift to mild malicious compliance. // “If your company is putting pressure on you to ship more, one solution is to spend less time on testing/refactoring/glue work.”
-
Refactoring to understand and “vibe coding” – ”Code is not the most valuable artifact. Your understanding of the codebase is.”
-
Developers spend most of their time not coding – Developers spending something like 50% to 60% of their time on stuff that should be automated and built into the process.
-
Measuring Productivity: All Models Are Wrong, But Some Are Useful – ”Measure Speed, Ease, and Quality Different facets of productivity warrant the use of different metrics. We typically think of productivity as a balance among speed, ease, and quality.”
-
Context-switching is the main productivity killer for developers – #1 way to improve developer productivity, 30+ years running: stop interrupting them while they’re coding. // ”Research from UC Irvine shows that developers need an average of 23 minutes to rebuild their focus after an interruption fully.”
You must be logged in to post a comment.