1. How to handle unclear requirements in project management | practical tactical tips for managers
This video provides a clear, real time, practical tips and tactical tips for handling unclear requirements in real-time project for experience project managers and new project managers.
Even this can be considered as an interview question for project management interview.
Let's look into some tactical tips, to handle unclear requirements in a project.
In a poll recently conducted in a recognised project management forum regarding the project challenge,
the majority of the project managers acknowledged that unclear requirements are, without a doubt, a top challenge for their real time projects practically.
Starting with unclear requirements is like, heading off on a journey without knowing your destination.
The most common reason for the project managers to start the project without clear requirements is, Senior Management Pressure.
They accept the ambiguous requirement specifications and proceed with project estimations.
Eventually the result would be, project gets delayed, cost gets doubled, client's quality expectations are not met, and, in the end, the project manager gets the blame.
What would be the best way forward to handle this situation practical?
First tactical tip for handling unclear requirements for new and experience project managers is , Make assumptions visible. Yes, That should be the first tactic that I recommend.
Second tactical tip for project mangers is, Log a risk.
In practical, Record in your risk register that your estimates are based on unconfirmed assumptions.
Third recommended tactical tip for handling unclear requirements is, Discuss when in doubt.
Fourth tactical recommendation for handling unclear requirements is, Be agile and Go phased
You can go for the iterative development life cycle and start with what you have, reaching out to clients for their feedback at every stage of development.
Use this feedback to fine tune the requirements, thereby hashing out all uncertainties.
Final tactical tip is ,put buffer on estimates.
Last, but not least, have a buffer on the estimates, account for requirement changes.