Свешникова Наталья Владимировна
Business requirements for agile development process
It is a story of an intensively growing product that used to have an iteration backlog with detailed stories. Due to the growth of complexity, it appeared to be important for the team to have short artefacts those describe the main aspects of changes.
I’ll describe how we decompose and maintain requirements on two levels of abstraction and what problems does it helps to solve.
How to deliver requirements just enough just in time
Consider your scope is much bigger than your team capacity; it is changed regularly and can’t be frozen. Moreover, business requirements have equal priorities. Is it possible to make the problem even worse just by choosing the way we analyze the requirements? What can business analyst do to simplify the problem according to team capacity and business needs?
I will describe how we discover priorities and decompose requirements while scope management. I will focus on how to avoid the hamster wheel of continuous actualization of growing analyst artefacts and how not to get lost in the changing net of changing requirements interdependencies.