TheOccasionalWr

Kanban in IT world in my experience implies approach where you focus on the work and tasks as they come based on priority. It doesn't imply what is on the board is finished strictly by some date, as the whole premise is that you can't really know.

SCRUM implies sprints where you agree in advance what will be actually pulled into sprints and delivered by the team so spillovers are not really expected / wanted.

So now you have 4 wrong estimates to work with :) To have some predictability you should have small features. That's the only thing that can give you strong estimates. No industry has solved giving strong and correct estimates - it's in the name, it's estimation!

I'm pretty sure software development of a website doesn't translate to a life and death situation that US army is dealing with. If anything it's why there is so many managers who think this works as if we are solving lives so they have to be strict and we all have to be strict and everyone needs to have their story points updated. The reason why most people went into software development is because they like building stuff so you have to inspire that - it's quite different to why people join US army.

My 2 cents on the actual manager philosophy is that it depends on the organization and the personal and cultural differences of the team members, some people like leaders, some people like servants and some like equality. At the end of the day everyone has to be aware they do work for the business and why they do stuff. The manager has to make that aware and inspire people.

Team topologies Shapeup Sooner Safer Happier

I think those fit most companies.

I'm not sure what you mean with the "code snippets are straight out of Stackoverflow". That is factually incorrect just by how LLM works. By now there has been so much code ingested from all kinds of sources, including Stackoverflow LLM is able to help generate quite good code in many occasions. My point being it is extremly useful for super popular languages and many languages where resources are more scarce for developer but because they got the code from who knows where, it can definitely give you many useful ideas.

It's not human, which I'm not sure what is supposed to actually mean. Humans make mistakes, humans make good code. AI does also both. What it definitely needs is a good programmer still on top to know what he is getting and how to improve it.

I find AI (LLM) very useful as a very good code completion and light coder where you know exactly what to do because you did it a thousand times but it's wasteful to be typing it again. Especially a lot of boilerplate code or tests.

It's also useful for agentic use cases because some things you just couldn't do before because there was nothing to understand a human voice/text input and translate that to an actual command.

But that is all far from some AGI and it all costs a lot today an average company to say that this actually provided return on the money but it definitely speeds things up.

What if they make 2 daily calls, that would surely improve the velocity by 2 times!