Tag Archives: Agile
Organisation structure vs System Architecture
When there is a defect or problem, we try to do some ‘root cause analysis’ work out where the defect or problem is stemming from and try to fix the cause (hopefully) and not the symptoms of the defect. The same can be done (but is often not) for improving the architecture, rather than just […]
Delivery teams are a system – what should own business logic and decision making?
If we can think of delivery teams as a system, there are certain things that we would try to do with this system. If the system is composed of many sub-systems/applications/services, we’d try to make sure that if there is an issue in one sub-system/application/service, that any impact to other sub-systems/applications/services are minimised. If we […]
Delivery teams are a system – Is asynchronous development is an anti-pattern?
Those of you who know me know that I am opinionated about maximising return on investment and maximising the speed of delivery. The more I’ve discussed concepts around software delivery the more I see delivery teams as a system. So I’ve decided to put together a series of Blog posts to explore this further, I’d […]
Have Vision, but don’t get there.
First of all, I’ll get this out there, I HATE the term ‘Technical Debt’ with a passion, it doesn’t help us in the relaying context, and to those in the business who aren’t working with ‘Technical Debt’, hearing the phrase sounds like hearing ‘my job isn’t easy I have so many problems, please make my […]
Organising teams for a good architecture (Part 1)
Having codebases owned by specific teams results in better productivity, and can result in a better architecture (if done properly). The worst case alternative of this is having the system not divided up but having a number of teams working on any codebase they feel they need to make a change in depending on the […]