Improve your entire delivery process from beginning to end by joining Gojko Adzic exclusively for both the Impact Mapping workshop ánd the Specification by Example workshop!
Are you bothered by a lack of collaboration between the business and software development?
Have unclear specifications caused delays during the development process before?
Has your team experienced problems during production that are caused by simple miscommunications?
Join the creator of Specification by Example, Gojko Adzic, and let him teach you personally how to
get the business and the development team on the same page and
how to create a mutual understanding within your team and organization.
The Specification by Example workshop!
Specification by Example is a collaborative approach to defining requirements and tests based on capturing realistic examples instead of abstract statements.
It is the cornerstone of any successful requirements strategy with agile and lean processes, such as Scrum, DevOps, Extreme Programming and Kanban.
This workshop teaches you how to apply Specification by Example to bridge the communication gap between stakeholders and implementation teams, how to build quality into software from the start, how to design and how to develop and deliver systems fit for purpose.
Having previously joined Gojko in the Specification by Example workshop, you and your team are now probably confident as to how to turn your planned scope into a good product.
To do that though, you need input. Good user stories, and good ideas for delivery.
For those interested in improving that part of the process, Gojko will be giving:
The Impact Mapping workshop!
Where Specification by Example helps to ensure that teams deliver what the teams and stakeholders agreed to do, Impact Mapping helps you ensure that what you agreed to do was actually a good idea.
Impact Mapping is a technique for creating software project scope from business goals, ensuring that the plan teams work on achieves business goals, and that it is aligned with the company vision, instead of just shipping features. Organizations use impact maps to create good product roadmaps for iterative delivery in agile projects, to create user stories that are small but valuable, and to align all stakeholders on a plan effectively.
Designed for senior level professionals with busy schedules, the Impact Mapping method is easy to understand, collaborative and most importantly: fast.
(Past participants have managed to cut their time from two months to just three days!)