I think we are majorly influenced by these items when we prioritize our task. The great one said – “ Prioritize what;s on your schedule and not what is not “ & Like one of my friend retorted – if there is nothing on schedule how do you prioritize?
1. Time/Schedule influenced?
2. Customer influenced?
3. Bugs Per Test value? (or some other ROI measurement)
4. Code changed vs. tests that cover code?
5. Code Complexity?
6. Hard to prioritize most important activity – i.e.: choosing between increasing coverage and automating a regression
--I think I disagree with this, but I'm not sure what it refers to. Are we referring to the general case of prioritizing what the testers should do?
7. Estimating time / costing for new projects
8. Estimating time to zero bugs (release ready)
9. Testability
Customer scenarios increase testing complexity; testability of our products; what do I test vs not test? Automate vs. not? Code coverage vs. not? Etc.
Vinay Jagtap
A hard core Technocrat with over a decade of extensive experience in heading complex test projects coupled with real time experience of project management and thought leadership. Extensive experience in Performance, Security and Automation Testing and development of automation frameworks and ability to setup and execute Global service centers and Center of Excellences for testing.
