Quality Intelligence: Transparency & Visibility
•
0 likes•206 views
One of the most important aspects of Quality Intelligence is transparency and visibility. Intelligence is worthless if it does not affect the decision-making process in some way. If the intelligence is not available to the people involved in the decision-making process, then it will have no effect.
Report
Share
![Quality Intelligence: Transparency & Visibility
One of the most important aspects of Quality Intelligence [1][2] is transparency and visibility.
Intelligence is worthless if it does not affect the decision-making process in some way. If the
intelligence is not available to the people involved in the decision-making process, then it will
have no effect.
During feature development, especially if everyone is working remotely, one tool that can be
used to collaborate is Miro [3], which I will use as an example in this article.
So if you are a QI specialist embedded in, or collaborating with, a team that is going to develop
a feature in a mobile game, they might have a Miro board that looks something like this:
This is where the team plans and collaborates around the different areas of the game feature,
and where they have their backlog and communicates their progress to the rest of the team and
their stakeholders. Maybe they also report found bugs in JIRA [4], or through post-its on the
Miro board.
This is where it becomes important to find a space for Quality Intelligence. How do you make it
available and valuable to the rest of the team? Of course this differs widely depending on
context, so I will just give one example here.](https://image.slidesharecdn.com/qualityintelligencetransparencyvisibility2-210126084954/75/Quality-Intelligence-Transparency-Visibility-1-2048.jpg)
More Related Content
Similar to Quality Intelligence: Transparency & Visibility
Similar to Quality Intelligence: Transparency & Visibility (20)
More from Johan Hoberg
More from Johan Hoberg (20)
Recently uploaded
Recently uploaded (20)
Quality Intelligence: Transparency & Visibility
- 1. Quality Intelligence: Transparency & Visibility One of the most important aspects of Quality Intelligence [1][2] is transparency and visibility. Intelligence is worthless if it does not affect the decision-making process in some way. If the intelligence is not available to the people involved in the decision-making process, then it will have no effect. During feature development, especially if everyone is working remotely, one tool that can be used to collaborate is Miro [3], which I will use as an example in this article. So if you are a QI specialist embedded in, or collaborating with, a team that is going to develop a feature in a mobile game, they might have a Miro board that looks something like this: This is where the team plans and collaborates around the different areas of the game feature, and where they have their backlog and communicates their progress to the rest of the team and their stakeholders. Maybe they also report found bugs in JIRA [4], or through post-its on the Miro board. This is where it becomes important to find a space for Quality Intelligence. How do you make it available and valuable to the rest of the team? Of course this differs widely depending on context, so I will just give one example here.
- 2. In this simple and easy to implement example, the first section covers both test scope and coverage of exploratory testing, which is then followed by found bugs in each test area, prioritized based on available information. This is followed by links to relevant dashboards which contain informformation that influenced the risk assessments, scope setting and test execution. The last section contains feedback from when the feature was sent to a play test session, either with internal or external users. The Quality Intelligence section is added to the team’s Miro board by the Quality Intelligence specialist who then maintains and updates it during feature development.
- 3. Obviously you can do this in a million different ways, depending on the team you are working with, the feature they are developing, existing processes, which tools are being used, and so on, but the core of it remains the same: “Find a way to make Quality Intelligence visible and available to whomever is part of the decision-making process.” If you are doing the work, gathering the information, and processing it into Quality Intelligence, and then not making it available to your stakeholders in a non-convoluted and easy-to-digest way, then you are not adding as much value as you could. Letting bugs drown in JIRA, or in a test management system that no one else is looking at, could have the same effect as not finding them in the first place. A QI specialist’s job is not just to test, though testing could be a big part of the job, but to enable that the right decisions are taken, based on good and available Quality Intelligence.
- 4. References [1] QI, not QA https://www.gamasutra.com/blogs/JohanHoberg/20161102/284652/QI_not_QA.php [2] What is QI? https://www.slideshare.net/JohanHoberg/what-is-qi [3] Miro https://miro.com/ [4] JIRA https://www.atlassian.com/software/jira