QA/Testdays/Strategy/Kick Off Post: Difference between revisions

From MozillaWiki
< QA‎ | Testdays‎ | Strategy
Jump to navigation Jump to search
mNo edit summary
No edit summary
Line 1: Line 1:
; Testdays Are Broken
; Testdays Are Broken
I do not think it'll surprise anyone who has participated in the QA community in recent months when I say, "Testdays are broken!". They have lost their energy and are not the once robust and purposeful events they once were for a variety of reasons. We have lost sight of the value these events present to Mozilla and our volunteers. We need to refocus these events on mentorship and establishing relationships, to teach new skills, to connect people, and to enable people to contribute in meaningful ways. We need to build a vibrant and unique program that is more welcoming, more lively and more purposeful than they are right now and have been in the past.  
I do not think it'll surprise anyone who has participated in the QA community in recent months when I say, "Testdays are broken!". They no longer seem to be the energetic, robust, purposeful events they were in the past. This happened for a variety of reasons, not least of which was that we lost sight of the value these events provided to Mozilla and our volunteers. We need to refocus these events, to build a more vibrant and purposeful program that serves to mentor, to establish relationships, and to enable people to contribute in meaningful ways.


A couple of us have been brainstorming, internally, over the last few weeks and we have come up with an extensive list of identifiers describing exactly what within the current event program is working and what is not, and some ideas of new things to try. However, we need your help and support to make these events a meaningful opportunity to redefine the program.
; Reversing the Tide
It is not enough for a couple people within Mozilla to try to reform this program; we tried this numerous times and failed. The only way we solve this problem is by working together.  We need your help and support to make this program a success. Internally, a couple of us have been brainstorming and we've come up with an extensive list describing what we believe to be working and what isn't, and some ideas of new things to try.  


Our goal for this quarter is to get help from you, our community, to determine our vision of what testday events can and should be, and to solve some of the lowest hanging fruit to achieve that vision. We see our first priority as creating a platform where conversations can take place, so we can start sharing our experiences and so we can start working together to solve our problems.
Our goal for this quarter is to get help from you, our community, to determine our vision of what this program can and should be, to define a strategy to realize that vision, and to resolve some of the lowest hanging fruit. To this end, our first priority is to create a platform for conversation, to share experiences, and to start working together to solve our problems.


To emphasize, we do not intend to eliminate the concept and ultimate purpose testdays as they provide provide us a unique opportunity to galvanize the community around a particular testing activity. The community remains, and has always been, one of the biggest contributors to Mozilla’s success. Without the support of the community we would not be able to push Firefox and the Web forward at the speed and level of quality the world has come to expect. We are hoping to extend and fix it to become more meaningful while still retaining it’s original intent at the same time.
; Never Stop
The community remains, and has always been, one of the biggest contributors to Mozilla’s success. We could not push Firefox and the Web forward at the speed and level of quality the world has come to expect without your support and contributions. Testdays have always been intended as a "gateway" to contribution and this will not change. We are hoping to fix the program without disrupting current activity and opportunity. '''If you presently participate in or organize testdays that you continue to do so, and encourage your friends to become involved.'''


; Calls to Action
; Calls to Action
To kick things off, we have a few calls to action we need you all to take:
1. [https://docs.google.com/forms/d/1TspohcF2FZQOCQvcoafm1mVit6kgRRxfKsHSzs5gs8A/viewform Fill out our meeting survey] so we can determine a day/time for a new weekly meeting. This meeting will be a place for '''everyone''' with a vested interest to voice their concerns and to get their questions answered.
1. [https://docs.google.com/forms/d/1TspohcF2FZQOCQvcoafm1mVit6kgRRxfKsHSzs5gs8A/viewform Fill out our meeting survey] so we can determine a day/time for a new weekly meeting. This meeting will be a place for '''everyone''' with a vested interest to voice their concerns and to get their questions answered.


Line 22: Line 26:
4. If you plan to participate in the upcoming [https://wiki.mozilla.org/QA/Work_Week_July_2014 QA work week] we'll be having a session to review the feedback so far and to kick off some discussions. Think about what you want to contribute to our vision and bring them to this session. ''We'll try our best to make this session remotely accessible for those of you unable to attend in person''.
4. If you plan to participate in the upcoming [https://wiki.mozilla.org/QA/Work_Week_July_2014 QA work week] we'll be having a session to review the feedback so far and to kick off some discussions. Think about what you want to contribute to our vision and bring them to this session. ''We'll try our best to make this session remotely accessible for those of you unable to attend in person''.


; Never Stop
; Conclusion
I want to emphasize that even though we are making considerable effort here to change what these events are about, you should not stop contributing if you already are. We want to make iterative improvements to these events without any interruption to the great work that's already happening. Please continue to organize and participate in events. These contributions truly matter.
...

Revision as of 18:58, 9 July 2014

Testdays Are Broken

I do not think it'll surprise anyone who has participated in the QA community in recent months when I say, "Testdays are broken!". They no longer seem to be the energetic, robust, purposeful events they were in the past. This happened for a variety of reasons, not least of which was that we lost sight of the value these events provided to Mozilla and our volunteers. We need to refocus these events, to build a more vibrant and purposeful program that serves to mentor, to establish relationships, and to enable people to contribute in meaningful ways.

Reversing the Tide

It is not enough for a couple people within Mozilla to try to reform this program; we tried this numerous times and failed. The only way we solve this problem is by working together. We need your help and support to make this program a success. Internally, a couple of us have been brainstorming and we've come up with an extensive list describing what we believe to be working and what isn't, and some ideas of new things to try.

Our goal for this quarter is to get help from you, our community, to determine our vision of what this program can and should be, to define a strategy to realize that vision, and to resolve some of the lowest hanging fruit. To this end, our first priority is to create a platform for conversation, to share experiences, and to start working together to solve our problems.

Never Stop

The community remains, and has always been, one of the biggest contributors to Mozilla’s success. We could not push Firefox and the Web forward at the speed and level of quality the world has come to expect without your support and contributions. Testdays have always been intended as a "gateway" to contribution and this will not change. We are hoping to fix the program without disrupting current activity and opportunity. If you presently participate in or organize testdays that you continue to do so, and encourage your friends to become involved.

Calls to Action

To kick things off, we have a few calls to action we need you all to take:

1. Fill out our meeting survey so we can determine a day/time for a new weekly meeting. This meeting will be a place for everyone with a vested interest to voice their concerns and to get their questions answered.

2. Review our wiki to get a sense of what we've brainstormed so far. We will continually review and update this strategy as feedback is collected and as things evolve.

3. Update our etherpad with your feedback, questions, and suggestions. We will be reviewing this periodically to integrate into the strategy. Here are example some questions to help get you thinking:

  • Why don't you attend testdays?
  • Why don't you host your own testdays?
  • What do you like about testdays?
  • What don't you like about testdays?
  • What would you like to see in testdays?

4. If you plan to participate in the upcoming QA work week we'll be having a session to review the feedback so far and to kick off some discussions. Think about what you want to contribute to our vision and bring them to this session. We'll try our best to make this session remotely accessible for those of you unable to attend in person.

Conclusion

...

Retrieved from "https://wiki.mozilla.org/index.php?title=QA/Testdays/Strategy/Kick_Off_Post&oldid=995841"