Sprint should not contain requirements. Disagree? Read on.
In tons and tons of agile literature, we all have been told that during a sprint, team completes requirements, design, development, testing and deployment.
Looks so picture perfect.
But does it really happen in real projects?
To me, I have worked on projects which are following sprint based approach but we do not work on requirements in the same sprint.
Same case when I talk to my fellow requirements engineers / business analysts from other companies.
It is indeed a near impossible task to complete requirements in the current sprint.
The reason is simple: Design, development, coding, testing and deployment is under team’s control, requirement is not.
Requirements need much more deliberation with stakeholders. Many often stakeholders themselves may not be clear about the requirements themselves.
It makes immense sense to work on requirements one or two sprints prior to the sprint for development. That way the product owner / business analyst gets the required time to build consensus on the requirements.
It will be good if we say what actually happens than describing an impractical approach.
Let me know your thoughts on this.
Ann heads the global sales and marketing role at Adaptive US Inc. She is also a coach and mentor to thousands of BAs in their pursuit of achieving IIBA certifications. Her mission is to help business analysts to start and build a successful professional career. She is a regular author, blogger on various Business analysis, management, and technology-related topics in leading tech sites and journals.