A framework for the integration of user centered design and agile software development processes
Proceedings of the 33rd International Conference on Software Engineering
Usability evaluation in software development practice
INTERACT'11 Proceedings of the 13th IFIP TC 13 international conference on Human-computer interaction - Volume Part IV
The usage of usability techniques in scrum projects
HCSE'12 Proceedings of the 4th international conference on Human-Centered Software Engineering
Quantified extreme scenario based design approach
Proceedings of the 28th Annual ACM Symposium on Applied Computing
Best practice for efficient development of inclusive ICT
UAHCI'13 Proceedings of the 7th international conference on Universal Access in Human-Computer Interaction: design methods, tools, and interaction techniques for eInclusion - Volume Part I
Understanding the UX designer's role within agile teams
DUXU'13 Proceedings of the Second international conference on Design, User Experience, and Usability: design philosophy, methods, and tools - Volume Part I
| Hi-index | 0.00 |
SCRUM poses key challenges for usability [4, 6, 8]. First, product goals are set without an adequate study of the user’s needs and context. The user stories selected may not be good enough from the usability perspective. Second, user stories of usability import may not be prioritized high enough. Third, given the fact that a product owner thinks in terms of the minimal marketable set of features in a just-in-time process, it is difficult for the development team to get a holistic view of the desired product or features. This experience report proposes U-SCRUM as a variant of the SCRUM methodology. Unlike typical SCRUM, where at best a team member is responsible for usability, U-SCRUM is based on our experience with having two product owners, one focused on usability and the other on the more conventional functions. Our preliminary result is that U-SCRUM yields improved usability than SCRUM.