About planning in Scrum ?

Thinh,

Your inquiry leads to many more questions that in my mind need to be answered/addressed:

1) How many team(s) will be working on the project?

2) How long are the sprints?

3) How long have the team(s) been working together? Does each team have an established velocity based on previous sprints?

4) What does the DoD look like for the team(s)? Is there work needed outside of the sprint for production release?

5) Has the project scope been identified? Has this scope been broken down into items that the team(s) feel can be completed according to the DoD within a sprint?

6) Have the team(s) estimated the project items?

7) Have the project items been prioritized in order (must have's, nice-to-have's)?

This is only the beginning of the information and preparation you would need in order to begin forecasting a potential delivery date.

I look forward to your response.

> When can I make plan and estimate general of
> entire project ? Becuase I must to give
> information about deadline and cost of project
> to customer as soon as possible,

Where is the desire to use Scrum coming from on this project? Who wants to use it and why?

I want to forecast how long project will be, so that I can answer deadline to customer

Thanks Timothy !!!

It may be useful to you to have a look at burndown (or burn up) charts. If you have an idea of the number of story points in the release and the average velocity of the team you can then project an end date. That being said if you're looking at being more accurate on end etc then you may wind up having to descope some story points (or with luck bring extra in!)

Either way I'd suggest a look at burndowns and sites such as https://www.mountaingoatsoftware.com/agile/scrum/release-burndown

Thinh,

Following Ian's point, what is your motivation for using Scrum to forecast the project?

Also, can you provide answers to the questions that I posed to you?