1 / 32

Enhancing Demo Effectiveness: Lessons from Exilesoft's Chief Scientist

In this insightful session led by Johannes Brodwall, Chief Scientist at Exilesoft, we explore the challenges faced in delivering effective product demonstrations. Part I focuses on common pitfalls, such as showcasing low-value features and improper database presentations. Part II introduces the Rainbow Plan for slicing requirements, emphasizing the importance of defining what is necessary versus nice to have. In Part III, we discuss valuable learnings from customer interactions and sprint meetings, highlighting the importance of demonstrating value consistently. Join us to refine your demo strategies and enhance customer engagement.

xandy
Télécharger la présentation

Enhancing Demo Effectiveness: Lessons from Exilesoft's Chief Scientist

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Requirement slicing Exilesoft Johannes Brodwall, Chief scientist Exilesoft

  2. Part I:

  3. Giving good demos

  4. Problem: Showing database in demo

  5. Problem: Showing code in demo

  6. Problem: Showing low-value features in demo

  7. Part 1c statement

  8. Part II:

  9. Slicing requirements

  10. Rainbow plan

  11. What is nice, what is required?

  12. What can we show?

  13. Part III:

  14. What did you learn

  15. «Customers»

  16. What did the teams show at demos?

  17. Teams

  18. Sprint overhead

  19. Demo readiness

  20. Sprint planning meeting

  21. Who is your… Customer? Product owner? User?

  22. «Business analyst» (and «developers»)

  23. What was your product backlog ordering?

  24. «Developers» (and «analysts»)

  25. Technical platforms

  26. Technical debt?

  27. «Everyone»

  28. Can we demonstrate value every 15 minutes?

  29. Can we demonstrate value every 2 weeks?

  30. Conclusion:

  31. Delivering value is a matter of practice and reflection

  32. Thank you jbr@exilesoft.com http://johannesbrodwall.com http://exilesoft.com http://twitter.com/jhannes Demonstrate value every sprint

More Related