“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

Geckoboard Code in the Dark

From a Salesforce Idea to a Lightning Web Component (LWC) Knowledge Widget

A Brief Introduction to Apigee CICD Pipeline

Launching WordPress In Public Subnet And MySql In Private Subnet With Bastion Host.

Product Acceptance

Roblox Drive City Codes 2021

Roblox Drive City Codes 2021

Replicating big datasets in the cloud

How to choose the right software house for your project

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

It’s all a Blur

“Burndown & Control Charts” from an Old Blog

Biases and the Toll on Daily Life

The Implementation of Social Media Marketing, with a look at the Virtual Influencer