Requirements, one of the most important, if not, THE most important artifact in any project. Managing them is most probably one of the toughest task (second to managing PEOPLE, of course !) that any seasoned project manager will attest to. Many projects failed or often gets delayed because requirements are not managed properly.
It is simple yet complicated. It is known yet unknown. It is understood yet misunderstood. it is documented yet undocumented.
At best, managing requirements is a misunderstood activity. Often, gathering requirements stops at talking to business folks. Often, it stops at explicit requirements.
At worst, managing requirements is a mishandled activity. Multiple or no requirements owner. Not documented, initially may be but as the project progresses, the requirements document are not updated accordingly. Not properly prioritized. No unique identification. Not traceable to the originator nor to the implementation.
But worry not, requirements can be managed successfully. The first step is to realize and accept the common pitfalls as mentioned above. Second step is to identify and develop suitable procedures, process and templates as well as identify suitable tools. Third is to get everyone aware and trained on those procedures, process, templates and tools. Fourth, to implement auditing and reporting to ensure the procedures, process, templates and tools are being practiced as intended. Last but not least, those procedures, process, templates and tools should be continuously evaluated and improved.
If you would like to know more on the process, procedures, templates or tools, please connect with us.
It is simple yet complicated. It is known yet unknown. It is understood yet misunderstood. it is documented yet undocumented.
At best, managing requirements is a misunderstood activity. Often, gathering requirements stops at talking to business folks. Often, it stops at explicit requirements.
At worst, managing requirements is a mishandled activity. Multiple or no requirements owner. Not documented, initially may be but as the project progresses, the requirements document are not updated accordingly. Not properly prioritized. No unique identification. Not traceable to the originator nor to the implementation.
But worry not, requirements can be managed successfully. The first step is to realize and accept the common pitfalls as mentioned above. Second step is to identify and develop suitable procedures, process and templates as well as identify suitable tools. Third is to get everyone aware and trained on those procedures, process, templates and tools. Fourth, to implement auditing and reporting to ensure the procedures, process, templates and tools are being practiced as intended. Last but not least, those procedures, process, templates and tools should be continuously evaluated and improved.
If you would like to know more on the process, procedures, templates or tools, please connect with us.
RSS Feed
