There is a misconception that in Agile development you can plan as you go along. In fact, you still need to plan ahead. What is different compared with waterfall development is that we respond to change over following a plan created when we knew less than we do now.
In this episode, we discuss several techniques for understanding what the desired business outcome is so that we can plan how to achieve the outcome more than, for example, the detailed features that, in any case, we may want to adjust as we start to gather user feedback.
We also talk about understanding dependencies and risks so that those can be planned for, rather than being surprised by them late in the development cycle.
Episode 33: Agile Games and Product Management with Emilia Breton-Lake
Episode 32: Agile in the real world - where theory meets practice
Episode 31: Chatting about agile challenges with ChatGPT 4
Episode 30: Key takeaways from the Agile2023 conference
Episode 29: Business Agility and Agile Transformations
Episode 28: Job hunting for Agile roles
Episode 27: Agile impostors
Episode 26: Fearless Change with Linda Rising
Episode 25: The hybrid working model
Episode 23: Collaboration tools for remote working
Episode 22: Taking Your Position as a Leader
Episode 21: Agile is BS!
Episode 20: When to use Scrum, Kanban, or both
Episode 19: Agile management and leadership
Episode 18: Using Agile in embedded systems development
Episode 17: Fixing Your Scrum with Ryan Ripley
Episode 16: Agile First Responders
Episode 15: Business Agility is the agility that really matters
Episode 14: Backlogs – The Why, What, When, Where and Who
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
Black Wolf Feed (Chapo Premium Feed Bootleg)
Bannon`s War Room