Category Technical Debt
Planning a “balanced” release (3)
I’ve been posting about the way that my thinking has evolved over the years – initially thinking about an “Agile Critical Path” and now thinking more about a “balanced” release. I’ve been writing about a “maintenance overhead” and in this post I’d like to look at this in more detail. The maintenance overhead for a […]
Planning a “balanced” release (2)
In my last post I mentioned my first attempt at a chart for this. My second attempt is below This approach has three regions – i) Green – where the entire payload is not at threat ii) Amber – where some of the payload may be at risk iii) Red – where the payload is […]
How Much Architecture is “Enough?”
I saw this brilliant article on InfoQ a couple of weeks ago. https://www.infoq.com/articles/mva-enough-architecture/ The article, written by Pierre Pureur and Kurt Bittner introduces a concept called MVA (Minimum Viable Architecture) that I’ve often thought about and this article discusses essentially the balancing act between MVA and MVP (Minimum Viable Product) that is often an unspoken […]
Value realisation (6) – five steps to value
So – to summarise this last series of posts, here are my five steps to value 1) We need to be able to describe the value that is being delivered. If we can’t describe it then how are we going to know when it’s been delivered? We also need to be able to describe this […]
What is Value (2023) (9) – What is the relationship between technical debt and value?
I’ve posted about Technical Debt on numerous occasions (see my last post here https://davebrowettagile.wordpress.com/2021/10/20/managing-technical-debt-1/). The term was first coined by Ward Cunningham that attempts to describe the effects of delaying software rework/updates in a similar way to accumulating financial debt. The debt needs to be paid back or it will accumulate. A simpler definition is […]
What Is Value 2023? (2) – seven questions…
In my last post I provided plenty of links about what I’ve written so far on Value – so let’s try a different approach for this iteration 🙂 Here are seven questions that in the next few posts I’d like to explore i) How do we measure/compare value? (I’ve already written about this here davebrowettagile.wordpress.com/2021/05/18/comparing-value-1/ […]
Back to the Golden Rules (8) – Rule 7 – Look at Burn-Down Charts and Velocity
Back in 2017 I wrote the following opening paragraph “There’s so much I could write about this – when I suggested this Golden Rule back in 2008 I was thinking that if you ignore burn-down charts and velocity then you effectively end up “doing stuff” and that was contrary to the ideas of agile. First […]
Tracking Value (6)
So let’s revisit our dashboard D1) The critical path and any risks to this D2) Risks and issues D3) Dependencies D4) Demo status D5) Test/Quality Status D6) Technical Debt Status D7) Non-functional Test Status The critical path is still key in our understanding of the overall status. Going back to the example I was writing […]
Tracking Value (5)
In the last post we added “Demo status” as a valuable addition to our dashboard. What else can help us to understand the status of our value? Testing is also an important measure as our demo will typically only cover the “happy path” and our testing can provide an indication of the maturity of the […]
Intelligent Backlogs revisited again (6) – Use of AI
So, to finish off this series of posts revisiting the idea of Intelligent Backlogs lets think about how AI can help us. My original post from 2019 (see here) concentrated on two aspects i) Intelligent interventions ii) Spot trends in data Remember that in this revisit we’re taking into account the idea that what we’re […]
Dave Browett-Agile Proj Mgt 
Recent Comments