What to share with client for Client Testing?

Purpose and Scope

The purpose of this SOP is to establish a consistent process for sharing and receiving feedback during the testing phase of development. This ensures clarity, efficiency, and actionable results while maintaining alignment with project timelines and deliverables.

This SOP applies to all team members responsible for client communication and project testing within LowCode Agency.

Definitions

Testing Feedback: Information provided by the client or stakeholders to evaluate and refine app functionalities and user experiences.
Test Users: Specific users designated for testing who can provide relevant insights based on their interactions with the app.
Feedback Deadline: A defined time frame within which testing and feedback should be completed to maintain the project schedule.

Purpose of Milestones

Testing feedback during milestones is critical for:

Validating app features and workflows.
Aligning app functionality with client and user expectations.
Addressing and resolving issues efficiently before the next development phase.

Procedure

Provide Test Users
- Share a clear list of specific users or roles that can test the app.
  - Example: "Please test using the following user accounts: [User A email@gmail.com, User B email+1@gmail.com, User C email+2@gmail.com]. Each account has a unique role to review."
  - Make sure client has access to the app with each of the corresponding roles.
- Highlight relevant scenarios for testing, if applicable.
Guide Feedback Submission
- Clearly outline how feedback should be provided.
  - Clients can either add their feedback under the Dev Board in the "QA" column by adding new tasks and assigning both the PM and BA OR through this form.
  - You may share the template below:
    
    How to provide feedback/bug reports?
    1. Create tasks in Plutio as shown in this guide.
    2. Submit tickets through this form: https://lowcode.plutio.com/p/form/x8XLma4zHBjGauLoJ
- Include steps or templates to ensure consistency and usability of the feedback.
  - Example: "Please use this format for feedback: [Issue encountered, Steps to reproduce, Expected behavior, Screenshot if applicable]."
Set a Feedback Deadline
- Define a clear and reasonable timeline for testing and feedback, we usually give one week to test the entire app thoroughly to meet our tight deadlines.
- Example: "Please complete testing and submit feedback by [specific date], end of day."

Responsibilities

Business Analyst/PM
- Ensure test users, feedback guidelines, and deadlines are communicated to the client.
- Make sure that the QA provided by the client is understandable for the dev, and it is not user error
- Follow up with clients to ensure compliance with the feedback timeline.
Development Team
- Address and resolve issues identified in the feedback within agreed-upon timelines.
Client
- Complete testing and submit actionable feedback within the specified deadline.

Exceptions and Special Scenarios

If the client cannot provide feedback by the deadline due to unforeseen circumstances, communicate promptly to establish a revised timeline.
In cases where no specific test users are available, provide a general testing scenario for the client to review.
For complex feedback requiring more detailed instructions, schedule a walkthrough session with the client.