10 things to improve in your Waterfall projects that we can learn from Agile and DevOps
Not every project is working based on an Agile or DevOps approach.
There are Waterfall projects that have been running in pretty good shape for a number of years, as well as teams that prefer to follow the V or W models for a number of objectively good reasons.
The truth is that neither Agile or Waterfall are flawless approaches and both of them have their pros and cons.
Still, there are many things that we can improve from the way we run our Waterfall projects by adopting specific aspects from Agile, DevOps and even from MT (Modern Testing) approaches.
- How to differentiate between a project working Agile and one working Waterfall, and why this is VERY important - Especially useful when you have a team saying they work Agile, while in fact, they are following Waterfall principles.
- Good points we can implement into our Waterfall projects that we can borrow from Agile and DevOps
- A very brief intro into MT (Modern Testing) and what can we adopt from it to our Waterfall projects
- Points we should not try to bring into Waterfall from either Agile, DevOps or MT approaches - and why
Webinar by Joel Montvelisky
PractiTest Chief Solution Architect With over 20 years of testing experience, Joel is an expert with vast knowledge in various QA methodologies. More from Joel on QA Intelligence