Testing is important for the maintenance of quality of your project, and this short tutorial video explains three reasons why and how not to derail the testing phase of your project.
Here’s a shot of the whiteboard for your reference!
Jennifer discussed how crucial planning for testing is for the success of your project. It can be tempting for teams to cut the testing period when deadlines loom and time is tight, but it will inevitably impact the quality of the product.
As the project manager, you need to maintain the integrity of your process, and planning for quality testing throughout the life of your project is one way to ensure quality targets are actually met.
But isn’t testing just a given? Why do I need to plan for it? Consider these three points in favor of planning along the way:
- You know early on what needs to be tested, as well as when and who needs to test it. Testing is not always best performed right before release, and when you plan ahead, your team will be more likely to communicate what needs testing. That way, you don’t find out too late!
- You’ll be prepared for changes to the schedule, allowing you to know what can be cut or deferred
- You’ll likely save time and money, avoiding rework due to errors or un-planned for testing.
Now that you know that testing is key, there are best practices you should apply for getting the best results from testing. They include:
- Establish agreement about quality measures among all team members and stakeholders
- Plan the work and work the plan (which includes testing!)
- When crisis hits—and it will!—reference your testing plan.
Pro-Tip: Use your planning tools to create quality measure milestones in the project. These can be marked by the whole team and celebrated together. It will help keep quality top-of-mind for the whole team, if they are reminded along the way when they’re on track.
For further Tips for Quality Testing, check out this article by Elizabeth Harrin.
Thanks for watching!
Hello, everyone. Today, we’re talking about three reasons why you should plan for testing.
You know as soon as you finish your plan, things are going to change, and when things change, you can reference the triple constraint, which is a tool that helps balance the scope, the cost, the time and quality of your project.
In crunch time, when people start looking at trying to reduce the time in the schedule, it can be tempting to cut testing. Let’s look at what that means.
When we talk about cutting testing, it impacts the product, the deliverable we’re producing as part of the project. There’s an entire product development life cycle, which includes the analysis, coming up with the requirements of the product, the design and development of that product, the quality assurance and testing that make sure it complies, the implementation and deployment of that product, and then turning it over for maintenance and support. When we talk about cutting testing, it’s talking about removing an entire process of this product development life cycle.
We don’t want to do that. Instead, that’s why today, I want to talk about why it’s so important to plan. Let’s look at a couple of reasons why.
Number one, it sets the stage. It lets you know what needs to be tested, when it needs to be tested, and who needs to test it. It also prepares for change because within the plan, it identifies when you start looking at alternatives what could possibly be cut, and what could possibly be deferred. It also helps to reduce the cost of the rework because errors do cost. They cost in money and they cost in time, so it can actually extend the project.
Here are a few best practices. One, establish agreement among the stakeholders the mandatory testing requirements. Plan the work and work the plan. In this case, testing. In a crisis, reference your plan instead of the temptation to cut testing.
If you need a tool to help you plan your testing, then sign up for our software now at ProjectManager.com.