| dc.rights.license | CC-BY-NC-ND | |
| dc.contributor | Gerard Wagenaar | |
| dc.contributor.advisor | Wagenaar, Gerard | |
| dc.contributor.author | Meer, Mark van der | |
| dc.date.accessioned | 2024-06-05T23:02:22Z | |
| dc.date.available | 2024-06-05T23:02:22Z | |
| dc.date.issued | 2024 | |
| dc.identifier.uri | https://studenttheses.uu.nl/handle/20.500.12932/46489 | |
| dc.description.abstract | This paper describes a case study on the rationale of using definition of ready at an Agile Scrum team, in combination with how teams create, maintain and apply their definition of ready. Conducted qualitative interviews showed that definition of ready can mitigate some Agile Scrum deviations. However, teams are inclined to use it to improve their process of refining requirements, by applying it to a template for their requirements. A definition of ready is often created through brainstorm sessions, and usually solely maintained when something went wrong during a sprint, with improvements being clarifications to existing criteria or additional criteria. | |
| dc.description.sponsorship | Utrecht University | |
| dc.language.iso | EN | |
| dc.subject | A research on how teams developing software using the Agile Scrum methodology, use definition of ready in their process and why. Teams not using definition of ready are also included, to understand whether certain issues arise by not having one, or if they have alternative strategies or protocols ready. | |
| dc.title | Definition of ready in practice | |
| dc.type.content | Master Thesis | |
| dc.rights.accessrights | Open Access | |
| dc.subject.keywords | Definition of ready, DoR, Practice, Deviations, Case Study, Rationale | |
| dc.subject.courseuu | Business Informatics | |
| dc.thesis.id | 31343 | |
