Lean Ux in Software Product Development (Hrishikesh Deshmukh)

D7424ff0e1dc983d898de62c7496c321?s=47 uxindia
October 25, 2013

Lean Ux in Software Product Development (Hrishikesh Deshmukh)

At TCS, products are developed using an adaptation of the Agile model. Development happens in Sprints but is preceeded by a short Sprint 0 for PoCs / Architectural Design. The User Experience COE has developed a lean UX version on top of this model to align the UX design framework with development. Our process is derived from User Centered Design, but focus is on rapid iterations, fast delivery and adherence to certain toll gates to ensure quality is uncompromised.

Product development entails large focus on not only functional requirements, but user requirements as well. Hence our engagements typically start with a Sprint 0 usually on the field. We use this time to the maximum to understand our prospective users using traditional UCD methodologies. At the same time, we use techniques like Kano Model Analysis to derive requirements that may not be obvious right from the start. Our requirement gathering process is governed by a User Requirement Definition Template [UXRD]. The activities are chosen based on desired level of UX maturity as defined in TCS - UXMM. Once requirements are signed off, we create personas for rapid validation of interaction design decisions.

Design & development work in tandem, interspersed with formative UTs. One key area where we are different is Enablement. We work with product dev teams as partners, and our model is geared towards ensuring that UX is driven from within the teams - not without. Finally, we have mandated cprocesses like UI testing and UX Final Inspection without which there can be no signoff. In this talk, we will describe our UX framework, its pros and cons and how it is different specifically for software products.

D7424ff0e1dc983d898de62c7496c321?s=128

uxindia

October 25, 2013
Tweet