Wrestling with a major UX challenge through the force of digital product development processes
“(…) how UX can be integrated into the process is the topic of ongoing discussions between UX professionals and with other stakeholders within the organization.”
(Kris Lohmann ~ CoreMedia)
Examples are great, but in the end we need more abstraction from all of them.
“Originally, the field of usability and interaction design was slow, cumbersome and costly. These were some of the reasons that it was not adopted very fast among practitioners. However, recent years a lot of the methods and techniques have been adapted to better fit the fast moving development processes that are predominant in software companies today. But what do you do when you can’t include users because of NDAs? How do you handle the fierce security demands, that are part of your project? Does your customer really know their users, or do they only think they do? And when you have a deadline, how do you avoid UI slowing your progress? This talk is a case story of how UX was included in the agile development process that resulted in the first Danish mobile bank app: Danske Banks mobile banking app. “
(Janne Jul Jensen a.k.a. @jjjtrifork ~ GOTO Conference 2014)
UX has the argument of reason; software engineering of power.
“Agile teams are more proficient in executing the development process, but the compressed timescale forces some to abandon user research and degrade the resulting user experience.”
(Hoa Loranger ~ Nielsen Norman Group)
With the interdisciplinary work of agile/scrum, UX is not an integral part of product development. And therefore everybody’s responsibility.
“As someone who has worked in the field of user experience for decades, received training on half a dozen development methodologies, and completed over 150 agile projects, one thing that I am quite confused about these days is the term waterfall. In pre-agile times, I never worked in any organization that claimed they were doing waterfall development. If I did hear terms like ‘toss it over the wall’ – and they were as derisive back then as they are now. Product development – at least for products that anyone expects to be successful – has always been iterative, incremental, and collaborative.”
(Steven Hoober a.k.a. @shoobe01 ~ UXmatters)
Getting software development more into the world of people through UX design.
“This article looks to educate developers, project managers, ScrumMasters, Product Owners, product managers, UX team members, and the like about a way to integrate UX and Lean UX principles into Scrum projects. It specifically focuses on the Scrum framework so familiarity with that method is encouraged when implementing the UX Runway practice detailed here and understanding this article. There are some concepts from SAFe but an in depth understanding is not critical. Though I have based the UX Runway around Scrum, it does have reusable concepts and could be readily adapted for other Agile methods.”
(Natalie Warnert a.k.a. @nataliewarnert and Thomson Reuters ~ Methods and Tools)
The theory, discipline, and practice of software engineering never really understood HCI. Why would they do now?
“For Scrum and Agile to live up to its full potential, it must address the needs of all team contributors, not just software developers. Giving support and trust to UX contributors will help motivate them to do their best work and leverage more of their skills in the pursuit of excellence.”
(Aviva Rosenstein a.k.a. @uxresearch ~ Boxes and Arrows)