In general, the ISTQB Advanced – Test manager defined a complete process include planning, monitoring and control, Analysis, Design, Implementation, Execution, evaluating exit criteria and reporting, Test closure activities, are applied to the projects, however, depending on the context of each project, these activities will be arranged or combined differently.
As a Test Lead who has a process of learning and applying ISTQB advanced – Test Manager (TM) knowledge to work and playing the leading role in the testing team over the years, I would like to share some experience in Planning, Monitor & control in the projects:
Test planning
As definition, test planning activities start at the initiation of the test process for each level and continue throughout the project until the completion of closure activities:
- Identify the activities and resources.
- Identify the methods for gathering and tracking the metrics.
- Determine the test Strategy including.
- that will be used.
- Decision which Tool will be in testing and test management.
- Training plan if needed, and documentation guidelines can be established.
- List out the specific features of the software that are within and not with in its scope.
- Analyze Risk information, and experience history… to Determine the priorities of the various testing activities
- Define the initial test environment specification.
- All external dependencies and associated service level agreements (SLAs) should be identified and, if required, initial contact should be made.
Not all the criteria mentioned above are always decided during the planning stage in projects. However, if we implement those aspects correctly, we will have a precise and efficient plan.
I worked on a challenging project in which we only had minimal information regarding the main system objective, activities and resources, and system goal. We used the testing tool, the management approach, the testing types and levels, and their goals, as well as the documentation based on Company standards. We discussed with the development team to specify the test environments and data management procedures, and the way we build on those.
There were wo disappointments. The first was we have been working in a new domain in which none of our team members has experience and there were fewer Google search results that caused complications throughout the initial time. Additionally, it is impossible to exactly quantify the risk from different angles. So many challenges happened in the beginning.
Luckily, we learned step by step, made changes to the plan, and the procedure became more reliable.
Through the project mentioned earlier, I learned a lot, really understood what customers want, and we should also look into the company’s testing rules, think about whether the rules are right for a specific project, and if there are any other rules that can help our team work better. In addition, we have to think about the risks, make sure everyone on the project knows what to do, and write clear documents that explain all the technical stuff so that everyone can understand when they need to.
Monitoring and control
Once you have finished planning, it is important to put the Monitor and Control method into action. This method assists us in keeping tabs on the test work products and resources, ensuring that they are in line with the plan.
In theory, essential steps include:
- Defining targets and measuring progress
- Guides the testing to fulfill the mission, strategies, and goals.
- Collecting data about the testing activities, test results, and defects found
- Comparing actual progress against the plan and implementing corrective actions
- Revisiting the test planning activities
- Appropriate reactions to the control data
- The most important step is to identify goals for each stage and how they will be measured. In my experience with many projects, it is necessary to understand and coordinate with the customer’s plan when defining the objective for each stage to prevent the circumstance where the team sets and accomplishes the target, but the customer has goals and criteria. That make completing the aim is not totally meaningful.
Another thing to keep in mind is to take appropriate reaction when actual activity and plan targets do not match as well. If the measurement and comparison are applied, but the reality does not match the plan, a quick modification is required. If simply monitoring is done and no action is taken when there is a negative difference, undesirable outcomes can occur.
Besides the purpose provide progress information for our team, the monitoring result in my project also involves communicating the status of the testing process to stakeholders, such as project managers, developers, and customers and help them identify areas for improvement or make right decision for next phrase of software implement process.
Conclusion
In summary, while managing the testing project, activity planning, monitoring, and control tasks are important in which I actively engage, learn, and gain valuable experience. Their final objective is to ensure that the testing process is efficient and adaptable to the project’s requirements and circumstances.
I hope this post has given you some insight into the planning, monitoring, and control of the testing process. If you have any suggestions, please inform me and we may discuss together.
Reference:
