In my post titled Why SAP BI projects fail, I reviewed some reasons why SAP projects fails. In this post I like to add more “Don't” kind scenarios, which help project managers to understand SAP project's pitfalls.
Don’t Misjudge Test Efforts & Time
Mostly project team misjudge test efforts and time take by testing. This is a major assumptions in QA. This is found that mostly team members are so "optimists" when testing that they misjudge the time and resources taken in testing. However being naivety in planning for extremely large test initiatives & assumptions on quality of entrance criteria make team very "Optimists". Being so optimists when testing is a major pitfall in SAP project. Whole team should be never-ending pessimists.
What's we lose when we are "Optimists" when testing:
1. It grounds overlapping of test phases – very complicated to manage & caused lots of rework & re-testing.
2. It make test schedule behind.
How to be an pessimists when testing. Being an pessimists is easy job, just ask the following questions. Let's take an example a task is given to QA team to test some 400 scenarios with in 4 week.
Question 1: Is it probable to test 100 scenarios a week?
Question 2: Is it 4 week include defect fix time also?
Question 3: Did all test cases in 400 scenarios pass in system test?
Suggestion:
Pertain the same approximation to QA test estimates as there is for development estimates. Think about complexity of tests, integration complexity, conversion requirements.
No comments:
Post a Comment