The Roadmap to Successful Testing and Delivery in the Enterprise
A group of people gathered in an event space discussing a topic.

The Roadmap to Successful Testing and Delivery in the Enterprise

How do you deliver a product on time and to the desired quality standards? How is that possible with a large system built by multiple teams and with multiple stakeholders? Read on to discover a roadmap to successful testing and delivery in the enterprise.?


Bring disciplines together?

When different stakeholders on a project are not able to communicate effectively, the quality of the product will suffer. Create opportunities to bring together testers, developers, and business users from different teams to work together on testing the product.?

Use structured exploratory testing techniques

Structured exploratory testing techniques, such as session-based test management, allow testers to have a more open-ended and investigative approach to testing, rather than simply following a set of test cases. This can lead to a collective and deeper understanding of the product. Collective knowledge will increase the likelihood of identifying important risks – the things that threaten the value of the product.

Visualise test results

Software testing is not just about finding bugs. It is also about communicating the results of testing to the different stakeholders on a project. Use visual tools to communicate the results of testing efforts. What are the main concerns of each stakeholder group? How might you tailor the visuals accordingly? And then consider using a visual coverage model to communicate across multiple teams and stakeholders.

Be flexible

Enterprise development has many working parts. Requirements and needs change. These changes can negatively impact delivery teams if those teams stick with the same testing approach. Adapt the testing process to the changing needs of the project. This may sound disruptive yet using cycles of work can help. For example, you could stick with an approach for a two-week cycle. Focus on specific areas of the product each cycle, and adjust your testing approach based on the results of the previous cycle.


Want to dig deeper into this topic? Aaron Hodder tells a good story about how he helped a test team of business users test a large, complex product in his TestBash talk: To Boldly Go: Taking The Enterprise On A Journey To Structured Exploratory Testing???

This talk is available to everyone for a limited time only until Monday 26th June.?


And don’t forget, you can hear many more talks and join plenty of practical workshops at TestBash UK 2023. You don’t want to miss out on this incredible opportunity to learn and connect with fellow testing professionals in person. Grab a ticket. ???


?? Discover what's happening in the testing community every week. Subscribe to the weekly newsletter and receive testing-related news in your inbox every Monday. New testing events, helpful business posts, learning opportunities, ways to connect with fellow testers and more! ??

KRISHNAN N NARAYANAN

Sales Associate at American Airlines

1 年

Thank you for posting

回复
Kim Nepata

Agile Project Lead & Senior Business Analyst

1 年

Love this article but I’m wondering where the decision makers sit within this roadmap to successful testing & delivery of the product. There need to be people with a holistic perspective of the entire delivery which may or may not be the testing resource/s / developers. Any defects that display during UAT need to follow the formula of repeatability & clear documentation on replication & expected business outcome. Rationale being, the business needs to prioritise business impact/value/cost to support (or not) these changes. The real issue is communication and understanding the problem as a whole which includes risk/dependencies/deliverables/business value. This is what Agile supports, this internal communication across multiple teams. We find pipeline blockage when communication becomes isolated to a single member or team.

回复

要查看或添加评论,请登录

社区洞察

其他会员也浏览了