If a project has forsaken to undertake a cycle of eliciting and documenting requirements, what level of risk does it introduce, how is this addressed and whom does it sit with?

  • How do you know what you're building if you have no requirements? Seems more like a blocker than a risk. – Phil192 Aug 15 '15 at 10:49
  • The requirements are not documented rather communicated verbally. – Motivated Aug 16 '15 at 1:13
  • This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. – Tob Aug 16 '15 at 7:06
  • If you have no requirements, do you really have project or merely a task that someone asked you to do? – Marv Mills Aug 16 '15 at 19:11

This sounds like it would be a HUGE risk. Because it is huge, I would escalate it at the highest levels of the organization and it needs to be addressed by the project sponsor and project manager.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.