Question to readers: What are the challenges of incremental software delivery?

July 25, 2022
What makes working on the single most important, small change you can do, a challenge?

Yesterday I made the case for incremental software delivery in response to a question I had recently received.

Today another reader wrote in, asking me to elaborate on this statement at the end of the message:

Of course this approach is not without its challenges. If it were easy, there’d be no need for people like me to help teams achieve fast, reliable software delivery.

That’s a great question, and I will elaborate on the challenges I see to this approach. But first, I’d like to hear from you:

What challenges have you observed with incremental software delivery? Particularly, the aspect of working on the single most important, small change you can do.

Depending on the number of responses I get, I’ll summarize, or I may respond to each one individually. When replying, if you’d rather I not quote you, or keep you anonymous, please let me know. Otherwise, I’ll assume you don’t mind me using your answer and name in a future email to the list.

Thanks!

Share this

Related Content

Reader response: The downward spiral of manual acceptance testing

Lack of unit testing drives the need for manual testing. Since testing is bunched up, development is as well.

A GitFlow story

A team I recently started working with has been using GitFlow. Until last week.

Audience question: What will be delivered when?

How do you create a plan for a team as to what will be delivered when?