So Agile development is great for iteratively working closely with customers to develop and refine information systems that are useful to them and the organization.
But even in Agile, there is a beginning and an end to the sprint planning and project management.
Taking Agile to somehow mean endless in terms of adding more and more requirements or scope creep is not what is intended.
Agile has to be bound by common sense somewhere between what is needed for a minimally viable product (MVP) and what is achievable with the designated resources, objective, and scope.
Good project managers always have to be sound arbiters and be willing to ask the tough questions and determine if something is truly a requirement or simply a wish list item that is out of scope (but of course, could perhaps make it in for future enhancements).
We need to understand the difference between genuine customer service and irrational project exuberance based on inflated expectations.
It’s not a dangerous project bubble we want to create that can and will get busted, but rather a successful project that is delivered for our customers that help them do their jobs better, faster, and cheaper. 😉
(Source Photo: Andy Blumenthal)