“Common Project Risks and Agile Mitigations, Part 2, Requirements” from an Old Blog

  • Discovery that there is no more need for certain requirements (or the system as a whole) to be developed.
  • Late recognition of the seriousness of requirements repercussions.
  • Mid/late-development changes in requirements and scope.
  • Inadequate acceptance criteria, which results in “poor-quality” delivered software.
  • Incomplete, ambiguous, inconsistent, and/or unmeasurable requirements (and other project objectives).
  • Unrealistic Expectations.




Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Galaxy Shooter 2D — Web GL

Kotlin vs Java: Performance Drill down & Which to choose

How to manage all my K8s secrets in git securely with Bitnami sealed secrets

Some people might take interest. Some may support you in your quest. But at the end of the day,

How Nylas got SOC 2 Certified and Why it Matters

How you can use Artifical Intelligence in your xamarin apps (a real-world example)

Five stages of RISC pipeline

Puzzles in the Terraverse: Chapter 2

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Scott Duncan

Scott Duncan

More from Medium

What’s Froge?

Salient v14.0.5 — Responsive Multi-Purpose Themes

Ecological Reciprocity: A Treatise on Kindness

Nova Science Publishers Ecological Reciprocity

October Sky