Monthly Archives: November 2017

The Retrospective

Note: This post is one of a continuing series re Scrum Intro. The preceding post is here. Basics We usually think of the Retrospective as the last meeting of the Sprint. But what is the difference between the Sprint Review and the Retrospective? The Sprint Review is about the product. The Retrospective is about the process, […]

The Sprint Review

Note: This is one in a continuing series of posts re Scrum Intro. The preceding post is here. The Sprint Review (meeting) happens almost at the end of the Sprint. Basics We gather the team (the whole team, including of course the SM and the PO) and meet with the Business Stakeholders (BSHs). We want […]

The Daily Scrum

Note: This is one in a continuing series of posts re Scrum Intro. The preceding post is here. Scrum has a daily team meeting that we call the Daily Scrum or the Daily Standup. The maximum timebox is 15 minutes. If the team is seven people, the minimum timebox is seven minutes. The whole team […]

The Sprint Planning Meeting

Note: This is one in a continuing series re Scrum Intro.  The preceding related post is here. Basics Before the Sprint Planning Meeting (SPM), there must exist a Product Backlog with small Product Backlog Items (PBIs) at the top of the list. The PBIs must be estimated. Specifically, we recommend User Stories and estimating using […]

The Sprint and the Meetings

Note: This is one in a continuing series of posts re Scrum Intro.  The preceding post is here. The next subject we turn to is the Sprint and the meetings in the Sprint. First, the Sprint is an important time box (one of many timeboxes) where the team must build working product and then get feedback […]

The Whole Scrum Team

Note: This is one in a continuing series of posts re Scrum Intro. The preceding post is here. The team needs to be considered on its own. The team is the whole Scrum Team. Normally that would be about seven people, including the PO and the SM, and normally the team will be full-time, a real […]

Scrum Roles — Team Role

Note: This is one in a continuing series of posts re Scrum Intro.  The preceding post is here. The next role is commonly called the team role (I am not happy with the name). There is only one team worth talking about: the whole Scrum Team, which includes all three roles. The team wins or loses […]

Scrum Roles — The ScrumMaster

The ScrumMaster (SM) is a hard role to explain, I think. It is easy to misunderstand, and, in fact, it is commonly misunderstood. The SM must first help the team learn how to self-organize. Self-organizing is a thing we humans all do, and we all can do more of it. Most of us can also […]

About the New “Path to CSP”

Below is key information about the “Path to CSP.” Two main take-aways: You can move to a new level now by taking the Advanced CSM course — as soon as I offer the course. To become a CSP you need to take two courses and have 2 years of experience (starting January 1, 2o18). The […]

Using a “Definition of Agile” in a Large Corporation

Fairly often a large corporation will mandate Agile. One thing to consider is Open Space Agility — more on that before and later. For now, I want to suggest a “Definition of Agile.” This is vaguely similar to the Definition of Done concept. The idea here is that often teams will… make up what Agile […]