Why is Scrum so popular?
Of the many reasons given for choosing Scrum, organizations are predominantly attracted by:
- Speed to market
- Increased productivity
- Lowered cost
Note the relentless focus on time and money?
The Scrum Guide, while being a model of brevity, devotes an appreciable amount of space to the definition of “Done”. In my travels as a trainer or coach though, I often come across questions about the definition of done. So, in this article, I’m going to examine it in more depth. I’ll provide some extra detail as well as reasons why your definition of “done” is so important and why you should invest time in creating, and maintaining it.
Many Scrum Teams make use of a team’s velocity to help in forecasting. TFS provides just such a feature but beware – the results can be misleading for the unwary.
If you use Visual Studio Online or Team Foundation Service, and the Visual Studio IDE, it’s possible you’ll come across the TF31003 error. If you have more than one Microsoft account as well, you just increased your chances greatly. Here are a couple of possible solutions to the error.
The Scrum Guide has a lot to say about the Product Backlog, and rightly so. It’s pivotal to everything a Scrum Team does. But one thing the Scrum Guide doesn’t tell you, is how you create a Product Backlog. So, here’s one way you can do exactly that.
In March 2012, I sat the Professional Scrum Master I assessment provided by Scrum.org. I did not attend any formal training beforehand and relied only on my experience and exam preparation. In this article, I tell you how I prepared for, and passed, the Professional Scrum Master I assessment.