Back to Forum

New to scrum questions

Last post 08:47 am June 29, 2015 by Idris Khalfallah
2 replies
Bindu Kiran
05:07 pm June 22, 2015

I would like to know when and how many times is the planning poker done.is it done during agile release planning ?
Is it done again during sprinit planning meeting for that sprint?

Is it during the sprint planning meeting the user stroies are broken to tasks..?

When user stories are broken down to task what is the role of scrum master in this?

Does the tools automatically create burndown charts?

Any good websites that explanins everything in details?


Thanks.


Nitin Khanna
02:44 pm June 24, 2015

Scrum doesn't specify how to estimate product backlog items.

Should you be using Planning Poker, it can be used at any time when the Dev Team need to estimate an item. It can be during planning, at refinement or any other junction.

Sprint Planning has 2 parts. Part 1 is "what" the Dev Team is planning to accomplish and Part 2 is "how" -- i.e. in your scenario the Dev Team may break the product backlog item (such as a User Story) down further. The Scrum Master (SM) is facilitating as requested or needed. If the SM is part of the Dev Team, then he or she is also breaking these down further.

Some tools create burndown charts, and some don't. Some even create them erroneously! Note that burndowns are not a formal artifact in Scrum, anymore. I have worked with a Team that didn't use this.

Other websites --
www.scrumtrainingseries.com
(Free. animated, but a little outdated with the current Scrum Guide)

I would strongly encourage you to read thru the Scrum Guide.

Idris Khalfallah
08:47 am June 29, 2015

Hi,

Perhaps this will give you any answer to your initial question on Planning poker .
as see on
https://www.mountaingoatsoftware.com/agile/planning-poker

Most teams will hold a Planning Poker session shortly after an initial product backlog is written. This session (which may be spread over multiple days) is used to create initial estimates useful in scoping or sizing the project.

Because product backlog items (usually in the form of user stories) will continue to be added throughout the project, most teams will find it helpful to conduct subsequent agile estimating and planning sessions once per iteration. Usually this is done a few days before the end of the iteration and immediately following a daily standup, since the whole team is together at that time anyway.
Idris

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.