8/30/2010 by Michael Vizdos
As a current Certified Scrum Trainer (CST), I'd like to share some information about what I have learned so far from working with people coming through the new process.
8/26/2010 by Prashant Pund
Is your team suffering from Scrum Mis-Adoption Syndrome? If your team is disinterested, unsure whether it is even doing Scrum, and failing to deliver, the team might have transitioned to Scrum without attending to some of the necessary details. Read on to discover how one CSM approaches agile adoptions in his organization.
7/27/2010 by Maria Matarelli
The story of how using Scrum helped one team complete a project outside the world of software with a minimal budget, almost no direction, and even less time.
7/9/2010 by Unknown anonymous
The name ScrumMaster can be misleading. Many have likened ScrumMasters to Jedi Masters, Kung-Fu masters, or other guru-type roles. This has probably happened because the word master itself seems to imply a deep knowledge and understanding. However...
7/2/2010 by Badri Srinivasan
Scrum teams are tasked with finding the most optimal way to accomplish the work. To do this, they make decisions ranging from how best to meet goals to who should work on which tasks. Reaching group consensus can be difficult. Some opinions are more dominant than others; some voices more hesitant to speak out. Even in agreement, true consensus might not exist. Find out how to reach an agreement that everyone on the team can believe in.
6/15/2010 by Henri Stegehuis
How one CSP discovered that when explaining product backlog items to new teams, it's best to avoid delving into details about the PBI itself and instead focus on the the workflow of a PBI and the interaction with the Scrum framework.
5/27/2010 by Diana Larsen
The Agile 2010 conference, long planned for Nashville, TN, suddenly had to be relocated due to severe flooding. Read the story of how this Scrum Alliance-sponsored conference used agile values and principles to respond quickly to change.
5/25/2010 by Pat Guariglia
Sprint burndowns are an essential Scrum artifact. Teams use them throughout the sprint to track work remaining. But one CSP has found that, for his projects, a release burndown has become just as essential, especially when it comes to communicating with upper management.
5/10/2010 by Marco Mulder
Are your team’s retrospectives really worth the effort? Do the problems you identify actually get solved? If not, your team might need some help learning how to use retrospectives to continuously improve. This article illustrates how Scrum teams can continuously improve by using a combination of their definition of done, working agreements, and the product backlog.
4/27/2010 by Sunil Upadhye
Successful ScrumMasters and agile coaches share many positive qualities—listed here from A&A to Z&Z.
Attitude & Affirmations
Dress up your attitude and you can achieve 100 percent success. Affirmation is a self talk – w...