This is not the event year you are looking for. For details of our next event, please visit agilemanchester.net
To view the latest event website please visit agilemanchester.net
For the latest event: agilemanchester.net
Agile teams are often strong in a development process but at times it happens that you’re pressed for time. In such cases, user involvement and testing is often the first to go. User Experience is a philosophy completely engorged in the user, in the situation and the practicalities and experiences of everyday life and use of the product. Agile is about fast, good software. These goals should support each other but in reality they often struggle. Why is that?
This tutorial examines the gap between User Experience designers and Agile processes. I supply quick and easy tools for bridging the gap between User Experience and Agile; everything from the way we think about sprints, to tools that ensure efficient communication and put the entire team on the same page.
The tools of this session may be applied to retrospectives, brainstorms, planning and whenever the need arises to communicate difficult problems for people outside the inner (agile) circle.
Mathilde works as a freelance User Experience designer and is thusly subjected to different ways of doing agile quite often. She believes in working with people rather than products. Her work includes sketching, mock-ups, models and long-winded storytelling that somehow translates into designs for products that make people happy.
She believes the developers are the most important users to any software product.
She writes about all things User Experience related on the Danish website QED.dk and gives talks about people, technology and design processes and tools.
Need help planning which sessions to attend? We've provided a breakdown of our various session types below.
A presentation and discussion of real-life (not theoretical) experiences of the application (or mis-application) of Agile and Lean practices. Case studies and experience reports include some discussion of lessons learned and an indication of how novel the work is.
Participants learn a new approach, tool or technology through using it to solve one or more practical exercises. Any software/hardware requirements are disclosed in the session description.
A session focused around some specific tool, technique or issue. Primarily led by the speaker, tutorials usually include some elements of interactivity or individual / group exercise.
An in-depth working session on a specific topic. May include paper presentations.