In 2001, the Agile Manifesto highlighted the importance of focussing on ‘working software over comprehensive documentation’. Twenty years later there are still debates on how best to write requirements in Agile environments. Independent of the context or the sector where a scaled agile approach is in use, ensuring requirements are appropriately captured is essential.
More and more teams are utilising ‘epics’, ‘features’ and ‘user stories’, but can these artefacts really take the place of an old-school 350 page ‘Business Requirements Document’? Are they really all that is needed? Can a ‘Post-it’ contain all the needed requirements for a successful value delivery?
In this informative webinar, you will hear:
– The different types of requirements approaches that work well with scaled agile approaches
– Pitfalls to watch out for
– Tips for ensuring that requirements artefacts capture just enough and no more
About the Speaker Almudena Rodriguez Pardo was born in Bilbao (Spain) and studied computer science at RWTH University Aachen (Germany). During 22 years involved in the telecommunication sector, Almudena achieved a strong technical background as a developer, quality coordinator and technical market support engineer in different organisations within Ericsson. Moreover, Almudena was strongly involved in the Agile transformation and DevOps deployment at Ericsson, and worked as an Agile and DevOps consultant for Ericsson customers.
She is a well-known public speaker with international reputation at Agile and DevOps conferences: also as an acknowledged expert, Almudena participates at the Hustef Budapest, UCAAT Paris and ExoQA Madrid as an invited Keynote. Furthermore, she contributes to the Agile community with publications like InfoQ.
Almudena is a partner at the international company Rodriguez Pardo & Assocs, working as Business Agility Consultant and Agile expert supporting organisations worldwide in their way to Agility and DevOps deployment.