Subscribe to this blog
Interested in a Lean-Agile-Scrum course or Workshop?
Recent Posts
Categories
- agile
- agile business
- Agile principles
- Better Agile
- business value
- BV Engineering
- Change Management
- courses
- Events
- freedom
- Getting started
- impediments
- Innovation
- Jeff Sutherland
- Kanban
- Key problems
- knowledge creation
- leadership
- lean
- Lean Software Development
- learning
- Listings
- Little's Law
- Little's Second Law
- managing agile
- Misc
- Nokia Test
- Paying
- People issues
- Recommended reading
- Release Planning
- Resources
- scaling
- Scrum
- Scrum Intro
- Scrum meetings
- Scrum roles
- ScrumButt
- ScrumButt Test
- Self-organization
- Talks
- Teams
- Uncategorized
- video
- WIP
- Yogi Berra
Category Archives: Scrum Intro
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 […]
Scrum Roles – Product Owner
Note: This is one in a continuing series of posts re Scrum Intro. The preceding post is here. The Scrum Guide does not ‘require’ you to have a fully dedicated team. I think if you read it carefully, you will see that they are urging you to have a fully dedicated team. Certainly I strongly […]
Why Scrum?
Note: This is the second in a continuing series of posts re Scrum Intro. The preceding post is here. Why Scrum? How did it get here? How do we understand it? How do you explain it to your colleagues? Why was Scrum invented? The way I understand it, Jeff Sutherland became a software development group manager […]
What is Scrum?
Note: This is the first in a continuing series of posts re Scrum Intro. I am starting a series of posts to explain quickly what Scrum is. It turns out that Scrum is very simple, and yet difficult to explain concisely. The main purpose of this series is to give my course attendees a bit […]