One-off automation project or ongoing development capacity?
The two models solve different problems. A bounded process fits a project; a changing backlog benefits from flexible recurring capacity.
01
Project: when there is a clear finish line
If the scope can be defined, a project gives a clean delivery and budget framework.
- clear scope
- defined milestones
- handover
- project budget
02
Ongoing capacity: when the backlog keeps moving
Many organisations have ten smaller problems rather than one large project. A recurring capacity can follow the priorities without a new procurement cycle each time.
- ongoing backlog
- smaller improvements
- support and stabilisation
- changing priorities
03
Avoid turning continuous operations into endless mini-projects
If a system changes all the time, quoting every small change separately creates overhead. Stable systems, however, do not need permanent capacity.
- change frequency
- business criticality
- internal capability
- support demand
04
The key question: is there useful work every month?
A recurring model works when there is consistently valuable work to prioritise. If not, a project remains the cleaner choice.
- monthly demand
- response time
- backlog quality
- internal owner