Planning

Roadmap

The team has a 6-month high level Roadmap which defines high-level themes and features to be addressed in this timeframe.

Iterations

The work planned during an iteration is captured in the iteration plan (see Iteration Plans). The feature highlights of each iteration are highlighted in the release notes.

Planning

Before each month, we will prioritize features and changes to the service we plan to make in the next iteration. For features, change requests and bugs planned for an iteration, we will create new issues and label them with plan item and add a milestone for the specific month the iteration represents. Change requests, feature requests, and bugs that are assigned to a milestone encompass the planned work for the upcoming month.

How items are selected

Our roadmap provides a general guide for where our core priorities stand. A significant portion of our team will be focused on delivering roadmap items every iteration, but bugs and change requests will be selected to address issues impacting your everyday use of the service.

Weekly

Each week we will manage work items, crossing off completed features, triaging issues and publishing updates on our progress. Some changes and enhancements will then be either postponed to later iteration or moved back to the backlog.

Recap

At the end of each iteration, we will publish a recap of our progress and what was successfully shipped.