I have a quick question. If someone has information please help me.
With Waterfall methodology, we will have plenty of time (around 4 to 6 months) to develop, test and deploy the code. But, with Agile methodology we have to do quick releases. For every 2 weeks, we need to develop, test and deploy the code. How do we handle this situation in real life world with such a tight schedules. In our company, we are trying to move from Waterfall methodology to Agile methodology. But, we are facing these type of issues. What is the testing process that we follow with agile methodology.
Thanks for the help.
Most flavors of Agiles are just mini waterfalls. Where you change delta is much smaller.
So there's basically 2 ways you can manage your Agile testing.
1. Test less. By keeping changes small and deliberate, you can reduce the scope of your testing. So one doesn't have to do a full on system regression. The idea is for any change, you'll want to know the full scope of the impact so you can test just that impact directly, as well as avoid introducing changes in a single sprint that has wide ranging impacts.
2. Automate more. By putting more under automation. In theory you can in theory take on riskier changes as more of the uncertainty is handled by automation.
Some basic differences between Waterfall and Agile:
1) Agile will not have detailed BRS documents. Instead here, we have Daily status meetings. This is very important.
2) Every two weeks, there will be one functionality completed. Total Development and QA team will work on that.
3) After major functionality completion or a few minor functionalities completion, there will be BETA releases to specific customers.
Don't worry. It is easy to handle. In the initial stages, there will not much pressure. Slowly, your team will get adapted to the methodology.
Agile is not a methodology. There's an Agile manifesto, that has four core value statements and twelve principles. It does not attempt to be a methodology. See here : Manifesto for Agile Software Development
Then there are practices like SCRUM and XP which attempt to capture the values of Agile in methodology.
Thanks very much everybody. I appreciate your responses, these are very helpful.
Very good information shared here. Thank you.
Very useful information.thnx all
I would again say, work closely with developers from their design reviews to release. One more main factor is, QA has to prioritize the bugs to be fixed by dev team.
Usually, in most organizations, agile (manifesto) is not followed to the core.
With my experience, I have seen that a kind of "hybrid" of waterfall & agile gets adopted in most of the organizations. There are several reasons for such an approach.
I am current managing such a setup and what we follow is:
1. Dev team develops features to be "demoed" in lets say Sprint 1.
2. The QA team does test development in Sprint 1 & test execution of these in Sprint 2 and so on...
Hence, a demo-able version of a product is ready from Sprint 2 onwards. Afterwards, the cycle goes on and every sprint you have some feature/story that can be demoed to the customer. The important difference here is -
a) The testing / QA team gets sufficient time in Sprint 1 to understand what Dev is developing and create scenarios.
b) When QA does test execution in Sprint 2, Dev along with developing features for Sprint 3, also fixes bugs for Sprint 2.
Please help me to find out the test cases related to video player placed on website homepage which is playing through you tube