The slides used for this session are available to download from here.
Diverse inputs from various directions: business owners, technical advisors, marketing specialists, user testing results. How to make sense of it all in minimal time? The tool that I suggest is integrated scenarios (IS) - UX stories put on the timeline and actions of the system integrated into them. IS serves several purposes: facilitates information gathering and analysis, presents results in easy to understand form and helps to set order and priorities.
In this tutorial you will learn:
Design and development are not two poles apart. With academic background in both IT and design, Tatiana helps all members of her teams connect with each other and reach shared understanding about what exactly is being built. She has studied graphic and interaction design, intellectual computer systems and visualisation in IT at the universities of St.Petersburg and Bergen.
Tatiana has worked with information architecture, branding and full range UX/UI design both in-house and as an external consultant. All this education and experience became the foundation of the methodology that brings together user-oriented design and agile development process.
Building software development teams from the ground up has been Arvid's main speciality for more than 10 years. His task is to assemble the technologies that are suitable for a particular business problem and then find the right set of people and skills for them. He has done this for clients in hugely diverse domains and also for several companies where he was a co-founder.
Work on all these projects has revealed the same problem: traditional tools and artefacts are not very suitable for establishing efficient communication in teams that try to work in a lean way. A new process is needed to tie all the stakeholders and developers closer together - from the CEO to the QA. Arvid is working on creating this process and teaching teams to sustain and evolve it.