How often does your software project land on time And what if you as a tester are not involved in the planning In this blog we dive deep into the world of estimations the art and science of estimating time and effort in software development. We explore the differences between Agile and Waterfall and share practical insights from the M2Q Quality Podcast with Darko Grabovac and Matthias Six, two experienced professionals at M2Q.
Whether you are a software tester, project manager or developer in Belgium this blog will help you create more realistic schedules, engage your team and avoid the pitfalls of inaccurate estimates.
Estimates are time estimates for software development. They help teams set deadlines, set budgets and manage expectations. But why do they go wrong so often
Waterfall Here, estimations are used to set out a fixed timeline. Each requirement is estimated and scheduled sequentially. Agile Estimates are more dynamic. They trigger discussions and help teams prioritize instead of just setting deadlines.
“In Waterfall it seems simpler, but the complexity of teamwork creates unforeseen problems.” Matthias Six, M2Q
The further you are from the beginning of a project, the more uncertain your estimates become. Imagine having to estimate how long it will take to build a Starship without detailed requirements. That’s exactly why Agile offers a better approach-it embraces uncertainty and adapts as the project progresses.
Advantages Clear deadlines, easy for stakeholders to understand. Disadvantages Little flexibility, late feedback and high risk of delays. Application in Belgium Many traditional companies for example in banking or government still use Waterfall, especially when Agile seems too expensive or complex.
Advantages Continuous feedback, adjustments possible, better quality. Disadvantages Requires experienced teams and a culture of collaboration. Application in Belgium More and more IT companies and startups in Brussels, Antwerp and Ghent are embracing Agile, especially in fintech and ecommerce.
“Agile offers tremendous benefits, but it requires a different mindset. It’s not just a method, but a movement.” Darko Grabovac, M2Q
Waterfall When requirements are fixed and little change is expected. Agile When flexibility and quick adjustments are crucial.
Testers are the last people responsible for quality. If they are not involved in planning and estimating, you run the risk of Delays because testing has not been estimated. Quality problems because requirements have not been properly tested.
“As a tester, you have to be able to substantiate your point. Data is key collect and structure it, and use it in retrospectives.” Matthias Six
Start with small steps Ask to be present at ONE planning meeting. Show value Show how your feedback improves quality. Be proactive Ask questions like “How are we going to test this?” during refinement meetings.
Symptoms Planning meetings take too long, estimates are unrealistic, team members are frustrated. Solution Introduce refinement meetings to discuss requirements in advance.
Symptoms Estimates are more accurate, meetings are short and effective, everyone knows what is expected. Solution Use velocity speed of the team to set realistic goals.
“In a mature team, estimates almost naturally become good because everyone knows what is needed,” he said. Darko Gravatch
Agile is not a roadmap it is a culture change. It requires Experimentation Try new things, learn from mistakes. Collaboration Everyone on the team is responsible for quality. Flexibility Adapt as requirements change.
Example A Belgian IT company applied Agile at the corporate level, with the support of the CEO. They knew some experiments would fail, but learned from them.
“Just do it try, fail, learn and improve.” Matthias Six
Too much work The team is constantly overloaded. No improvement Retrospectives do not lead to action. Lack of fun Work feels like a rollercoaster instead of a Ferris wheel.
“If you’re still nauseous after five laps on the rollercoaster, it’s time to make a change.” Darko Grabovac
Estimate tasks as S M L rather than hours. This reduces pressure and makes estimates more accessible.
Compare new tasks with previous work. “This is just as complex as that previous feature.”
Jira for backlog management. Trello for visual planning. Teamleader popular in Belgium for project management.
Make sure product owners, developers and testers all give input.
Use velocity and retrospectives to improve your estimates.
Estimates are not an exact science they are a team effort. Whether you work in Agile or Waterfall, the key to success is Collaboration among all team members. Learning from mistakes and data. Flexibility to adapt to change.
