Skip to content

3. Doc process

Surbhi-MSFT edited this page Jan 13, 2021 · 6 revisions

Sprint planning illustration

Sprint Planning

A sprint is a specific and recurring interval during which designated work is completed. At the Teams sprint meeting, based upon the level of completion, you should have the previous sprint's tasks resolved, completed, or moved to the current sprint iteration.

The Teams Platform sprint planning meeting is held every other Monday (bi-weekly) at 4:00pm PST.

Update the Current Sprint

  1. Add Requirements with R4 dates within the current sprint to the current sprint iteration.

  2. Set the Finish date to one (1) working day prior to the R4 date.

  3. Set the State to Active.

  4. If you do not have clear direction and/or the necessary information to complete the documentation, toggle the Blocked status to Yes and reach out the PM owner for more information.

  5. Assign Requirement task to the appropriate doc team member.

  6. Ensure that PR titles and/or branch name for the Teams or Graph repo include the Azure Boards work item number.

  7. Monitor and update work item State changes.

    • Active: documentation is in-process.
    • Resolved: documentation is complete and awaiting publication.
    • Closed: documentation has been published and you have updated the Docs tab on the feature to Published.

Working with Pull Requests.