Working open: Difference between revisions
Jump to navigation
Jump to search
(Created page with "=How to Work Open at Mozilla: a FAQ= ===Definition=== * What does "working in the open" mean at Mozilla? * Why does Mozilla do it? * How has it changed? ===Successes=== *...") |
|||
| Line 1: | Line 1: | ||
=How to Work Open at Mozilla | =FAQ: How to Work Open at Mozilla= | ||
<em>Frequently Asked Questions and helpful resources for when, why and how to work open at Mozilla</em>. Got a question? Please add it below! | |||
===Definition=== | ===Definition=== | ||
Revision as of 19:47, 1 October 2013
FAQ: How to Work Open at Mozilla
Frequently Asked Questions and helpful resources for when, why and how to work open at Mozilla. Got a question? Please add it below!
Definition
- What does "working in the open" mean at Mozilla?
- Why does Mozilla do it?
- How has it changed?
Successes
- What are examples of how working open has made Mozilla successful?
Challenges
- What's hard about working open?
- What if I don't believe in the benefits?
- When there's a conflict between openness and business requirements, how should we navigate that?
- What are some examples of failures / areas we've done badly?
Strategies and Tactics
- How do you work open? What are some specific strategies, tactics and best practices?
Different approaches
- How do different parts of Mozilla take up working open differently? (e.g., design vs. communications vs. QA) What can we learn from each other?
Resources=
- What resources do we have available for guidance and help?