Will you stick to the refined and finalized requirements if you discovered something was wrong in the end?

  1. There was an idea
  2. It was refined
  3. Use cases written
  4. Requirements finalized
  5. Designs finalized
  6. Development started
  • At this point you and the team realize you made a mistake and something doesn’t look right. It could be the UI or the UX or the functionality
  • What do you do now? Carry on with what was decided?
  • Do the needful and make changes to the original scope?

What authority do you and the team have?

In reality it will tend to get raised, escalated to the decision makers and decisions made regarding what is lower risk to carry on doing or do something less risky that does not depend on this whilst that re-design takes place.

Lots of factors to consider but its usually a risk decision that you want to be as informed as possible.

3 Likes