Confirmed users
1,193
edits
MDN/Development/ProcessNext: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 94: | Line 94: | ||
=== Priority meeting === | === Priority meeting === | ||
The product manager and project manager meet every two weeks to discuss priorities. Over time, other MDN stakeholders will be invited to this meeting to inform priority decisions. | |||
== Planning and Retrospective | == Planning and Retrospective meeting == | ||
The development team, product manager, project manager and interested users meet every two weeks to discuss process improvements and review the state of development. | The development team, product manager, project manager and interested users meet every two weeks to discuss process improvements and review the state of development. | ||
| Line 102: | Line 102: | ||
== Working with contributors == | == Working with contributors == | ||
The project manager lists himself as a mentor in bugs that seem like good candidates for contributors. The team shares a list of these bugs with contributors. | |||
== Tracking Progress == | == Tracking Progress == | ||
| Line 117: | Line 116: | ||
=== Notifications === | === Notifications === | ||
The team publishes several RSS feeds that stakeholders can subscribe to for notifications about progress. | The team publishes several RSS feeds that stakeholders can subscribe to for notifications about progress. The state of things might change by the time a notification is seen, so subscribers are encouraged to always consult the corresponding Kanban card for the most up-to-date information. | ||
* [http://pipes.yahoo.com/pipes/pipe.run?_id=a3d378990547aff38f71f3874fb99b73&_render=rss All team progress] | * [http://pipes.yahoo.com/pipes/pipe.run?_id=a3d378990547aff38f71f3874fb99b73&_render=rss All team progress] | ||