![]() ![]() When questions are asked, it would be good to make sure that we not only answer them on a public list, but also document the answers to make them easy to find for others. There is some information that already exists - an explanation of MDN’s agile process, and a glossary of agile terminology. How you can contact each team and get updates on their work.How to find more information on what you can do for each team at the current time and in the future.What the different teams are and what they are responsible for.How the process works in general, and an explanation of key terms like durable team, “functional team”, “cross-functional”, etc.InformationĪn explainer doc to explain the agile process would be useful, including: We need to work out better tools/workflows for volunteer contributions. Some of the “agile tools” can appear closed off and difficult to access for those outside your organization (at least, in the ways we’ve been using them).Slack is hard in terms of giving people the right permissions. ![]() We need to review the tools we are using, and make sure that they are open for volunteers to get information and updates. These details are fairly brief, but they act as good starting points for further investigation. Let’s look at the solutions that were discussed. The challenge we face is how to make the agile process more transparent, so that volunteers can understand what is happening and how it happens more open so that volunteers can contribute in meaningful ways and more welcoming so that volunteers feel they are part of a team and are appreciated and recognized for their efforts. There is very little information provided for volunteers who want to participate in a project managed in an agile fashion.Their work is deprioritized, they feel ignored, they find it harder to participate. The agile process in general does not lend itself well to volunteer discovery or contribution.The tools used to track work are not open, so volunteers cannot access them.This is written from the perspective of the Mozilla Developer Network (MDN) team, but we are sure that other teams have experienced similar negative trends. Since moving to an agile, “durable team” model, the amount of interaction we have had with our volunteer community has decreased. This post explores the issues we’ve found, and shares some potential solutions that we could work towards implementing. We are Mozilla, and transparency, openness, and participation are part of our core values. While the agile workflow encourages accountability for full-time team members, it leaves very little space for part-time or occasional participation by volunteers. However, one aspect of our work that has suffered in this new paradigm is openness and inclusion of our volunteer community in marketing activities. Read the Agile Marketing Manifesto for more background.) (For those familiar with agile software development, agile marketing applies similar principles and workflows to marketing. Participants in that discussion included Janet Swisher, Chris Mills, Noah Y, Alex Gibson, Jeremie Patonnier, Elio Qoshi, Sebastian Zartner, Eric Shepherd, Julien G, Xie Wensheng, and others.įor most of 2016, the Mozilla marketing organization has been moving towards working agile - much of our work now happens within “sprints” lasting around 2.5 weeks, resulting in better prioritization and flexibility, among other things. This post is based on a discussion at the Mozilla All-Hands event in December 2016. Facilitating openness and including volunteers in agile sprints
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |