Tools for assessing what is a need, and what is a nice-to-have.
This talk is designed to give practical tools for managing scope when faced with the real costs of meeting the original project vision.
The traditional approach to project management is that you create a list of everything the project must accomplish, and then you craft a plan to deliver that list of things. That list is called the requirements for the project.
There is something reassuringly certain and fixed about the term “requirements.” But real life shatters that illusion pretty quickly. We could learn something along the way that means the requirements must change. Or someone could just change their mind as they see the system coming together.
The term requirements then is a bit of a misnomer – it might be more accurate to call them desirements to clearly emphasize that at the end of the day, almost everything’s optional.