There are many commonly held myths about agile. Two of these myths are that agile projects don’t do any planning and that you can’t do agile on a fixed date project. On the other hand, organizations have customers they want to satisfy and operations to run. And sometimes they feel a need for planning, and sometimes they face a fixed date. Can we simple neglect these feelings or must we exclude such projects from our Agile world? Valid requests for fixed date or mid-term planning In my daily practice I meet questions like:
- How much can be done by a given date? So that we can prepare our Sales people training in time.
- When can this set of features for our product be shipped? So that our clients can prepare their systems for it in time.
- How many teams do we need working on this project? So that we are in time for the due date set by the Regulations Authority. If we set off too slow, we know that catching up often is very hard and requests measures like doubling the capacity before you know.
- When can I plan the project resources for another/next project? So that I know whether I need to hire extra resources or not.