Skip to content

Planning

Patrick Nikoletich edited this page Feb 6, 2019 · 18 revisions

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 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.

Issue types & Labels

For information on how labels are applied refer to the Issue labels page.

Bug

Reported bugs are placed into the bug inbox until triaged and assigned to someone on the App Center team. We'll discuss details of the issue with you directly to see how we can resolve your issue in a future iteration plan.

For general issues using App Center please contact us through the built-in chat option within the portal

Change and Feature Requests

We don't always create the best experience right away, but we are committed to always improving. Create a change or feature request for us to discuss changes we should make to improve your daily life in App Center.

Proposal

We'll share ideas or thoughts on potential future work we'll be tackling to get your input on the feature's importance and the general design.

Plan Item

Bugs, change requests, features and proposals are plan items added to iteration plans every month. We'll openly discuss design details and share early designs of the features we are working on.

Known Issue

This designates that the item is an issue that we are aware of and likely have no control over. This can occur when a service we have a dependancy on goes down.

How items are selected

Our roadmap provides a general guide for where our core priorities stand. A significant portion of our team are 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.

Clone this wiki locally