In agile, planning is crucial. We want to do the right things, and we want to do them right. We do our best to avoid waste. So we need planning.
We do at least a Sprint planning for our Sprint, and a daily stand up to haven a synchronized daily plan. We prepare the planning with refinements, and we plan how to plan better in retro. And planning is not one-wo/man-band, the whole team is included and taking over responsibility.
But we always keep in mind: Our goal is not to fulfil the plan. Our goal is fulfilling the sprint goals with an outcome having the highest possible value.
We are learning during the sprint, and also our customer is learning. Objectives, goals, values, features and user stories can be a moving target.
And as soon as we know that following the plan is waste, because there is a better way to do it – we say “¥€$ we can”, and we’ll do it better.
Responding to change over following a plan (Value #4)
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. (Principle #1)
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. (Principle #2)
Manifesto for Agile Software Development