Scrum Dictionary
Is Your Scrum Team Really Cross-Functional and Self-Organized? Find Out Now.
According to the Rules of Scrum, Scrum Teams are cross-functional and self-organized. Having a firm grasp on what these two terms mean, and what they look like within the realities of Modern Scrum, is key to a successful Scrum Team.
Read MoreManaging Known Unknowns: The PlaceHolder Story
One of the most common issues for Scrum Teams is what to do about work they expect to have to do during a Sprint, but don’t actually know the details about yet.
Read MoreThe 4 Types of Technical Debt
The 4 Types of Technical Debt
Technically speaking (pun intended), we can define Technical Debt as deficiencies in the code, technical documentation, development environments, 3rd-party tools and development practices, which makes the code hard for the Team to change.
Done/Done/Done/Done in Scrum
In 2002, (give or take), I introduced the term “Done/Done/Done” into agility in order to describe what Done meant in an agile setting. It is now pretty established that Done is a HUGE concept in Scrum, but at the time we were just figuring it out.
Read MoreBuild It Up Scotty
We recommend using a BuildUp Chart to gain a more accurate snapshot of how the Team is really doing throughout the Sprint. The BuildUp Chart’s focus is on the Doneness Agreements that were made during Sprint Planning.
Read MoreThe Scrum Team vs. The Development Team
In Scrum, names matter. They add clarity and help define accountability. Which is why we designed our latest infographic to illustrate the difference in some important names. Scrum Team vs. Development Team.
Read MoreWhat’s in a Name: The Most Dangerous Scrum Terms Explained
Let’s face it, scrum can be dangerous. It’s a powerful tool, and if used incorrectly–the consequences can be detrimental.
Read MoreAgility In All Things
What does it mean to really be “agile”? How many ways can one be agile? Join us as we count a few of the ways!
Read MoreAtomic Scrum (“Five People in a Garage”)
Every once in a while I start thinking too hard and I ask myself: “What is Scrum, anyway?” Sometimes the answer is complicated, and sometimes it’s simple… depends on my mood, I guess…
The basic idea is pretty simple. Have some work to do, and a (small) Team to do it…
Read MoreWhat is a Team Swarm?
Scrum is about Teams producing Results, not people doing work. The best way that Teams can produce Quality Results is by working together, helping each other out, having conversations, and just plain ‘getting it done’. This pattern of work is called the Team Swarm, and I discuss it in this post. Ever since I started developing…
Read MoreScrum in Real Life
We practice Scrum at our workplace. We use it to complete complex projects. We appreciate its flexibility, its visibility and its inherent collaboration. We value our PO who prioritizes our journey down the road, our ScrumMaster who removes any bumps in the road, and of course our Team who develops an easy and efficient cadence…
Read MoreRoles Outside the Scrum Team
What are the common Roles Outside the Scrum Team? First, we will refresh our model by exploring roles inside the Scrum Team and then we will jump outside the Scrum Team. There are three common roles for people on the Scrum Team: Scrum Master, Product Owner and Team Member. This blog post will break down…
Read More