The most widely used format for the daily scrum, or daily stand-up, is having everyone answer three questions:
What did you do yesterday?
What will you do today?
What is blocking progress?
For a description of the rationale behind using these questions, see this article by Jeff Sutherland.
In addition to these questions, I like to add the following:
What is [...]
It’s not easy being a product owner. For a lot of you out there it’s a lonely job. It’s also a job that brings with it a lot of responsibility. You are responsible for the vision and the profitability of the product.
That’s not something to be taken lightly.
A recent discussion on the Scrum Development List [...]
My talk about agile planning at Øredev 2008 is now available here.
Chris and I have been helping a team introduce agile software development for a while now. When we are running a planning meeting, we have usually used planning poker for estimation. But we seem to be using planning poker less and less.
I like planning poker. It has a lot of advantages. In particular it helps [...]
If you’re doing any kind of agile software development, you’re probably having some form of daily stand-up. In my experience most of the daily stand-ups out there are, quite frankly, pretty uninspiring things. A lot of meetings are spent mechanically reporting status to a project manager or discussing details of interest to only a few.
Like [...]
Anchoring and adjustment is a psychological heuristic that influences the way people intuitively assess probabilities. According to this heuristic, people start with an implicitly suggested reference point (the “anchor”) and make adjustments to it to reach their estimate.
– Wikipedia
The team managing the project portfolio in a large enterprise need to come up with a rough [...]
This is how we collaborate to create the product backlog in my current project. Having a set of stories that will make up the backbone of the project, the product owner is given 1000 points to distribute between the stories. The most important story gets the highest number of points. The second most important story [...]
I haven’t been as active writing on this forum as I hoped I’d be. A large part of the reason for this is that I have prioritized other things than writing when I have time away from work. But another important part has been the problem to come up with things meaningful enough to write [...]
I find using points an excellent tool to estimate and track the progress of a project. There are advantages with using points, such as separating the estimation of size from the estimation of time, and that it comes quite naturally to estimate the relative size of one story to another. I find that the process [...]
Discusses the need for a clear cut exit criteria for a planned feature and how a test is one way to go.
In the project I am currently involved in, we release software once a month. We have currently released the first increment of work, and one of the activities we start after a release like [...]