Building powerful roadmaps

2. Who am I? • Gino Marckx • Business Improvement Consultant, Coach, Team Builder, Developer • Co-founder of the Toronto Agile Software Development Community • Passionate about making every team thrive © 2018, Xodiac Inc. All rights reserved.

4. What’s in a name? road·map [rōd-map] - noun 1. a map designed for motorists, showing the principal cities and towns of a state or area, the chief roads, usually tourist attractions and places of historical interest, and the mileage from one place to another. 2. any plan or guide to show how something is arranged or can be accomplished: your roadmap to ﬁnancial independence. © 2017, Xodiac Inc. All rights reserved.www.dictionary.com

17. So really… • (Techno)logical building blocks • Schedule driven by technical dependencies • Limited incremental value delivery with little opportunity for feedback • Lack of pivoting options makes it hard to embrace business change © 2018, Xodiac Inc. All rights reserved.

21. A powerful roadmap • A milestone delivers real progress towards the objective, either through value delivery for the end user or through the mitigation of a risk • The description of a milestone informs the team about the goal of this milestone in context of the larger solution • Feedback from every milestone delivery informs the team about which steps to take next © 2018, Xodiac Inc. All rights reserved.

22. Process © 2018, Xodiac Inc. All rights reserved. Identify the problem Build high level solution architecture List risks Sort according to risk exposure Mitigate risks Create new functionality Assess risk reduction Prioritize functionality Map existing functionality (split if possible)

23. Identify the problem • Elevator pitch • Strip context from the problem description © 2018, Xodiac Inc. All rights reserved. @yourconvenience.com  providing an online yet personal corner store experience

24. Build high level solution © 2018, Xodiac Inc. All rights reserved. User Administrator Catalogue Shopping  cart Orders Accounting Content  management Payment  engine Order  management Delivery  service

25. List risks • What if we cannot guarantee speedy delivery of ‘frozen goods’? • What if someone from the other side of the country tries to buy stuff? • What if we are out of the product people want? • What if customers are not interested in the service? • What if our POS system is too old to integrate? • What if credit card transactions are too expensive for small purchases? • … © 2018, Xodiac Inc. All rights reserved.

26. Sort according to risk exposure • Risk exposure = opportunity cost * probability © 2018, Xodiac Inc. All rights reserved. Risk Cost Probability What if we cannot guarantee speedy delivery of ‘frozen goods’? + ++ What if someone from the other side of the country tries to buy stuff? ++ - What if we are out of the product people want? ++ + What if customers are not interested in the service? ++ ++ What if our POS system is too old to integrate? - ++ What if credit card transactions are too expensive for small purchases? ++ +

27. Mitigate risks • Either reduce the probability of the risk occurring or reduce the cost to deal with it • Use planned functionality for risk mitigation • Useful strategies to deal with unmitigated risks • Lure - draw the risk out to force dealing with it • Inform - ﬁnd out more information about the cost or probability • Spy - record information that reduces the cost of dealing with it • Avoid - ﬁnd an alternative solution © 2018, Xodiac Inc. All rights reserved.

28. © 2018, Xodiac Inc. All rights reserved. Mitigate risk Planned  functionality  mitigates  risk? All  functionality  is required to  mitigate? Extract  mitigating  functionality Add mitigating  functionality List risks Assess risk  reduction Mitigation algorithm

29. Our mitigating functionality • Build product catalogue and… • Provide ‘shopping list’ • Offer ‘virtual wallet’ as payment • Offer pay-at-delivery • Show product availability in product catalogue • Arrange pick-up in store • Organize delivery to companies • … © 2018, Xodiac Inc. All rights reserved.

30. Assess risk reduction • Build product catalogue and… • Provide ‘shopping list’ • Offer ‘virtual wallet’ as payment • Offer pay-at-delivery • Show product availability in product catalogue • Arrange pick-up in store • Organize delivery to companies • … © 2018, Xodiac Inc. All rights reserved. • What if customers are not interested in the service? • What if credit card transactions are too expensive for small purchases? • What if we are out of the product people want? • What if we cannot guarantee speedy delivery of ‘frozen goods’? • What if someone from the other side of the country tries to buy stuff? • What if our POS system is too old to integrate?

31. • Build product catalogue and… • Provide ‘shopping list’ • Show product availability in product catalogue • Arrange pick-up in store • Organize delivery to companies • Offer pay-at-delivery • Offer ‘virtual wallet’ as payment • … Prioritize functionality © 2018, Xodiac Inc. All rights reserved.

32. Process © 2018, Xodiac Inc. All rights reserved. Identify the problem Build high level solution architecture List risks Sort according to risk exposure Mitigate risks Create new functionality Assess risk reduction Prioritize functionality Map existing functionality (split if possible)

35. Benefits • Real roadmap allows for prioritization instead of scheduling • Customer can help with prioritization • Delivery remains ﬂexible • Real value at every milestone • Biggest risks are addressed early in the project • Get additional value from risk management process © 2018, Xodiac Inc. All rights reserved.

Building powerful roadmaps

You are reading a preview.

Check these out next

Building powerful roadmaps

More Related Content

Similar to Building powerful roadmaps (20)

More from Gino Marckx (10)

Recently uploaded (20)

Building powerful roadmaps