Contents

Goal: Go Beyond Books

My goal with these articles is to go far beyond what most books and guides can offer – to go into the deep level of detail that can only be learned through many years of real world experience.  And to share that experience with others, in the form of practical tools, techniques and tips.

Sprint Planning

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.

Estimating

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.

Retrospectives

How to plan, schedule and execute a Retrospective. This how to is based on good practices learned over years of experience conducting hundreds of Retrospectives with Scrum teams, functional teams, engineers, managers, directors and executives.
Contains the Retrospective template in wiki page and spreadsheet formats described in Retrospective How To. You can use this to share the results of a Retrospective in a wiki or other shared space.

Sprint Reviews

Scaling

How to scale Scrum to large programs and portfolio. How to avoid common mistakes in Scrum.

Books and Guides

The Scrum Guide is the official guide to Scrum and is required reading for everyone working with Scrum and Agile.
Describes the Scrum roles, responsibilities and commitment of anyone in those roles. Most of this content came from The Scrum Guide and I added some additional content based on lessons learned and good practices.

Training

Here is some of the training that I have developed and conducting over the years.

Lessons Learned and Tips

In this article I'll begin discussing some lessons learned through pain and triumph in the real world, and try to boil them down to some Do’s and Don’ts with some real world situations.
How to scale Scrum to large programs and portfolio. How to avoid common mistakes in Scrum.
Why Scrum is required these days ? Studies that demonstrate project success rates over a decade. Why is Scrum a huge competitive advantage ?

Agile Tools

Atlassian's Jira

I’ve been using Atlassian’s Jira since 2011.

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.

Microsoft's Azure DevOps (VSTS)

This Microsoft set of tools is now called Azure DevOps.  Previously it was known as Visual Studio Team Services or VSTS.

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.
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.
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.
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.
Need an Agile Expert ?

Looking for an expert in Agile Coaching, developing & leading Agile transformations, Agile tools, DevOps strategy and Scrum ?

Send me, Ken Adams, a message on LinkedIn and let’s talk.

Subscribe

Enter your email address to subscribe to this blog and receive notifications of new posts by email.