Agile Does NOT Mean ZERO Planning...
Before diving into how I managed planning for this project, it’s important to understand what a plan is and the role of agile planning.
A PLAN is a detailed proposal for doing or achieving something. It’s like a beacon, offering stakeholders a clear vision and placing realistic expectations. It can project a rough timeline for marketing activities, too. The book Agile Estimating and Planning, by Mike Cohn introduces plans as guidance to investment decisions, helping us know who needs to be available to work on a project during a given time and if a project is on track to deliver the functionalities that the user(s) may need and expect. In short, plans usually take the form of documents or figures. They are a big picture of how a project is supposed to unfold.
PLANNING, however, is a quest for value. It is an activity done continuously responding to the feedback from users. Planning helps the team adjust their original plan towards the final destination. To serve different purposes, product teams structure and frame different levels of planning. In a fast-paced world, Agile teams achieve this by planning at three horizons — the release, the iteration, and the current day.
How to connect with AgileDad:
- [website] https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/
