What is the minimal version of the product that should be built? How do we agree what’s in and what’s out? Scenarios provide a tool that helps to leave emotions and company politics out of the MVP equation. Applied to different projects with different stakeholders, this technique works over and over again, helping to make the MVP live as early as possible.
This tutorial teaches a specific application of scenarios as the tool that helps define the MVP so that the result is minimal, complete and solving the business purpose.
You will learn how to write scenarios that put all stakeholders on the same page during initial brainstorming. You'll practice using scenarios to facilitate cross-discipline discussions in the team to find the easiest possible solutions to technical tasks. You'll understand how to use scenarios as the prioritisation tool that shows what's really necessary to build and what can wait until later. Finally, you will see how scenarios can be used for explaining the product and selling its idea to outside world.
Design and development are not poles apart. With academic background in both IT and design, Tatiana helps all members of her teams connect with each other and reach a shared understanding about what exactly is being built. She studied graphic and interaction design, intellectual computer systems and visualisation in IT in universities in 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 the 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.