6
kdvps
1d

Sprint planning, we spot a risk for one of the stories: An old client wants a new feature that relies on a third-party component that has not been included in our integration tests for the last 2 years.

The risk: It's probably not compatible with the new version of our system, if that's true, we'll need to make changes to our system before starting to work on the new feature, and setup integration testing.

Management: - Are you sure it's not compatible anymore?
Me: - No, we would need to bring both systems up and test if they work, there's no automation for that right now.
Mangement: - If you have not checked it's not a risk.
Me: (o_O) ? Whatever, I've warned you.

2 Days later: Our system does not work with this third-party system anymore, we can't finish the feature this sprint.

Management: (☉_☉)

Comments
  • 4
    Next time bring a dictionary and make them search for the term "risk".
    Maybe they think it's just a board game or something.
  • 1
    they think by exporting risk they're doing a good job as managers of things when in reality they're sabotaging the project
  • 2
    They caught a bad case of the stupids. It’s contagious at high corporate elevations.
Add Comment