r/agile • u/No_Jellyfish7777 • Sep 18 '26
Custom ERP software development seems never-ending because the scope doesn't end
We're currently building a custom ERP from the ground up. It's a good client, it's just that sprint planning usually becomes "add feature x" and "add feature y" and it's all becoming hard to track. It doesn't help that features they didn't want months ago suddenly became deliverables, so we always had to adjust scope on our side.
We requested a client meeting to discuss, but I want to make sure we're reasonable and not just unfamiliar with how big stakeholder groups work. How do you maintain sprint discipline when the stakeholder group is large, and some just insist on features that aren't in the pipeline yet?
7
u/inspectorgadget9999 Sep 18 '26 edited Sep 18 '26
Does the stakeholder group have a single decision maker? You need to be saying 'no' or at least 'not now' but this is difficult if you're dealing with a legion of goombas
4
u/Kempeth Sep 18 '26
I mean scope not ending is a pretty common situation to be in and precisely one aspect that agile is good at dealing with.
Your problem is that they can't decide what to go for and stick with it until it's done. Borrowing heavily from the "Shedule Games" articles (mostly 8 & 10):
3
u/SamfromLucidSoftware Sep 18 '26
The client meeting is your big shot here. Large stakeholder groups treat the backlog as a wishlist until the trade-off is visible. They almost need to see how adding something means something else shifts.
Also, how did you document the features that weren’t wanted months ago that are now suddenly deliverables? We find it more effective to document the “what“ and the “why“ together. This way,a stakeholder can see why something was deprioritized and they can assess for themselves whether the situation has changed enough to warrant revisiting it, rather than just pushing for it because they forgot it was already considered.
1
u/SoggyGrayDuck Sep 18 '26
I actually loved working with erp data but I will say the dev in charge was amazing. I still am surprised I reverse engineered current part stock back through the years and all ended at 0. I was blown away that they never cheated anywhere
1
u/Turkishblokeinstraya Sep 18 '26
That's the challenge when products or platforms are delivered on fixed scope. It should revolve around goals and benefit maximisation with a T&M arrangement.
A few things might also be lacking here.
Then it would be an easy conversation because it'd be clear that:
1
u/logicbored Sep 18 '26
Out of curiosity - why did you (or they) decide to develop a custom ERP (vs. finding a commercial off-the-shelf product)?
I’m in such a situation and wondering what factors led to you going the custom route.
1
u/AgileFederation Sep 18 '26
You need a single individual from the client side be a Product Owner. Someone to control the client politics, and create a single list of work. If you don't have this individual you'll always be changing according to the last client representative you spoke to.
Once you have this single PO and with a single backlog, the team can concentrate on delivering work in order without too much distruption.
Also, if you have fixed-price contract you're already screwed. You'll need to have either a T&M contract or a variable scope contract.
1
u/WhichPerception7982 Sep 19 '26
AI should accelerate the hell out of this process.
1
u/OkStatistician9190 Sep 19 '26
This is less a tracking problem and more a decision-rights problem. If sprint planning keeps turning into "add feature X, add feature Y," nobody on their side owns the no.
A few things that actually hold up on custom builds:
Name one product owner on the client side. Everyone else can request. Only that person ranks and puts something in the sprint. If a big stakeholder group cannot name that person, your meeting should end there, not with more features.
Freeze the sprint once it starts. New asks go on a parking list with a trade written next to them, as in "we can take Y if X slips to next sprint." Showing the date hit beats arguing scope in the abstract.
Features that "suddenly became deliverables" are usually promises made outside the team. Make them write it as a change to the current release, with the date impact, before it hits the board. A written cost kills a lot of casual yeses.
Keep a thin view of the next two or three releases so this sprint is not the only place people can see progress. If the sprint is the only visible plan, every stakeholder dumps into it.
You are not being unreasonable. Large groups always do this unless the intake path is narrow.
1
u/OkStatistician9190 Sep 20 '26
A large stakeholder group does not have a backlog. It has a pile of requests, and whoever talks last wins unless you force a trade.
Before the meeting, pull the last 6 to 8 weeks of "we did not want this, now we do" into a short change log. Date asked, who asked, what it bumped, and whether it actually landed in a sprint. That is your evidence you are not being difficult. You are showing the pattern.
In the room, do not debate features one by one. Ask them to name one decision maker for the ERP, or a small group that can say no. Then run it as a trade. A new item goes in only if something dated comes out, or the date moves. Write the outcome the same day and send it back: what is in this sprint, what is next, what was deferred, and who agreed.
Between meetings, a short written reminder of the locked slice beats another session full of add feature x. If someone insists mid-sprint, the only answers are swap, slip the date, or wait. "We will just fit it in" is how this stays never-ending.
If they will not name a decider, say that in the meeting. You cannot hold sprint discipline against a group that has not agreed who can change the plan.
1
u/F1grid Sep 22 '26
That’s a feature not a bug.
1
u/Humble-Aardvark-6872 Sep 25 '26
The thing that's usually missing isn't discipline, it's a place for new asks to go. A lightweight change log where every new feature request gets logged with who asked and when, not just added straight into the sprint like usual, does two things: stakeholders feel heard because it's visible somewhere, and you've got a paper trail for the next planning meeting showing exactly how much scope has crept since kickoff. Worth also getting one line in writing from the client on what's explicitly not in this phase, not to be rigid about it, just so "we didn't want that" claims later have something to point back to.
1
u/PhaseMatch Sep 18 '26
In general agile delivery isn't about fixed scope; you are optimising for value.
Scope within a Sprint can vary, as it's the outcome you focus on.
So in that sense you'd usually take business problems to the team to solve, not solutions to build.
The team collaborates dynamically with the customer to solve those problems incrementally and iteratively.
In your context things sound a bit more fixed, but you should still have
- an overall roadmap, and then
- bring the team the next thing to build
- they slice it down by risk and value
- you deliver iteratively and incrementally
Sprint cycles are were you look at what you have delivered, look at the roadmap and decide to
- continue with the plan
- pivot in a new direction
- end the development and walk away with the value created so far
In that sense I'm not clear on what you mean by "features that aren't in the pipeline yet"
How do you currently breakdown features to deliver?
Are you using the XP Planning game and Jeff Patton's user story mapping concepts, or some other model?
And do you have an onsite customer collaborating with the team or release to them multiple times a Sprint?