Comments on: Step 4: Sprint Planning (Tasks)

By: Anonymous

Anonymous — Fri, 10 Sep 2010 14:15:00 +0000

With more rigid contraints, maybe KANBAN would be appropriate.

By: Anonymous

Anonymous — Thu, 20 Aug 2009 14:05:42 +0000

I have a few questions:
Can Agile be used for projects with Fixed scope, Fixed timeline, and a fixed budget?
Can you ever do Agile without a product backlog? E.g. i have a feature list and that is it, i dont know the number of story points etc but i am already 3 sprints into the project which we suggested would be 13 weeks (sprints) No sprint 0 nor stabilizing sprint.

By: Fahd

Fahd — Tue, 26 Feb 2008 13:30:00 +0000

hi,

"Add up all the task estimates for the selected Product Backlog.

If they are significantly over the team’s Sprint Budget, reduce the number of Product Backlog items selected for the Sprint."

I have a bit of confusion; Is the "Product Backlog ITEM" a potentially shippable product or is the "SPRINT Backlog" made up of a number of "Product Backlog Items" a potentially shippable product?

If it's the Sprint Backlog, then what if removing some items from the sprint makes it not potentially shippable anymore? do we increase the sprint duration or something else?

thanks & regards,
Fahd.

By: Kelly Waters

Kelly Waters — Wed, 09 Jan 2008 12:20:00 +0000

Hi Mikkel

You missed a key word from my post - I said make sure the product backlog *item* is 100% complete.

So, as you rightly say, I just mean the selected backlog items and not the whole backlog for sure...

Regards
Kelly.

By: Anonymous

Anonymous — Wed, 09 Jan 2008 11:57:00 +0000

Hi,

Under "Breaking Requirements into Tasks" you write:

"Include all tasks necessary to make the Product Backlog item 100% complete – i.e. potentially shippable – within the Sprint."

Do you really mean that the list of tasks, i.e. the sprint backlog, should include all tasks to make the PRODUCT BACKLOG 100% complete, i.e potetially shippable? Or do you maybe mean the "SELECTED PRODUCT BACKLOG", i.e the sprint log?

If you really mean it, then I read it as after every sprint the whole product must be 100% complete. Can you explain that, please?

I undestand that there is some kind of a delivery after each sprint, but I take it that only the implemented features are delivered; not the whole product with non-implemented features stubbed out. Or am I wrong?

Cheers
Mikkel

By: Artem Marchenko

Artem Marchenko — Fri, 12 Oct 2007 06:00:00 +0000

I prefer estimating sprint tasks in *ideal* engineering hours. It explicitly leaves work like e-mail checking or going to unnecessary meetings out of the estimation – simplifies the estimations and in the end of the sprint might show how much time actually goes to these “extra” tasks.