Quality Assurance (also referred to as QA) is the testing phase of the WalkMe implementation. It is an opportunity to catch and resolve any errors before WalkMe content goes live to your users. This can mean you personally testing your own WalkMe content, as well as involving other users or groups for a more formal Quality Assurance process.
Quality Assurance
There are many stages as you work through preparing your WalkMe implementation for go-live.
As a builder, you will be doing your own quality assurance as you build and will likely also perform a formal round of QA with other stakeholders. Working with your Project Lead, you will help organize, collect, and implement feedback.
Considerations
There are a few key considerations to think about here. It's most helpful to contemplate these items at the beginning of a project so your team can plan effectively. Nobody likes surprises that delay a project!
| Current Company QA Processes |
|---|
Does your company already have an established QA process in place for all tech projects, adding site guidance, or adding new features? Though WalkMe may be a new tool for your company, there may be related business flow procedures WalkMe must adhere to. If your company has an established Quality Assurance department, compliance team, or marketing department, consider if it is required for them to be involved with your project. |
| Whom to Involve |
|---|
Quality Assurance will likely require bringing in other business stakeholders to review content. This could involve folks from the teams mentioned earlier, subject matter experts, your manager, managers of other teams that will benefit from your WalkMe content, or your Project Lead to name a few. Whoever they are, make sure you know about how long they will need to complete a QA cycle. It is essential to identify who will give final approval to move forward with publishing WalkMe content to the production environment. Understand what they will need to provide that approval, and incorporate it into the process. |
| How to Document |
|---|
Documenting feedback from your QA testers is crucial - you will not remember every detail from a conversation. This will also depend on how the QA cycle is being run. Here are a few ideas:
|
| Timeline |
|---|
Once you have an understanding of the required QA process and who should be involved, you can establish your project timeline. You don't want to get into a position where you have built content against a deadline for go-live but did not budget time for QA! This will delay your project. You can start by understanding how long you need to create content, how long is needed for QA, and then set a goal date for go-live. If there is already an established go-live date associated with a specific milestone, work backward from that date to decide when is appropriate to start building the WalkMe solutions. |