Modern QA Roadmap: If we are talking about a Modern QA engineer should we really include V-Model and Waterfall? about developer-roadmap HOT 3 CLOSED

Lots of teams work on projects which inherently require Waterfall methodologies (building a moon lander, eg.) - and many more engineers will work on teams where those (mostly) out-dated methodologies are still used. I think it's important that folks know what these terms mean and understand them well, so they can choose when to employ them or why to avoid them.

Even for an agile team, Waterfall might be needed in some instances, like when developing an integration with a customer's system that has been defined by an RFC document in advance. Perhaps a middle-way option would be to add some noted indicating that these methodologies are older and aren't considered best-practice for many teams.

from developer-roadmap.

Good shout, would it be worth highlighting that they are not used to much on the majority of modern software development projects?
Im thinking of as this is the modern QA roadmap that they dont fit in quite so much, I probably wouldnt advise any new QA to learn them as they will likely never use them.
So I think youre right in maybe not removing them and as you said adding a note?

from developer-roadmap.

Exactly @samelawrence, it's important to not only show the most bleeding edge topics in use today but always a realistic look at what's out there in the wild.

@tom-murton Feel free to submit a PR adding copy to these sections saying that they're not the most bleeding edge methods but personally, I don't think it's required.

from developer-roadmap.