Engagement/Agile Council
Jump to navigation
Jump to search
Objective
During the Whistler Coincidental Work Week, Jascha announced the formation of the Agile Council.
The Agile Council is the cross-team committee empowered to define and roll-out agile systems across Mozilla Marketing.
Deliverables
2015 Q3
Item | Summary | Example |
---|---|---|
Glossary of Terms | shared language | what do we call it? scrum-ban / moz-bon? how does it work next to other agile implementations? |
Tools Recommendation | business process & tech | standups three days a week? trello? physical boards? |
Team Size POV | smaller > bigger | what is the max size of a team? what is the minimum size? |
Overall Work System POV | ‘scrum of scrums’ | how many durable teams? how are they organized (scrum of scrums, etc.)? workforce plan. training? |
2015 Q4
Item | Summary | Example |
---|---|---|
Test & Retrospective | near-term success | pick a project in a theme and run a test of the proposed system |
Roll Out Plan | long-term success | set and launch the system |
RACI
Who | Group | Role |
---|---|---|
Jascha | Executive | Product Owner |
Cory | WebProd | Scrum Master |
Full RACI with all team members and roles
Schedule
References
Meeting Notes
https://docs.google.com/document/d/1DUiS1YfM32V9tlSnG4qAPnM_gdhxpRVsFRafgi_saLI/edit
Questions?
Send any questions to agile@mozilla.com.