If your business has moved to agile scrum style development you'll also have encountered the situation where the designs for a giving feature or product needs to be reworked during implementation.
This iteration on design/UX as part of implementation is a very healthy one, it addresses the unknowns that may have not been present at the time a given feature was designed and allow the development team to adapt and implement ideas quickly, but a process that requires developers to make Design and UX decisions on the fly can be problematic, poor judgment and assumptions can degrade the quality of a user interface and disrupt product vision and longterm development.
Involving your UI Design & UX department in the iteration in principle could solve this issue but anyone that is familiar with an organization of this structure will know that passing work back and forth from one department to another when a problem is encounter creates a very un-agile development environment. Design & UX resource become stretched and development team slow.
Lean UX to the rescue.
Among other things Lean UX practice advocated embedding designers and UX professionals in your development teams enabling the team to iterate quickly to solve problems outside departmental silos. In practice this mean less design & UX is done up front, moving the focus to the Design/UX that happens during implementation.
Read more about Lean UX here: http://uxdesign.smashingmagazine.com/2011/03/07/lean-ux-getting-out-of-the-deliverables-business/
I currently involved in implementing Lean UX in our development teams and business here at Marktplaats.nl.
Check my blog over the coming months for some insight and practical tips on how Lean UX can improve you product development life cycle.
I will also be presenting at The UCD 2014 conference on London: http://2014.ucduk.org/
Nice Post!Thanks for that...
ReplyDeleteFront End Development