Estimates are a fundamental element of Scrum. Because they are the basis for planning and predicting when work will be completed. Like Sprints, if you’re not using Sprints and estimating, then you’re not using the Scrum framework.
Details on an example VSTS Dashboard the is used to capture, report and take action to correct data quality problems that will occur in a VSTS backlog.
Documentation for people using Aha <-> VSTS integration and good practices. This integration is done utilizing Aha’s own integration software.
Documents the configuration of the Aha <-> VSTS Integration done by system administrators.
How to setup and view dependencies between work items in VSTS. Focuses on Feature work items, but is also applicable to any work item type in VSTS.
Tips on how to keep VSTS work item states up to date.
Everything below the top level work item needs a parent for the backlog structure to work correctly. So as you create new work items, everyone should keep an eye on that. ScrumMasters should facilitate their teams backlog work and monitor their Backlogs for data quality problems like these.
Documents how to track blockers in VSTS with the configuration of Blocker color coding configured on Board team views.
Some info on the VSTS Work Item Visualization extension, providing some quick tips and links to learn more. This VSTS extension allows you to visualize relationships between work items from within the work item form.
Requirements of a Sprint Plan & tips to make it easier and more effective to do Sprint Planning.
Documents the VSTS Product Backlog Hierarchy used for sophisticated products and portfolios of products, and how you can use the levels of the hierarchy and the work item types.
Lists requirements for Scrum teams before starting a Sprint, and before a new Scrum team starts their first Sprint.