Pitfalls of Configuration Management

Document all the new IT 'stuff' aka software, patches, middle-ware, hardware, network and security updates and go back and ensure all the previous documentation is updated.

Finding the elusive IT software owner...who configures this software for what it does? And then try to pull the teeth that are 'configuration items' to see if they've been documented, (which it is likely that they have not).

Do that with minimal resources, (human power) and make it happen yesterday. These are just the starting pain points of managing configuration.

I brought more Testers than you did.....

The more eyes the better and when those eyes do nothing but look at bug and issues and requirements all day they are trained in a way that our business testers will never know.

https://www.youtube.com/watch?v=lSHuma375Ec

Casandra effect - Leading Quality

Casandra was cursed to know the future by Zeus with one caveat that being no one would believe her; as a leader in QA this will be the position you'll be put in on a daily basis.

Rinse and repeat

Who else uses the vendors you're testing for, provide them your test beds?

What to do when you don't have them?

How to build a stage or mirror of PROD and why do that?

Formula for Level of efforts and the swags

Resource allocation and how to 'swag' or an estimated Level Of Effort, (LOE).

If dev time was 100 hour is 50 hours of QA enough?

How would you know if you had no requirements documentation?

Who will be testing? QA or The business.