agile and user experience: definition of 'done'

Like other UE professionals I will argue that working software means little in terms of user experience. A piece of software or a website that works technically, does not necessarily mean that users would either want or be able to use it. Agile methodologies' focus on technical efficiency is simply not enough to guarantee a user centred product. There is a need for an explicit requirement for the product to meet certain 'user centred' standards, and by that I do not mean usability standards but user experience requirements, that is ensuring the product successfully supports users' goals while also helps users immerse themselves in the brand.

Each agile project is required to offer a definition of 'done', that is, to describe when a product will be considered finished, done. Scrum masters are expected to work with their teams and list all the requirements the software will be measured against at the end of each sprint as well as at the end of the project. If the code meets the requirements then it is considered done and it taken off the backlog list.

This definition of 'done' is a window of opportunity for the UE member of the team to make sure user experience requirements are included in the definition thereby ensuring the product is not simply functioning but also offers a compelling  experience.