Development Team Standards

Product Backlog Usage

Operations Information R&D Process from Feature to Task.

Development Team Backlog

All development team backlogs should exist in the Azure DevOps 'osieng' organization in the 'engineering' project. The Operations Guild manages the creation and administration of product and team backlogs. Teams can initiate Azure DevOps backlog creation and maintenance requests to the Operations Guild via the ADO Administration Channel in the OpsGuild Support Team in Microsoft Teams.

Fields are Properly Defined

Clear Title User Story in Description Acceptance Criteria Parented to a Feature

Additional Notes

• All Product and Program-Related Development Work Items should be parented to a feature​.
• Team-related Work Items, such as new developer onboarding and support collaboration requests, may be parented at the team's discretion.
• Work with TPM, SPM, EPM to find an appropriate Epic and Feature for your work items.

State Usage

Prioritized Backlog

• Backlog reflects priorities as stated in Program Backlog
• Team works on highest priority items​
• Backlog priority is updated at least every sprint

Estimates

• Backlog items are estimated…
• After being approved​
• Before they are committed to a sprint

Tasks with Hours (Work Remaining)​

• Items committed to a sprint have tasks defined​
• Tasks are estimated in hours
• Tasks are updated daily
• State​
• Hours
• Decomposition

Committed Items Are Done at the End of the Sprint​

• Consistently finish all items in a sprint​
• Other teams depend on your progress