So you have somehow got the job as a Product Owner and all you have to do now is to look at the feature wish list and prioritize it? It perhaps was not that simple.
This is not just another course. With 5 leading, published experts in a two day intense camp filled with practical exercises, you will be at a higher level of expertise after this.
Get the big picture of your product without losing the grip of details, prioritize dynamically as the world around you changes and stay in touch with the passion for your product.
and Christian Hassa
will teach you Impact Mapping.
goes through Effective User Stories
makes you rise to the knowledge of Discover the whole story of User Story Mapping
presents the intrigue idea of Concepts.
All this will help you to build an awesome product that meets the market spot on.
See also the international site
for this camp.
Who this course is for
You have some experience as a Product Owner and perhaps already are a CSPO.
Learning outcomes for this courseImpact Mapping: How to make a big impact with software products
with Gojko Adzic and Christian Hassa
Impact Mapping is a strategic planning technique that prevents organisations from getting lost while building products and delivering projects, by clearly communicating assumptions, helping teams align their activities with overall business objectives and make better roadmap decisions. Impact mapping can help you build products and deliver projects that make an impact, not just ship software. The half-day workshop is aimed at product owners, business analysts, developers and testers working primarily in an agile or lean environment. It is based on Gojko Adzic’s books Impact Mapping. We’ll cover:
Effective User Stories: Getting the most out of iterative delivery
with David Evans
- how to ensure that you’re building the right product
- how to align the activities of delivery teams and the organisation around them
- how to make an impact with software products and projects
- how to communicate overall goals and vision to delivery teams
Stories seem like a simple enough idea. But the notion of a Story can mean different things to different people. For some it is the common “As a… I want… so that…” template, for some it is an index card on a board, for others it is merely a “promise to hold a conversation”. Product Owners are ultimately responsible for a team’s Stories, but not all Product Owners write all the stories, and many POs are challenged by issues such as:
- How much should I write down, and where should I write it?
- Should a Story be a requirement, a solution or both?
- What about technical stories, and what about bugs?
- What is the difference between acceptance criteria and acceptance tests?
In this session we will look at the essential parts of a user story by considering its value and form at different times in its life-cycle. We will cover:
User Story Mapping: Discover the Whole Story
with Jeff Patton
- Story Naming guidelines
- Alternative templates
- Finding the right level of detail to document
- Media choices and their pros and cons
- The difference between stories and specifications
In ideal Agile development teams build small valuable chunks of functionality. But, that’s easier said than done. Not all products or features are small and breaking them down into small buildable parts is challenging. And, even when you do, how do the people building those small parts not lose sight of the big picture?
Story mapping is a simple practice for telling the story of a whole product or feature starting by telling the stories of the users who’ll use it. In this fast-paced workshop you’ll learn the concepts of story mapping by building a map collaboratively with others. You’ll learn advanced techniques for slicing a map to find small viable product releases, and then how to build your product using smaller stories without losing sight of the big picture.
Workshop: Introducing Concepts
with Mattias Skarin
- The creation and anatomy of a story map
- Story Mapping in a holistic product discovery process
- Story Mapping techniques for finding Minimum Viable Release candidates
- Story Mapping techniques for reducing delivery risk
The product owner is an established role in Scrum. Every team should have one. But is it a solution or a sub optimization? What happens when the PO becomes a bottleneck? The default reaction to the challenge of scale is to build hierarchies of PO’s. At this point it is time to pause and ask; what are we trying to optimize and why?
What would happen instead if we let the person passionate behind the idea, run with it – regardless of role? What if he/she would talk directly with developers? Run with the idea all the way to satisfied client?
Let me introduce to you Concepts and share a case example of applying it in a multi team scenario during the ideation and discovery phases of product development. A concept includes an A3 set by business and development together. It works as an adjustable standard guaranteeing a prepared conversation between idea owner and developers.
Try it out in product development workshop using Lego. Experience the challenges of product development – create something usable under three different circumstances. With a detailed specification, with user stories and using concepts. We will then discuss the strengths and weaknesses behind each approach and how they apply to challenges in product development.
For more information of concepts: crisp.se/concepts
Practical experience as a Product Owner.