Related Posts
What is your 5 year plan?
Additional Posts in Software Engineering
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
What is your 5 year plan?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

This is one of the few places where I’ve actually seen solid speed up from using AI tools. Are you able to use them at your org?
fix the message then load the page because send the profile but update the update1941.
read the report but assign the user but type the plan so scroll the post86.
Thank you for asking, you gave me a bunch of ideas for a LinkedIn post.
Just a few thoughts...
- If you are testing something that if things don't work right it would be catastrophic such as people dying or half of the world having a blue screen of death, I might use that. Is it worth risking those things just to stay on schedule? Of course you have to be tactful about it so do that with caution.
- In most of the organizations I've worked for, it's the product owner that decides what bugs are important enough to fix vs ship. As a result, I've always viewed my role as merely the person reporting the bugs. What the product owner or business folk decide to do with it is not my concern. They'll have to live with their decision. But I've mostly worked on internal enterprise software projects, not customer facing SaaS products.
- It's too late for this one but always try to streamline and automate as much of your work as possible so that you aren't asked to speed things up since you're already very fast. (They wouldn't ask you to hurry things up if all you have to do is run some tests for 3 hours.)
- Never just ship it and hope for the best. In certain organizations, that will get you fired if something goes seriously wrong. But if they really really pressure you, have them sign a release form that releases you of all liability if anything goes wrong. Just kidding, mostly. You do have the prerogative to decide what tests are most important to run based on risk and likelihood to occur. Maybe you don't need to run all 50000 regression tests and could get away with a smaller subset?
Chief
I feel it every sprint because my team takes a while to get through their dev work and burn down doesn’t occur until it passes qa and product review
I joined project that didn't even have regression testing. I discovered THAT when I spent a month being blamed for a breaking a feature that was never implemented; since QA never tested it, "it wasn't broken before".
If they are cutting testing in half, and being on schedule is the highest priority, then the decision has already been made to ship low quality. Make your concerns known and re-iterate the consequences, and let management take the heat for a broken product.