Sprint Planning, second segment — Plan 30 days

This post covers the second segment of Sprint Planning, read about the first segment here. As with the first segment, the second segment is also time-boxed to 4 hours. During the first segment the team committed to items in the Product Backlog. The purpose of the second segment of Sprint Planning, is to create a Continue reading

The Sprint Backlog — Some Boring Facts

This post is a bit boring (but quite necessary if you’re following our Scrum series). It covers mere practical details about the Sprint Backlog. Force yourself to through it and then reward yourself with a banana. It consists of just one short definition and 5 simple facts. You’ll surely manage. Have a look at the Continue reading

Scrum — Gets The Most From Your Wet Sponges

This post is a part of our series on rationale for choosing Scrum as our process framework. You will never achieve perfection. (You will never achieve perfection. You will never achieve perfection!) Thus you should avoid it. Understanding that your strive for total perfection is actually hurting your overall goals of closing in on it, Continue reading

The Product Backlog – 6 benefits

This post covers rationale and practical details about the product backlog. Have a look at the post on scrum basics to put the Product Backlog into the greater picture. The product backlog is a list of functional and non-functional requirements sorted by importance. It is continuously updated and maintained to represent current customer needs. The Continue reading

Scrum basics – everything but the gobbledygook

I have recently written a few short posts about Scrum without having the decency to set the scene and introduce you to what Scrum really is. That’s why I’ve now made an effort to summarize the mechanisms of Scrum. I’m making this a short, stripped down introduction for two purposes; a) To show how small Continue reading

5 Reasons Why We Are Implementing Scrum

We’re implementing Scrum as a process framework for the development of our projects. We’re iteratively implementing it, sprint for sprint. Therefore, this is not a post on how we do Scrum, rather it is a post on why we’re implementing it. Reason #null: It’s agile It’s so fundamental that I’m not going to justify this Continue reading