Your assignment1 is not a good one because it doesn't have any specific or measurable goals for success2. Once you've defined your goals the rest of the process falls into place.
1. How to introduce QA into an organization? [Choose Metrics]
Here's the process to follow:
- Choose your goals (an improvement in some metric).
- Before you change anything, do some measurements and see how you're currently performing3.
For demonstration purposes pick a couple sample metrics4:
- Regression bugs introduced
1. I'm assuming this question is about adopting new QA processes into an existing department.
2. What does it mean for quality to be "baked-in"?
3. Oddly enough you may find out that measuring something, paying explicit attention to it, solves the problem.
4. I picked these at random to show how the process works.
2. How to break up QA into parts that others can do? [Implement Changes]
This is the step when you make a single change, per goal, and then measure the results.
You have lots of options here. You might choose to pick a single person to champion each change and try to prove its effectiveness.
For reducing down-time you could implement:
- System monitoring (AlertSite)
- Testing of critical infrastructure
For reducing regression bugs you could implement:
- unit testing
- code reviews
3. How to prioritize what needs QA?
This should be the first step. What needs QA is something that has an associated metric that you're trying to improve.
4. How to determine what to buy? code? etc. [Automate What's Proven to Work]
Don't start thinking about what you can buy when the process starts. Only after you make a change and see that some metric has improved, should you consider automating that change.
For anyone who is better than I am at formatting posts feel free to change anything above