fast fish forum - 6 april 2016
TRANSCRIPT
Welcome to the inaugural
Text
AMIT LALLOO - ENTERPRISE ARCHITECT
Is the traditional role of the IT Architect still valid in modern software
development ?
WHY ARCHITECT ?
• Do we still need skyscrapers?
• What are the traditional architecting roles?
• Who defines the Non-Functional Requirements?
Integrating customer research and usability testing into incremental software delivery
Project Success
The need to deliver change that must bring about an exceptional experience for Customers
and End Users
UXAgileFacilitates rapid change Builds an exceptional
experience
But using only one or the other presents some problems…
Designer is isolatedToo much documentationUnrealistic expectations Developers not involvedSlow to marketResponds poorly to change
No customer factsNo designers or users involved
Delivers an IT solutionLack of customer vision
Change may not be the right one
Technical feasibility vs. real value
Blind Agility Big Design
How do we get the best of both approaches?
Iteration ‘zero’. User research is done before the development iterations begin.
80/20 principle. Just enough to infer correct customer and user requirements.
Continuous analysis and testing. Do user interviews, observations and user testing for each iteration of software.
A sprint ahead. UX team works one sprint ahead of the development team to have new screens ready for the development sprint.
What have we found on the ground?
Don’t skip scenario and task analysis
It is easy to get stuck in standards-based design
Solving needs vs. wants
The design is never right the first time
How to be the fast fish?
Don’t start sprinting unless you have insight into your users’ profiles, tasks and environments
Make use of ‘discount’ UX methods frequently
Keep the product vision based on customer value rather than system orientated
Ensure that solid development practices are used
Thank you for joining us!
Keep the conversation going