Gathering thorough and appropriate requirements is a critical piece of a successful project. Very often, even a well-scoped project can get derailed by poorly gathered or managed requirements. This article will outline four practices to help you breathe L.I.F.E. into your requirements.
Project teams usually wait for requirements to be ripe before attempting to collect them. But would it be helpful if they collaborated with business teams to identify, prioritize and prototype the requirements? The answer is a resounding yes.
Have you realized that your organization is not putting enough attention on requirements? Wondering what types of tools are out there and how much they cost? Do you even need a tool? And if so, what kind?
Requirements cannot stand alone. So why do we so often fail to acknowledge that connection to other project elements...and what is the consequence of that failure?
|
"Managing senior programmers is like herding cats." - D. Platt |
