Comments on: Don’t Go Chasing Waterfalls (Mini-waterfall vs Agile)

By: Software Developer Skills - The Technical Skills You Need To Have

Software Developer Skills - The Technical Skills You Need To Have — Thu, 14 Dec 2017 21:25:01 +0000

[…] the way, side note here: don’t expect any team to actually really follow the software development methodology they profess …. I’m not trying to be cynical or point fingers here. I’m just a realist, and I happen to know […]

By: Parker

Parker — Sun, 21 Feb 2016 05:07:00 +0000

Agree – there is no hiding the fact that without proper, rigorous design mapped to requirements followed by build and test you wont get quality software you’ll get crap
Skip design etc and just jump into code will result in crap software.
The only way Agile could work is with a team of top flight, extremely capable professionals who know how to work in collaboration and for a business unit that wont change its mind every 2 minutes.
And that’s very very expensive.

By: keith williams

keith williams — Sun, 22 Nov 2015 04:38:00 +0000

semantics. the reason people are confused between agile and waterfall is because the first time they get introduced to agile is when a consultant tries to sell the company scrum. agile is a mindset not a methodology but its a lot harder to sell a mindset, a lot harder to explain. scrum IS mini waterfall, no matter how hard you try to hide the design code test deliver bits. in a pure agile team they dont do sprints, they accept change by the hour if that’s the way the business wants to operate. they deliver as soon as the code is ready which could be minutes, hours or days.