Simplifying software engineering and leveling up your C# development!

Dev Leader

Waterfall is the only one that works? 😬

Waterfall: you want to go to mars, you set the requirements, the team, create the diagrams, 10 years later you go to mars but 5 years before they discovered that they needed to go to saturn.

Agile worked as well, plan changed along the way and you met the new requirements :D

I prefer the waterfall method ngl

What the waterfall technique tho ?

We frequently end up in ‘ScrumFall’ the project had to be planned out, in detail to get approved, we break the work in to ‘sprints’ of a few weeks each which (ideally) act as checkpoints to make sure we’re on track and delivering but are routinely ignored… because. As is normal the initial plan has one or more significant ‘misses’. The business analyst never went on site or engaged actual users, just their managers. The also never read the actual users ‘spell books’ - you know the documented procedures and attached handwritten notes and posits that they actually follow every month? We then need to react to ‘on the fly’ (agile style) but we can’t re-budget the project because we are only approved for the initial design time estimate. The executive sponsor ‘will try’ to get us more time to fix the miss but don’t count on it… We’ll get it done but it actually ends up with the dev team picking up the slack and pushing to make target, that push results in errors that we then have to mad fix at go-live, war-room style.