Abstract: At first sight it looks like being Agile means get rid of requirements analisys. For many people using agile methodology is merely an excuse for lacking documentation and analysis in the project. Indeed, once we have a rapid feedback from customer, is it really important to waste time on thorough requirements elaboration? Instead we can build "something", then allow our customer to look at it and rework it if needed.
In the real world this approach often drives to serious problems. During the session we will discuss the need in analysis in Agile and when it is needed. We will consider different requirement elaboration practices and discuss requirements management process in agile world.
- Do we need requirements analysis in Agile?
- Agile requirements practices and artifacts
- Requirements elaboration and analysis lifecycle
Bio: Askhat Urazbaev has graduated from MIPT and made a typical career from junior developer to project manager. Later on, in Luxoft, Askhat as a process architect was engaged in adopting "heavyweight" methodologies in different departments of the company. Happily, thanks to one of the customers, Askhat got familiar with Agile. The new way of development looked very effective. Askhat has participated in several Agile projects.
Askhat started helping teams and departments to adopt Agile methodologies in Luxoft. In March 2006 he has started Russian Agile Community (AgileRussia.ru). In 2008 Askhat along with his partner Nikita Filippov founded company ScrumTrek which consults, trains and helps companies in their transition to Agile. Among the customers of ScrumTrek there are such companies as Yandex, Afisha, HeadHunter, Ascon, Luxoft, Infopulse and many others.