My father is an architect. He once told me that contractors used to just want to deliver a beautiful building. Together with the client. The same interest, the same goal.
I don't recognise that anymore. Not in construction, and frankly, not always in our profession either.
What's wrong with scrum?
Scrum in itself is not a bad method. It is designed for large, complex software projects where requirements are constantly changing and the end result cannot be fully defined in advance. Think of teams of dozens of developers building a large platform.
I know what I'm talking about. I took scrum master training at Fabrique myself. Have also experienced many scrum sessions at other parties. I know the method inside out, the principles, the ceremonies, the sprint reviews. And that is precisely why I know when it works and when it becomes an excuse not to commit to the end result.
In the world of web development for SMEs and industry organisations, scrum has often become something else. A way to get in low, start fast and then have a conversation every fortnight about the next budget. The end result remains vague. The bill runs up. And the customer feels like they are never really finished.
That is not how we work.
Our starting point: a clear plan upfront
We start every project with a thorough inventory. What do you want to achieve, who are your users, which functionalities are essential and which are nice-to-have? On that basis, we make a clear plan of action with a fixed price.
No surprises afterwards. No extra payments for functionalities that should have been there all along. Just do what we agreed.
That sounds simple. But it requires something from both sides. We have to listen carefully and be honest about what is feasible. The client has to think about what he really needs before we start. We prefer to have that conversation at the beginning rather than halfway through a project.
What if something changes?
Projects change. That is normal. A customer gets a new insight, a functional requirement turns out to work differently in practice, or something new is added.
We are not rigid about this. If something changes during the project, we discuss it honestly. What does it mean for the planning, what does it mean for the price? Transparent and hassle-free. But we don't start a project without knowing what we are working towards.
Long-term relationships as proof
The best proof that our approach works is our customers. Waterbouw.nl has been working with us for more than 15 years. BO Akkerbouw now has three platforms running with us. CED-Groep has been our partner for a complex e-commerce platform for years.
Those relationships are not there because we made them dependent. They are there because we deliver what we promise, communicate honestly and grow with what they need.
Some clients have been with us longer than with their own employer. We are genuinely proud of that.
Conclusion
Scrum works fine for the right projects. But for a trade association needing a new website, a startup wanting to build a SaaS product or a company wanting a web application developed, a clear plan with a fixed price is more fair, predictable and manageable for your budget.
We believe in the approach of the good contractor. Working together to deliver a beautiful property. Same interest, same goal.
