Archive for the ‘process’ Category
Wednesday, August 27th, 2008
I have already asserted that without feedback, there can be little or no improvement. And we need to provide and receive feedback to improve ourselves and our team members.
This post is part of our Scrum-series, and we have arrived at the fifth and last activity in the Scrum-process (according to ...
Posted in process | No Comments »
Thursday, August 21st, 2008
It's demo-time! (Play theme from Knight Rider here, and visualize The Hoff). This post is part of our Scrum-series.
The Team has been hard at work for a month, and time has come to show off what have been accomplished.
So How Did We Ever Get This Far?
Revisiting our stripped down definition ...
Posted in process | 1 Comment »
Monday, August 18th, 2008
Here he goes again, you might be thinking, pounding his chest and asserting that creating great software is like creating any other form of art.But I'm telling you, the process of creating great software is an intellectual and creative effort, which in many ways are very similar to the process ...
Posted in process | 2 Comments »
Friday, August 15th, 2008
This is the second post about The Sprint in Scrum. Read the first one here.
The Daily Scrum Meeting is the continuous inspection and adaptation mechanism of Scrum. The Team inspects its own efforts, and adapts to new information. To put the Daily Scrum into the larger picture, have a look ...
Posted in process | 2 Comments »
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 »
