There are various approaches to control the quality of your team’s work. Some approaches are better structured than others. But how do you know the quality of your team's work? Today, we are going to share with you a simple – but highly effective – approach that we advise our clients to use when they want to evaluate their team effectiveness.
We’ll guide your through the simple steps of creating and using a Mobile Product Audit Canvas, or MPAC [em`pak]. This term was invented by Yalantis, initially to describe our own in-house quality control. But an MPAC can also help product owners maintain control over their projects.
What is an MPAC?
An MPAC is a structured document that describes the quality of each important part of a mobile app project. The components of a mobile project which are the most significant to the project’s overall quality are chosen by the product owner and the technology team.
We will now address how to create an MPAC, how to use an MPAC, and will consider the benefits of using an MPAC.
How to Create an MPAC
To create an MPAC you first need to create a list of components that your project consists of. Then you must select those whose quality you care about most. In our example, these selected components will be: the App Icon, App Store Screenshots, App Name, Onboarding Screens, Push Notifications, Code, User Experience Design, and User Interface Design.
Now create a spreadsheet, placing selected components along the top row and names of you and your team members down the left-hand column. Your spreadsheet should now look something like this:
You’ve now created your very own MPAC! Next we’ll discuss how to use it.
How to Work with an MPAC
After you’ve created your first empty MPAC, ask your team members to fill in values of A, B or C into each cell in the row with their name. (Also, do this yourself.) A means Excellent, B means Good, and C means Poor. Excellent, Good, and Poor all refer to quality.
After the first iteration of work with your team, you might have an MPAC like this:
A = Excellent, B = Good, C = Poor
This chart is useful for you and your team because it shows your team how satisfied you are, as the product owner, with various parts of the project. And you get to see what your team thinks about each aspect of the project.
As you can see, the product owner and team members can have different marks for the same items. In our example, we can see that the Product Owner thinks that the app’s name is excellent, but the Designer thinks the app name still needs some work.
At this point, the Product Owner asks the team what they can do to get each item marked with an “A.” Team members give feedback, the product owner listens and responds, and together they come to an agreement and create a roadmap for improvements.
What you want to get in the end is an MPAC that looks something like this:
A = Excellent, B = Good, C = Poor
Our advice is to create your own MPAC for each iteration of your project. Then fill in the MPAC, together with your team, and review the history of changes and track progress. This will give you an opportunity to evaluate quality assurance and other aspects of work in your team.
The Benefits of Using an MPAC
An MPAC is a simple and efficient method for you and your team to jointly take control of the quality of your project.
There are four key benefits to using an MPAC:
- Agreements between a Product Owner and Team as to development priorities (i.e. what to improve first).
- Control of quality over time, and tracking of improvements.
- Collaboration among all members of the team.
- The creation of a quality improvement roadmap.
Our design and development team recommends that product owners experiment and create their own MPACs. Make sure to share an MPAC with your team in order to set quality expectations right from the start.
If you have any questions, don’t hesitate to contact us.