Consulting on processes
Uniformity in your test processes is a good thing.
Are you aware that there is a big difference between Severity and Priority?
check your Jira, Azure or Tosca test management parts against this fact. How are they displayed? if needed, change it (in line with to the read-on link)
Ensure absolute uniqueness in your terminology—avoid ambiguous combinations like "priority=medium AND severity=medium." Embrace both 'Priority' and 'Severity' in your defect/bug tracking process.
Make sure to use them BOTH in defect/bug tracking, 'Priority' as well as 'Severity'!!
Make sure to understand a (example) [ Priority:Medium with a Severity:Moderate ] does NOT say anything about your washing program...(your test effort planning)
Make sure to understand that next to the fields Priority and Severity you also can (advisibly) have a field: 'Attention'. (Least, Average, Maxium) washing program...(your test effort planning)
This is the first free takeaway/giveaway... in consult.
check your Jira, Azure or Tosca test management parts against this fact. How are they displayed? if needed, change it (in line with to the read-on link)
Ensure absolute uniqueness in your terminology—avoid ambiguous combinations like "priority=medium AND severity=medium." Embrace both 'Priority' and 'Severity' in your defect/bug tracking process.
Make sure to use them BOTH in defect/bug tracking, 'Priority' as well as 'Severity'!!
Make sure to understand a (example) [ Priority:Medium with a Severity:Moderate ] does NOT say anything about your washing program...(your test effort planning)
Make sure to understand that next to the fields Priority and Severity you also can (advisibly) have a field: 'Attention'. (Least, Average, Maxium) washing program...(your test effort planning)
This is the first free takeaway/giveaway... in consult.
| Priority | Severity |
|---|---|
| Low | Cosmetic |
| Medium | Minor |
| High | Moderate |
| Major | |
| Critical |
Read on about that aspect here...
And if you'd like to get more similar tips, and get far more advice in such important aspects as these, please give us an e-mail.
And if you'd like to get more similar tips, and get far more advice in such important aspects as these, please give us an e-mail.
Considering Break Methodology rule #16...
items can have the same category "high priority", but there can be only 1 item #1 on the list!, make sure to have something similar like: high priority #1, high priority #2 etc. Those are the Break methodology rules.
items can have the same category "high priority", but there can be only 1 item #1 on the list!, make sure to have something similar like: high priority #1, high priority #2 etc. Those are the Break methodology rules.
Understand that your test effort planning may resemble something like:
| (Sprint) Item | Priority | Prio Category # | Severity | Attention | Poker Points |
|---|---|---|---|---|---|
| Item 1 | High | 2 | Moderate | Least | 8 |
| Item 2 | Medium | 1 | Minor | Maximum | 40 |
| Item 3 | High | 1 | Critical | Average | 13 |
This makes sure that you understand the concept: labeling a bug (or feature) is not the same as understanding there can be a fix script order.
Item 1 of the Sprint is only number 2 of the high priority category and Item 3 of the Sprint is number 1 in the high priority category. (the only possible chronological fix order for example) (like a movie script you film every scene regarding a Island on 1 certain day for example)
Item 1 of the Sprint is only number 2 of the high priority category and Item 3 of the Sprint is number 1 in the high priority category. (the only possible chronological fix order for example) (like a movie script you film every scene regarding a Island on 1 certain day for example)
Break software testing also provides in help with overal direction in software testing on a top level.
click here if you want te check-out the beta content about it...
click here if you want te check-out the beta content about it...
Although there might be a lot of people that would like to see software testing as something systematic and static, it will always be something that will organicaly grow (in a company) and is very context dependend.
