A good roadmap unites a team and provides direction.
Sometimes, when a roadmap goes wrong, it can feel like an imaginary ball and chain: something you don’t believe in, but you’re tied to it. Promises are made during roadmap creation: what will be delivered on and how much it would cost, perhaps features and timelines as well. Often what is initially agreed upon, won’t be met. In these times the fear of disappointing stakeholders and a tarnished reputation loom. A project could be late and/or overbudget. The blame will fall on someone, and that is usually on the person who failed to deliver on time.
The reality is that in most situations no single person or team is the problem. The problem is that the organisation thinks of a roadmap as a backlog, rather than as the start of a learning exercise. There is also no forum for the delivery team to change direction mid-flight.
We’re hosting a web forum for members of agile teams to learn how to ensure your roadmap will deliver results. The session will be led by Ricardo Escalon our Principal Designer with 15+ years of experience in Agile delivery and Human Centred Design.
This event solves for situations in which:
- Features were delivered, but not outcomes
- Teams don’t believe in what they are building
- A project is late and overbudget
- There is no time to really understand the problem you are solving
This event is perfect for product owners/managers, UX designers, technical architects and project managers who want to participate in an active learning experience.
The session is very interactive with activities that will be conducted in groups with like-minded peers. At the end you will leave with helpful frameworks and tools that will help you in creating a strong roadmap for your organisation.
Learn how to avoid common pitfalls which can lead to a product that has no impact. Know what is required for successul roadmap.
Know the common ways in which leaders can get caught up in features rather than what really moves the needle.
There is nothing worse than being constrained by a scope which is no longer relevant. Learn how to avoid issues like this.