Standardize Team Process
Forward informal process emails or attach notes. Get a structured process document back. State the roles involved if you know them.
Draft an email
Subject
FWD: RE: Project Nimbus - QA Handover from Emily
On Mon, Feb 26, 2024 at 10:37 AM Liam Chen <liam.chen@innovatex.com> wrote:
Hey team,
Just forwarding Emily's notes on the new QA process for Project Nimbus. She's leaving next week, so we need to get this locked down asap.
From: Emily Vance <emily.vance@innovatex.com>
Date: Sat, Feb 24, 2024 at 9:15 AM
Subject: Project Nimbus - QA Handover
To: Liam Chen <liam.chen@innovatex.com>
Hi Liam,
As discussed, here are the key steps for QA on Nimbus before release. The dev team (specifically David and Sarah) will push builds to the 'QA_Staging' environment. I usually pull the latest build from there twice weekly, or whenever David pings me about a major update. Once I have the build, I run through the 'Nimbus_TestPlan_v2.1' document located in the Shared Drive (Innovatex/Projects/Nimbus/Docs). Any bugs get logged directly into Jira under the 'Nimbus QA' project, assigned to the relevant dev (David for front-end, Sarah for back-end). Critical bugs get an 'Urgent' tag and I'll ping them directly on Slack. Once all criticals are resolved, I do a final smoke test. Then I update the 'Release Readiness' sheet in Excel (also in Shared Drive) and notify the Release Manager (that's you!) and Michael in Marketing.
Let me know if anything's unclear.
Best,
Emily
Hey team,
Just forwarding Emily's notes on the new QA process for Project Nimbus. She's leaving next week, so we need to get this locked down asap.
From: Emily Vance <emily.vance@innovatex.com>
Date: Sat, Feb 24, 2024 at 9:15 AM
Subject: Project Nimbus - QA Handover
To: Liam Chen <liam.chen@innovatex.com>
Hi Liam,
As discussed, here are the key steps for QA on Nimbus before release. The dev team (specifically David and Sarah) will push builds to the 'QA_Staging' environment. I usually pull the latest build from there twice weekly, or whenever David pings me about a major update. Once I have the build, I run through the 'Nimbus_TestPlan_v2.1' document located in the Shared Drive (Innovatex/Projects/Nimbus/Docs). Any bugs get logged directly into Jira under the 'Nimbus QA' project, assigned to the relevant dev (David for front-end, Sarah for back-end). Critical bugs get an 'Urgent' tag and I'll ping them directly on Slack. Once all criticals are resolved, I do a final smoke test. Then I update the 'Release Readiness' sheet in Excel (also in Shared Drive) and notify the Release Manager (that's you!) and Michael in Marketing.
Let me know if anything's unclear.
Best,
Emily
.svg)
What is via.email?
AI agents that each lives at an email address. Just send an email to get work done. No apps. No downloads.
.svg)
How to use?
Send or forward emails to agents and get results replied. Try it without registrations. Join to get free credits.
Is it safe?
Absolutely, your emails will be encrypted, deleted after processing, and never be used to train AI models.
More power?
Upgrade to get more credits, add email attachments, create custom agents, and access advanced features.
Make email work for you.
Your first agent awaits - just one email away.
Try for free
join@via.email
Type name in subject and send.
