Everyone on your team is at 100% capacity. That's actually the problem.
Everyone on your team is at 100% capacity. That's actually the problem.
What does 'in trouble' actually mean for a work item? It's subjective... unless you have data. Here's how to define 'typical' so you can spot the outliers.
'We'll refactor after we ship' = We'll never refactor. 'We'll write tests later' = We'll never write tests. 'We'll document it when it's stable' = We'll never document it.
'When will it be done?' sounds like a simple question. It's not. You're never predicting one item β you're predicting a pile of items landing in sequence.
The rewrite project isn't a process problem. It's a hubris factory. You already built it once so how hard can it be? Very. Very hard.
'They're all important! Get them done!' just shifts prioritizing to the team β and they'll prioritize differently than you would.
A client once told me they were proud of their low development costs. They had the invoices to prove it. But they were measuring the wrong thing entirely.
At 3 concurrent projects you're spending 40% of your time switching between them. That's two full days a week of pure waste.
Everyone talks about trunk-based development like it's the promised land. Just commit to main! Problem solved! It's not that simple.
You built microservices. Your services share a database. Your services reference each other's code. You don't have microservices. You have a complicated monolith.
Written software is interesting. Delivered software is valuable.
A branch is an integration credit card. What if there was a way to ship code without branching at all? Feature flags change the game.
If your team has more than 3 long-lived branches you don't have a branching problem. You have a trust problem.
Forget story points. Forget velocity. Just count what you finish each week. It's simpler and it's more accurate.
How much do your stakeholders care about you finishing half the tasks for a feature? None. Zero. They don't care about your tasks. They want their feature. Done. Working. In their hands. If it's not done, it might as well not exist. youtu.be/wIJ6OggdeOw
"What are YOU going to do about it?" doesn't create accountability. It creates people who get really good at hiding problems from you. youtu.be/x0njd7fa8-Y
Scrum didn't slow you down. It showed you how slow you already were. The numbers always looked bad β you just couldn't see them before.
That branch you created three months ago? The one you've been dreading to merge? Let's talk about why that dread is justified.
I killed my team's self-organization by being helpful. Every time someone asked a question I gave them the answer. Turns out that was the problem.
Rewrite projects look like the easiest project in the building. You already know the business. You have the team. The existing app is right there. That confidence is exactly the problem.
'Just give me a date. I don't want probabilities.' Sound familiar? Here's the thing: you've been giving exact dates for years. And they've been wrong for years.
If youβre building forms in ASP. NET Core, donβt sleep on System.ComponentModel.DataAnnotations.
@benday.bsky.socialβ¬'s post is all about validation and how easy it is to implement the basics and beyond. Check it out! vslive.com/blogs/news-a...
If youβre building forms in ASP. NET Core, donβt sleep on System.ComponentModel.DataAnnotations.
@benday.bsky.socialβ¬'s post is all about validation and how easy it is to implement the basics and beyond. Check it out! vslive.com/blogs/news-a...
Clean up your ASP #dotNET Core MVC views with Editor and Display Templates.
@benday.bsky.social walks through using @ Html.EditorFor to handle nested models like Address, organize shared #templates and keep your #Razor code maintainable.
π Read more!
New Video! Streamlining & supporting the Daily Scrum using GitHub Projects. youtu.be/5uZ0FdNsdUQ #github #scrum
My column for @vslive.bsky.social just went live and it's one of my favorite things I've written in a while. It's a nerdy deep-dive into how C# top-level statements work. I even get into the weeds of looking at the .NET IL impl of "hello, world". Give it a read! #csharp vslive.com/Blogs/News-a...
Join Microsoft MVP and certified Scrum trainer @benday.bsky.social at Visual Studio Live! Las Vegas this March 10-14, where he'll bring his wealth of expertise to this premier developer conference.
Just started my new video series on YouTube on implementing Scrum with GitHub Projects. Give it a watch and lemme know what you think. #github #githubprojects #scrum youtube.com/playlist?lis...
DevExpress released an ARM64 version of CodeRush!!! YES! https://marketplace.visualstudio.com/items?itemName=DevExpress.CodeRushforARM
I just published a new course! Ever get the feeling that your estimates are always wrong? Is your team struggling to figure out when features will done and delivered? You should try flow metrics. #flowmetrics #throughput #cycletime #scrum #agile
https://courses.benday.com/c/flow-metrics-2023