Oh, definitely. I personally like the fact that there isn't something stronger than "risk", like "ongoing problem". I.e., "We're building a mobile product and h

Oh, definitely. I personally like the fact that there isn't something stronger than "risk", like "ongoing problem". I.e., "We're building a mobile product and have zero mobile devs". We're stumbling along and figuring it out as we go, so does it jeopardize the project? Well, no. Does it jeopardize timelines, and a whole bunch of non-functional requirements such as stability and security? Very, very much. But I can't quantify those. Or "velocity is X per sprint, and the deadline you've set is 3 sprints, and we have 6X worth of stories". That's not a risk, that's a promise we'll not deliver on time. But then upper management just sees that risk and either just says "well, we need to hit it", adn expect you to magic a solution, or tries to solve it in the only way upper management knows how, by trying to throw more people at it, despite the fact they've all presumably heard of the Mythical Man Month.