Confirmed users
2,959
edits
QA/Work Week July 2014: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 2: | Line 2: | ||
* '''When:''' July 28 - July 31 | * '''When:''' July 28 - July 31 | ||
* '''Where:''' Mountain View headquarters; 331 E Evelyn St. Mountain View CA | * '''Where:''' Mountain View headquarters; 331 E Evelyn St. Mountain View CA | ||
= Overview = | |||
This is going to be a fun and productive week. There are still places to sign up for sessions in the schedule, if folks would like to do so. I am really looking forward to seeing everyone. This agenda has been designed to favor discussions and interactivity over presentations and listening quietly. Prepare to be involved. Start thinking now about what you want to be different in QA at Mozilla. | |||
Monday – Wednesday morning will be a crucial time to design the future of QA at Mozilla. We will be offline during this period. This means no computers, no cell phones. If you need to attend a meeting or be away, then you'll need to step out and return later. I've already sent mail and told many managers and directors of projects we work on that we will be away, they are expecting that you will not be available—that said, it is good to remind them of this yourselves. | |||
= Goal = | = Goal = | ||
The goal of this work week is to break down old, outmoded models of Quality engineering. And build ourselves a vision and a strategy to achieve our overall QA goal of becoming more relevant and impactful. We will do this by: | The goal of this work week is to break down old, outmoded models of Quality engineering. And build ourselves a vision and a strategy to achieve our overall QA goal of becoming more relevant and impactful. We will do this by: | ||
* Becoming more technical to engage with the web platform and our products on a deeper level | * Becoming more technical to engage with the web platform and our products on a deeper level | ||
* Making decisions based on data and metrics and publishing those metrics for wider use | * Making decisions based on data and metrics and publishing those metrics for wider use | ||
| Line 17: | Line 23: | ||
When booking flights plan to arrive on Sunday at the latest. We start promptly on Monday at 9AM. You may use Friday as a travel day for your return flight if you so choose. | When booking flights plan to arrive on Sunday at the latest. We start promptly on Monday at 9AM. You may use Friday as a travel day for your return flight if you so choose. | ||
== Logistics == | |||
There is a shuttle that runs from hotel strata to the mountain view campus. I don't know much more about it than that – I've seen the vehicle. Please inquire about that at the hotel and make arrangements. | |||
For Bocce Ball on Wednesday night, I'm looking for volunteers from the local folks to drive people. We should have enough cars to be able to take everyone over to the site and back to either the hotel or the caltrain station. If you would like to volunteer yourself as a driver, please email ctalbert. | |||
== Hotel Info == | == Hotel Info == | ||
| Line 96: | Line 107: | ||
* On Wednesday July 30, we will go have some fun at Campo di Bocce in Los Gatos. We'll play Bocce and eat some great food, and have a good time. | * On Wednesday July 30, we will go have some fun at Campo di Bocce in Los Gatos. We'll play Bocce and eat some great food, and have a good time. | ||
* On nights when there is nothing planned, we'll make reservations for small groups (around 10-ish) of us to go dine somewhere in downtown mountain view. It will be a good way to connect with people in a smaller setting. | * On nights when there is nothing planned, we'll make reservations for small groups (around 10-ish) of us to go dine somewhere in downtown mountain view. It will be a good way to connect with people in a smaller setting. | ||
== Agenda == | |||
=== Monday === | |||
9AM Breakfast | |||
10AM Exploding Inertia – Overview of the week and the process | |||
11AM [Strategic Group] Define Most Important Change Your Team needs to Make | |||
12PM LUNCH | |||
1PM [Cross Groups] Introductions and a Challenge | |||
2PM [Cross Groups] Identify what we can do better, and what tradeoffs we need to make 3:30 BREAK | |||
4PM: Two Discussions (split your cross functional group so you have representation at both): | |||
• Discussion 1: What does Technical Acumen look like? Where does automation fit in? (ctalbert) | |||
• Discussion 2: What kinds of Data/Metrics do we need? (mschifer) Evening Dine About | |||
== Other Suggested Events == | == Other Suggested Events == | ||