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.
If you’re using waterfall or some other non-agile methods, then transitioning to Agile principles and the Scrum process is a significant paradigm shift. So it’s extremely likely that without professional Agile transformation guidance, you will encounter one or more of some common major Agile implementation mistakes.
The Scrum Guide The Scrum Guide is the official guide to Scrum and is required reading for everyone working with Scrum and Agile. It is only about 19 pages of content, that contains the definition of Scrum including Scrum’s roles, events, artifacts, and the rules that bind them together. Ken …
Complex software requires the efforts of more than just 1 Scrum team. So in this article I discuss: How to scale Scrum to large programs and portfolio. How to avoid common mistakes in Scrum. Originally Published by Scrum Alliance: I am proud that the Scrum Alliance editorial team reviewed, approved …
Everything is moving faster and faster. And agility is needed now more than ever. In this article I’ll dive in to: Why Scrum is required these days ? Studies that demonstrate project success rates over a decade. Why is Scrum a huge competitive advantage ? Originally Published by Scrum Alliance: …
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.
Tips on how to conduct a Sprint Review for internal use by Scrum teams. As opposed to a review that might be organized for an external audience such as stakeholders.
Here are some guidelines for having the most effective Sprint Review activities.
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.
Documents some techniques you can use to estimating in Story Points using Affinity Estimating.
Quick tips on writing good Epics, Features, Stories and any other work item types and using the INVEST technique to break down work in to smaller pieces.
Some quick tips on learning and using Estimation Poker to estimating. Also known as Planning Poker.