Raghul Murugesan, Head of QA at ClickUp, will explore how ClickUp has transformed its QA role from reactive to proactive in a fast-paced startup environment. 
This session highlights strategies for integrating QA into product development, lessons learned, and best practices for scaling quality efforts while maintaining speed and customer satisfaction.
Not registered yet? Don’t miss out—secure your free tickets and register now.
Already registered? Share your questions in the thread below 
Hi there,
If you couldn’t catch the session live, don’t worry! You can watch the recording here:
Here are some of the Q&As from this session:
Can you share insights into how ClickUp’s QA team measures success and quality improvements from sprint to sprint?
Raghul Murugesan: ClickUp’s QA team likely measures success through metrics like defect density, test coverage, and cycle time, and tracks quality improvements by comparing these metrics across sprints.
What strategies are the most effective in integrating QA seamlessly into the product development process?
Raghul Murugesan: Effective strategies include early involvement of QA in planning, continuous integration and testing, automated testing, and maintaining clear communication between QA and development teams.
Here are some unanswered questions that were asked in the session:
What are the challenges we have to face during the establishment of any new company?
What are the problems that we had after implementing shift?
What challenges did ClickUp face during the transition to its current QA practices, and how were they overcome?
How does ClickUp rate with JIRA or other PM software?
How does the QA process adapt with each sprint to ensure quality improvements?
What were some of the biggest QA challenges ClickUp faced during its growth, and how did the team address them?
Can we apply shift-left for API testing?
What are the drawbacks that you had after implementing shift left, if you had any?
What KPIs did you focus on while ramping the test team, and how did that help with tuning the performance of the test team?
How should we grow as QA, based on best practices from ClickUp?
With a shrinking QA pool as described in the slide, are the remaining roles going to feature greater value in their work (vs. repetitive smaller tasks)?
How can startups grow very effectively?
Which best practices should be used to speed up testing while maintaining a good level of quality?
What are the unique QA challenges faced by startups compared to established companies?
Most PM software favors the dev parts; how is ClickUp different from others on this matter?
How is ClickUp better than Jira?
