The document discusses institutionalizing user experience and design thinking approaches within an agile software development process at Siemens Technology and Services Pvt Ltd. Research found gaps in incorporating user and design perspectives in requirements. Initiatives were started to introduce UX processes and train people. An iterative UX process was developed aligned with SAFe principles. Over time, the process was formalized and supported more projects, and designathon events helped increase awareness and find champions. Further work is needed to standardize templates and fully institutionalize the approach.

1. 1
5/23/2018
Institutionalization of User
Experience and Design
Thinking… the agile way…
Chaitanya Inamdar
Siemens Technology and Services Pvt Ltd.
inamdarchaitanya@gmail.com
Chaitanya Inamdar
• Software Architect – STSPL
• BE (ENTC), MBA (Finance)
• Total IT Work Experience – 12 years
• Passionate about User Experience and Usability
• Human Factors International – Certified
Usability Analyst
• Certified SAFe Practitioner
• Hobbies
• DIY
• Automation/ IOT
• Robotics
• Hackathons/ Designathons
5/23/2018
https://www.linkedin.com/in/chaitanya-inamdar-7275a716/
inamdarchaitanya@gmail.com

2. 2
5/23/2018
Agenda
• Introduction
• Motivation
• Context
• Research
• Initiatives
• Role of Agile
• Process
• Event Timeline
• Challenges
• Results
• Questions
Motivation
• Situation in the software industry –
• 50- 80% of all software we ship fails to accomplish
its objectives - Marty Cagan
• 3000 raw ideas equals 1 commercial success ! -
Stevens, Greg A., Burley, James 1997
• Every 4 projects that enter development, only 1
makes to the market ! – IAG consulting
• 64% of features and functions are rarely or never
used! – Jim Jhonson
• And many...war stories...
5/23/2018

3. 3
Context
5/23/2018
• Siemens Technology and Services, Pune (450+)
• A R&D / GIC (Global In-house Center) of Siemens AG.
• Working as a offshore development center engaged in
collaborative product development with
US/Europe/China
• Local Management Vision –
• Moving from Engineering Support to Product
Leadership.
• To change the perception within the parent
organization
• Moving out of ‘Make to Spec’ Mindset / Factory
Mindset to Product Mindset
• Domain Knowledge Gaps
• Innovation Challenges
5/23/2018
Research
• Basis : BDT Model (IPMA Conference)
• Any 2 Strong aspects = PRODUCT SUCCESS
• Interviewed 12 Projects in Building Automation Domain
within department. (Offshore)
• Research findings indicated a gap in Design UX.

4. 4
5/23/2018
Research findings…
1. Business and end user related information is mostly absent (70%)
2. Business Requirement and Marketing Requirement info is absent
(87%)
3. User Persona information is missing in the requirements (92%)
4. User Experience information is almost minimal/absent in
requirements (65%)
5. Usability/ experience/ themes and NFR absent (27% completely
73 % sometimes)
6. New products inspired by the legacy products (77%)
7. Missing feasibility constraints (82%)
5/23/2018
Initiatives
• What is UX and how can we institutionalize it?
• What are proven UX processes?
• Brainstorming about bringing UX perspective in
software development at all levels like
• Requirements
• Architecture
• Testing
• Importance of sensitization about UX aspects for all
as well as specialized Training for relevant people.
(NID + HFI)
• Promoting Design Thinking by participating and
organizing initiatives like Designathons

5. 5
5/23/2018
Role of Agile
• An approach to software development under which
requirements and solutions evolve through the
collaborative effort of self-organizing and cross-
functional teams and their customer(s)/end user(s).
• Agile method proposes incremental and iterative
approach to software design
• All 12 principles of Agile Manifesto are inline with
what UX principle also tries to focus. i.e. User
centricity, focus on feedback and iterative
mechanism.
5/23/2018
UX Process
Iterative
Clear roles and responsibilities
Time boxed approach
Based on SAFe (Scaled Agile)
Note : Double click image for detailed view.

6. 6
Requirements analysis
• Considering the User perspectives
• Characteristics
• Demographics
• Environment
• Tasks
• Priorities
• Importance
• Activities performed
• What is the “cheeze”
and what is the “shock” ?
5/23/2018
Mockups/ Clickable Prototypes
• Present a fair idea of how the software will work
• Extremely valuable feedback possible
• Its best to fail early , correct and then develop
what is correct.
• Offer a lot of flexibility and modifiability as
compared to the working product.
5/23/2018
https://balsamiq.com

7. 7
5/23/2018
Development
5/23/2018
Usability Testing
• Whether the user’s problem is getting
solved with the proposed solution?
• How easy or difficult is for the user to use
the solution?

8. 8
Event Timeline
5/23/2018
Challenges
• Cultural Challenges – Complexity and over
engineering
• Budget - (Initially…)
• Identifying people from within
• No Proximity to the User – Feedback?
• Too much focus on deliveries and the “Plan”
• Breaking UI=UX culture
• Ego wars –
• Designer Vs Designer
• Designer Vs Developer
5/23/2018

9. 9
Results
• Formalized process now followed
• New proposals/ pre development ideas getting
refined by our UX group
• Catering to 7 projects for – Heuristic evaluations,
revamps, new software development.
• Designathon events proving beneficial for bringing in
awareness about UI ≠ UX , idea generation and
refinement as well as finding Usability Champions
within.
• Designathon 2017 – 26 Participants (5 teams)
• Designathon 2018 – 137 Participants (31 teams)
5/23/2018
Next Steps
• Continuously improve the process.
• Work on standardization of templates.
• Extend support to other projects.
• Collaboration with other business units
regarding this initiative bringing in more
opportunities.
• Formalize this process and include it in QMS
(Initiated. PCR pending)
• Sustain the initiative until there is a cultural
shift.
5/23/2018

10. 10
5/23/2018
Questions