Sromon DasSenior Project Manager| Mara ConsultingHalifax, Nova Scotia, Canada
I'm learning the basics of scrum and am trying to understand if and how should UAT be incorporated in the sprint cycle. Is the concept of UAT not endorsed by scrum principles? Or is the dev team responsible for testing? Or are business users engaged in testing during the sprint review?
would appreciate your thoughts on this matter.
thx Saving Changes...
UAT should be wherever it needs to be to validate/test the product. Usually it's done at the end of the Sprint, but some do it in the Sprint Review (risky), or just after the Sprint has completed. The UAT should be incorporated into the Definition of Done (DOD). Saving Changes...
Remember that a key outcome of each sprint should be a "potentially shippable product increment". As such, all aspects of testing required to deliver a production-ready increment should be completed.
However, in many organizations, due to technical constraints (e.g. UAT environment is shared across multiple teams and access has to be scheduled), resource constraints (e.g. business users aren't readily available) or both, certain types of testing cannot be completed within a sprint and hence there is the need to do these as part of a final pre-release process (I will purposely NOT use the word phase or the phrase "hardening sprint").
The team's Definition of Done should reflect all feasible activities and criteria which can be completed for work items within a sprint.
Kiron Saving Changes...
Sromon DasSenior Project Manager| Mara ConsultingHalifax, Nova Scotia, Canada
