Bug Reporting
Making Bug Reporting procedures standardised can help maintain consistency across org. A badly written bug report can cause a lot of ping-pong between team members, namely between the testers and the developers, which can cause delays in the bug fixes.
(It's free)
How to use this template for your next
Bug Reporting
Release Notes
Date: XX-MM-YYYY
Release Version:
🥁 New Stuff
⚡️ Improvements
🐞 Bug Fixes
Product & Engineering
Release Notes
Template By
HC
Drive Feature Awareness. Increase Customer Adoption.
QA
What
Requirements:
Designs: linked here
Please check here for the expected experience, and match to what you see in your testing
Feature Breakdown (overview for customer-facing teams)
How
Where to test: [link to your product]
Testing instructions (include video recording):
Step 1:
Step 2:
Step 3:
Step 4:
What to look out for when testing:
Deliverable 1:
Deliverable 2:
Deliverable 3:
Where to report issues: [link to external spreadsheet or other bug reporting system]
Timing
QA start: MM/DD
QA end: MM/DD
Release date: MM/DD
Product & Engineering
QA
Template By
HC
For successful & efficient QA process
Product Launch Checklist
Project Summary
Keep everyone on the same page by adding a quick summary about this launch here.
Launch Deadline:
Pre-release Checklist
Engineering
Work with QA by giving a demo and helping them update pages for the feature.
Set the release type for relevant platforms.
Database scheme
Design
Performance
Community & marketing
Demo of new feature
Written help guides
Update the What’s New page
Are we updating socials?
Growth & analytics
How do we track metrics?
What valuable questions can we ask about this feature?
Product & Engineering
Product Launch Checklist
Template By
HC
Ensure nothing slips through cracks for your next Lauch!
Sprint Retrospective
Sprint no. :
🥁 What went right
😢 What went wrong
🧠 What did we learn?
✅ Action Items
Product & Engineering
Sprint Retrospective
Template By
HC
Look back on your past achievements & pitfalls.
User Interview
Introduction
Plan how the interviewer is going to handle the introduction part and get to know the user’s background.
Questions
Compile your primary list of questions to be asked at the interview.
What if Scenarios
Discuss the users’ predictions for ideal scenarios or future predictions.
Conclusion
Wrap things up and discuss anything that was not yet covered.
Product & Engineering
User Interview
Template By
HC
Cheatsheet for User Research Interview & Follow-ups
Product Requirement Documentation
Description: What is it?
Problem: What problem is this solving?
Why: How do we know this is a real problem and worth solving?
Success: How do we know if we’ve solved this problem?
Audience: Who are we building for?
What: Roughly, what does this look like in the product?
How: What is the experiment plan?
When: When does it ship and what are the milestones?
Product & Engineering
Product Requirement Documentation
Template By
HC
Only thing you can't run away from.
Technical Documentation
Product Overview 👀
Provide a brief summary covering what your product/feature is
Product Objectives 🎯
What does your product do? How should it be used?
Product Features 🧩
Describe the different features or elements of your product and how to use them.
Feature/Element 1
Description
Add your code snippets
Element 2
Description
Element 3
Description
Product & Engineering
Technical Documentation
Template By
HC
Give everyone in-depth details of how the product works!