8 - 9 Nov: 1000 SEK
at Skansen Kronan, Gothenburg
The theme for 2013 year's conference was “Building Great Things” where we worked to help you make sure that the products and services you deliver make a real difference in the lives of those who use them.
In addition to our usual conference we offered an optional add on of a intimate and interactive workshop about “Impact Mapping” with our keynote speaker.
Facebook LinkedIn Twitter
Software is everywhere today, and countless software products and projects die a slow death without ever making any impact. Today's planning and roadmap techniques expect the world to stand still while we deliver, and set products and projects up for failure from the very start. Even when they have good strategic plans, many organisations fail to communicate them and align everyone involved in delivery. The result is a tremendous amount of time and money wasted due to wrong assumptions, lack of focus, poor communication of objectives, lack of understanding and misalignment with overall goals.
There has to be a better way to deliver! Gojko presents a possible solution, impact mapping, an innovative strategic planning method that can help you make an impact with software.
- Keynote at XP 2013, presented at the NDC 2013, BDD Exchange NYC 2012, Atlanta Scrum User Group October 2012
Gojko Adzic is a strategic software delivery consultant who works with ambitious teams to improve the quality of their software products and processes. He specialises in agile and lean quality improvement, in particular agile testing, specification by example and behaviour driven development.
Gojko's book Specification by Example was awarded the #2 spot on the top 100 agile books for 2012 and won the Jolt Award for the best book of 2012. In 2011, he was voted by peers as the most influential agile testing professional, and his blog won the UK agile award for the best online publication in 2010.
Gojko is the author of Impact Mapping, Specification by Example, Bridging the Communication Gap, Test Driven .NET Development with FitNesse and The Secret Ninja Cucumber Scrolls.
Over the last thirteen years, he has worked as a developer, architect, technical director and consultant on projects delivering financial and energy trading platforms, mobile positioning and e-commerce applications, online gaming and complex configuration management systems.
Building great products using agile practices centers around success factors such as having a strong product vision, an accelerated feedback-loop towards users and the market and one Product Owner to rule them all. But what if you enter the Wheel of Misfortune game instead?
Your product vision is steered by cognitive bias, your users and their feedback are taking your product in the wrong direction and your PO is a single point of failure? In this talk Bea reflects on the need for more “Product Integrity” when building great products. The concept of “Product Integrity” is inspired by the term “Conceptual Integrity”, which Fred P Brooks presented in his famous “The Mythical Man-Month” (1975) , and she applies it to agile development, especially aspects of product visioning and product ownership. She will explore the Wheel of Misfortune and explain why the life saver for your product is a two letter word - “no”!
Bea Düring is a PMI-certified project manager and senior agile coach at Softhouse Consulting AB. Her experience with coaching agile methods, project management and requirements go back almost 15 years.
Bea has been involved in project managing distributed agile development within the Python Open Source community during her years of working on the PyPY project, supporting the project in managing various formal funding efforts (6th Framework Program/EU, Eurostars/Vinnova and Google) during the years 2004-2011. Bea have published and held talks at agile conferences as well open source conferences.
Bea will zoom in and share her insights on agile requirements and her experience in coaching product management/product owners in how to really “do the right thing right and fast”.
Well-functioning Scrum teams are generally quite good at delivering working software, but that does not necessarily mean that they deliver optimal business value. A more business oriented culture can be created by focusing on end-user needs and the effects needed to satisfy them. User experience has come a long way since the 2nd World War. In this session you'll learn how to integrate UX in your development to build even greater things.
The ideas that satisfy the needs are the ones that can create value. Products that don't satisfy any needs cannot create any value, the better you satisfy the needs the more value you can create. I will use examples to explain the principle that value is created when needs are met.
Wouldn't it be great if we could just ask our customer what they want and then give it to them? Unfortunately, humans aren't that good at expressing their needs in speech. We can usually talk about our explicit needs, but we also have visible and latent needs that we aren't aware of. To fully understand the needs it's not enough to only talk to people, you need to observe them and interact with them.
A brief history of User Experience so far, emphasizing the differences between traditional UX work and Agile or Lean UX work. Agile development as well as Lean startup has had great impact on the UX work, and UX professionals have had to adapt to working in short iterations, e.g. Scrum, and to focus on the Minimum Viable Product.
If you want to have the best of both worlds - how do you make it work? Traditional organizations, tools and methods are not always well suited for Agile development, but there are ways of adapting to create focus on the needs of the end-users.
My interest in the human brain is what led me to study Cognitive science where I specialized in Human-Computer Interaction. I've worked with Usability and Business requirements for over 10 years, with everything from truck displays and workshop systems to public computers and healthcare telephones.
My first encounter with Scrum was as a Project manager, and it was love at first sight. Since then, I've strived to combine User experience work with Agile and Lean because I believe the combination can bring the best of two worlds together to build great things!
Craftsmanship is about skillfully creating useful, well-wrought items, for example furniture and glassware. The term sounds like it’s straight out of a description of the middle ages, yet many of the best software developers in the world have signed their names to a manifesto that values “well-crafted software” and pledges to “help others learn the craft”. What are they on about? Surely software development is a branch of engineering not carpentry? I’d like to take you through the manifesto for software craftsmanship, explain the background and what it means in practice for developers on an agile team.
This is all about successful software development in the 21st century - fancy wooden chairs and hand blown wine glasses will not feature, I promise!
Emily Bache is an independent consultant specializing in automated testing and agile methods. With over 15 years of experience working as a software developer in organizations as diverse as multinational corporation to small startup, she has learnt that to be truly agile, teams need to learn use agile engineering practices.
Emily is the author of “The Coding Dojo Handbook: a practical guide to creating a space where good programmers can become great programmers” and loves to coach and teach developers about Clean Code, Test Driven Development, Refactoring, and more.
Emily speaks regularly at international events such as Agile Testing Days, XP2013, ACCU, and recently gave a keynote address at “Test Automation Day” in the Netherlands.
Because we are a small, non-profit, organization we must enforce a strict no cancellation policy. No return on tickets to the event. Program subject to change at any time.
If you are interested in being a sponsor, mail: email@example.com