The Fast Fish Forum is an opportunity for challengers of convention and drivers of progress to come together for the benefit of South African business and society. The forum consists of purposeful, committed and open-minded people across industries, organisations and roles who collaborate and learn together; creating a critical mass that drives innovative change in our country. At the inaugural event, held at the BSG offices on 6 April 2016, we covered two thought-provoking topics: 1. Ensuring that innovative solutions are sustainable and can fit within existing systems and processes • Is the traditional role of architecture valid in modern software development? 2. Project success – the need to deliver change that must bring about an exceptional experience for customers and users • Integrating customer research and usability testing into incremental software delivery To find out more and join the conversation follow us @FastFishForum and http://bit.ly/fastfishforum

1. Welcome to the inaugural

2. Text
AMIT LALLOO - ENTERPRISE ARCHITECT
Is the traditional role of the IT Architect still
valid in modern software development ?

3. WHY ARCHITECT ?
• Do we still need
skyscrapers?
• What are the traditional
architecting roles?
• Who defines the Non-
Functional Requirements?

4. Integrating customer research and usability testing into
incremental software delivery

5. Project Success
The need to deliver change that must bring about an exceptional
experience for Customers and End Users
UXAgile
Facilitates rapid change Builds an exceptional experience
But using only one or the other presents some
problems…

6. Designer is isolated
Too much documentation
Unrealistic expectations
Developers not involved
Slow to market
Responds poorly to change
No customer facts
No designers or users involved
Delivers an IT solution
Lack of customer vision
Change may not be the right one
Technical feasibility vs. real value
Blind Agility Big Design

7. How do we get the best of
both approaches?

8. 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.

9. What have we found on the
ground?

10. 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

11. How to be the fast fish?

12. 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

13. Thank you for joining us!
Keep the conversation going