“Common Project Risks and Agile Mitigations, Part 7, Everything Else” from an Old Blog

  • tension in social relationships; people (often respected staff) who, for one reason or another, block progress.
  • missing, or delayed access to, information resulting in untimely decision-making. (Shari Pfleeger [May] notes the common situation that “there isn’t one person who has an overview of the whole project.”)
  • not learning from past problems and/or ignoring the need to act on what has been learned.
  • inadequate procedures, strategies, and tools to be used in testing; late involvement of the test team in the project.
  • poor vendor performance delivering on a contract; for vendors of contract staff, a concern was offshore-outsourcing relationships as engineers sometimes must train colleagues who do the same work for much less pay. (Vendor contract issues were not mentioned much, but were a high % item when they were.)




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

Recommended from Medium

x64 SLAE — Assignment 3: Egg Hunter

How to deploy Rails 5.2 on AWS EC2 + Ubuntu + Nginx + Passenger

How to “Open the Floodgate”: Trading Bot API user guide

Minting Harmoonies NFT On MetaMask

First Flutter App

Introduction to GDB

Why Quality Assurance Is Important? Here are top 5 reasons behind it

LSB Steganography — Hiding a message in the pixels of an image

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

Meet the Guide: A series about the Forest Therapy Guides I meet on their trails around the world.

Stacking Bricks

What’s better than a plastic bag? In ABQ, more plastic bags

What’s Stopping You from Achieving Your New Year’s Resolution or Goals? by Laura D. Harver