Today's Big Picture

Oct 27 2010   7:10PM GMT

Marching Towards Crunch Time

Shilpa Venkateshwaran Shilpa Venkateshwaran Profile: Shilpa Venkateshwaran

Every tester has had to deal with crunch time during the test phase. Testing is always towards the end of the development cycle and invariably something goes wrong upstream that causes the testing crunch at the end. There could be various reasons for this crunch time: Budget cuts, scope creep, hitting the dates, uphill deliverable dates slipped, etc.

It is important to be prepared when marching towards this crunch time.

  1. When you have down time in the beginning, take it as down time. No matter how fast testers get their analysis done, test cases written there are chances things will change again. So don’t feel guilty in taking the down time. But the other side to this is that when its crunch you have to give it all. You will have to make up the time to get the work done. Its give and take policy that you can discuss with your project manager or team manager. What counts the most is getting what needs to be done to get the product out the door. We can sit and complain but if the product does not go out the door, then we have failed as a team including the testers. So we can complain about it or plan it ahead to balance work.
  2.  When estimating, plan some buffer time that can be used in the end when there is time crunch. You can do this hidden (don’t share with your project team – beef up estimates 10%) or you can let the team know what you are doing. This is not the best way but if you have been burned in the past then this could be something that you can discuss with your manager or department head and get a buy in from them.
  3. Cross train people in different projects. So if you have tester colleagues who are working on other projects, you can train them on your project and you can get trained in theirs. So during crunch time you can use their help and vice verse.
  4. Constantly go over the list of changes that are being planned in the release. See if there are areas/features that are being heavily affected. Plan more testing in those areas. During your downtime clean up regression test cases for those areas so you can have good test cases that anyone from your project can execute. You can use your cross trained colleagues or other resources (BSA or SE) from your project to help with testing those areas. This way you know your test cases well (since you reviewed and updated them) and you know exactly what they are doing when testing.
  5. Risk Ranking everything including regression test cases will help. Communicate this to your team and let them know as the time is crunched, you will be taking things out of the list that have lower priorities (less risky areas). Use different colors to show things that will absolutely have to be executed and things you can compromise on. Get a buy in early on from the team and management.

Its easy to stress about crunch time since we know its coming or we can go into the war fully prepared.

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: