Archive for the ‘process’ Category
Thursday, August 14th, 2008
We've arrived at the part of Scrum where real work gets done. The Sprint! The Sprint is where people get down to business and apply their funky stuff. They architect the software, code it, design it, test it. Repeat that. They wave their arms in joy and frustration. They turn ...
Posted in process | 1 Comment »
Friday, August 8th, 2008
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, ...
Posted in process | 2 Comments »
Monday, August 4th, 2008
This post covers the benefits of the first segment of the Sprint Planning meeting. It relies on the previous post (a quite boring elaboration on the details of the Sprint Backlog).
The Sprint Planning meeting is time-boxed to 8 hours, and consists of two segments that are 4 hours each. The ...
Posted in process | 2 Comments »
Friday, August 1st, 2008
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 ...
Posted in process | 1 Comment »
Thursday, July 31st, 2008
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 ...
Posted in process | No Comments »
Wednesday, July 30th, 2008
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 ...
Posted in process | 3 Comments »
Wednesday, July 16th, 2008
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) ...
Posted in process | 5 Comments »
Wednesday, July 9th, 2008
Scrum does not allow for any detailed planning for longer than 30 days at a time. So how can you make a list of functionality that will be implemented within 3 months? Short answer, you can't. If you do, it's not Scrum, nor is it agile.
Old style waterfall planning let's ...
Posted in process | 2 Comments »
Thursday, July 3rd, 2008
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 ...
Posted in process | 6 Comments »
