16 May 2017 by Sophia Sykes
The Importance of Stakeholder Engagement with Developers and Testers
While the role of a developer or tester is traditionally one of solitude, there are many advantages to stakeholder engagement, with software development projects benefiting from a varied set of opinions and support. While the phrase 'too many cooks spoil the broth' has been ingrained within the world of development, is it time we revised this approach?
First, it is worth defining what a stakeholder is. In essence, a stakeholder is an individual that possesses an interest in the business, whether it be an investor, director or anyone that is impacted by the business' actions, objectives and policies. Boasting such an importance, their involvement in software development and testing should always be welcomed. However, an agile, methodical testing approach should also been considered.
Choosing the right stakeholders
Utilising stakeholders in such projects can be an advantage if you choose the correct ones. For example, you should always ask who has legitimate reasons to comment on what, steering away from a 'too many cooks' scenario. For example, if you want to test user experience, it could be worth roping in the help of an investor that does not live and breathe the industry, gaining an outside perfective on aspects such and functionality and performance.
Origination – Communication – Resolution
If you are a developer or a business struggling with the stakeholder relationship, then we at CPS Group urge you to take inspiration from the Origination – Communication – Resolution formula; a setup that will give way to a more streamlined, beneficial collaboration.
Origination – This part of the puzzle could come from anyone; an investor, a remote tester or a consumer chosen at random. Whether they are highlighting a glitch, asking a question about usability or simply don't understand the tech, it is essential that the query is dealt with.
Communication – Now that this origination is made, it then becomes necessary for all the interested parties to communicate, exploring the issue with the whole team of developers, testers and stakeholders.
Resolution – Through brainstorming and further analysis, a resolution can be arrived at, giving way to a perfect piece of code and a clean, usable product.
To conclude, stakeholder management and communication plays a pivotal role in a successful software development and testing project. However, stakeholders need to be asked the right questions and introduced during phases of the testing process that they can add value to. Stakeholders will no longer be viewed as a distraction if you follow the formula of Origination – Communication – Resolution.
11 May 2017 by Sophia Sykes
04 April 2017 by Sophia Sykes
03 April 2017 by Sophia Sykes
This website uses 'cookies' to give you the best, most relevant experience. Using this website means you're happy with this. You can find out more about the cookies used by clicking this link.