If the agile and UEX communities are going to work together effectively, they need to find a middle ground.  I believe that middle ground exists, but that both communities need to adopt several changes in order to succeed.  First, agile professionals must:

  • Learn UEX skills. .[…].
  • Accept that usability is a critical quality factor.  […]
  • Adopt UI and usage style guidelines.  Developers must understand that not only should their code follow common guidelines, so should their UIs. 

 

Similarly, UEX practitioners must make some changes.  They need to:

  • Go beyond UEX.  Agilists have mostly abandoning the concept of building teams of specialists and instead favor teams of generalizing specialists.  The implication is that although UEX practitioners bring a critical skillset to a development team, they still need to learn a wider range of skills to become truly effective.  […]
  • Become embedded in ASD teams. By embedding UEX practitioners on agile teams, not only will this increase the chance UEX issues are addressed, it will help to promote UEX skills within the agile community […]
  • Give ASD approaches a chance.  Kent Beck suggested to Alan Cooper that a week be invested at the beginning of a project to explore interaction issues, although Cooper believed that wasn’t sufficient.  The easiest way to find out who is right is to actually try it in practice.
  • Start looking beyond XP.  […] To address UEX concerns you will very likely find that you need to tailor some of the principles and practices of Agile Modeling and/or the techniques of User-Centered Design into your base software process.

 

Scott W Amber urges us to try the combination of UX design and agile and explains what needs to change on both ends of the spectrum to make it happen.

 

Geef een reactie

Het e-mailadres wordt niet gepubliceerd. Vereiste velden zijn gemarkeerd met *

Deze website gebruikt Akismet om spam te verminderen. Bekijk hoe je reactie-gegevens worden verwerkt.