All those issues will be lost in backlog and meetings, like tears in the rain

Discussions
,
1

(not) funny stuff you can (not) change

— The release is unstable. Devs and QAs say they need more time.
— No delays. Ship it.

— QAs are reporting critical bugs and high risks.
— We’ll fix it later. Ship it.

— QAs need better testing tools, data, strategy, and approaches.
— We have no budget.

— Engineering says they need more staff to meet deadlines.
— We have no budget. Stay agile.

— The system can’t handle even 10% of our users; nothing is working.
— We’ll fix it later. Ship it.

— We found major vulnerabilities in the system.
— We’ll fix it later. Ship it.

— We need a proactive, effective approach to avoid leaking security issues.
— Valuable feedback.

— Users are furious. The latest update broke key functionality and corrupted their data.
— Valuable feedback.

— We need to fix major bugs immediately.
— We’ll fix it later.

— Support is overwhelmed. Tickets are piling up.
— Optimize workflows.

— User data loss and corruption are happening in real time.
— We’ll fix it later.

— The engineers are leaving the company.
— Stay agile.

— The employees ask difficult questions and disagree with management decisions.
— Let them go. Stay agile.

— Our hardware is too slow for efficient development.
— We have no budget. Stay agile.

— We need more effective leadership and goal-setting strategies to achieve our objectives.
— Valuable feedback.

— We need proper, thorough testing before shipping.
— No delays. Ship it.

You’re passed. You’re showing great management potential!

Got any to add?

4 Likes
2

— QAs need better testing tools, data, strategy, and approaches.
— We have no budget.

This one hits home.

My addition:
Don’t log the UI bugs in JIRA, put them in a sheet we’ll fix them later!

2 Likes
3

This one from my side :

The client doesn’t have money to continue the project.
Don’t fix the problem. Ship it

We need fast development and fast deployment.
No delays. Ship it.

1 Like
4

This is so true, management just want to see that deployment is done, see that new features are developed and they don’t even listen enough to see that it is better to ensure that the quality of what is being deployed is like 90%