Thank you Mike. This is great information. Especially for pointing out Tip#6 - How anchoring impacts the estimation. As in so many subtle ways people pass on statements without realizing its impact of estimators decision!!
@@MountainGoatSoftware I need to read a book on planning and good user stories. You have 2 books on the subject and I'm not sure which one to go for. The "user stories applied" one already had a section on planning and estimation so I'm not sure how that's different from the other book. Any help would be greatly appreciated.
@@9gager87 The information on estimating and planning is much more complete in my Agile Estimating and Planning book. But both books are incomplete compared to the articles or video courses on my site.
@@9gager87 Because the books are 19 and 20 years old. I've learned new things since then and have learned better ways of explaining some things since then.
I would be grateful if you could help me answer 2 questions that have been tormenting me lately) Is it possible not to conduct a Daily Scrum on the day of Sprint Planning? Is this a violation of the Scrum rules? Is it good practice to conduct a Retrospective and Sprint Planning on the same day? For example, on Friday at 10 am, Retro starts, and then at 2 pm, Planning begins.
Answering your questions, 1-I would say that is a team decision. I already had teams that didn't do dailies on the same day of sprint planning and others that liked to keep the dailies. Usually, I see no point in doing the daily meeting when you have sprint planning on the same day (there are exceptions). 2 - I see no problem. Again, it is another team decision. The important is that both take place :)
Hi Andrey, BidGene gave you some perfect answers. I agree completely. I rarely do a daily scrum on the day of sprint planning. And when possible I like batching meetings so we'll do a review + retro + planning all in a row. That's hard when teams are highly distributed, though, just because of timezones.
![Agile Estimating | What Makes a Plan Agile? [Plus Story Points & Planning Poker]](http://i.ytimg.com/vi/37zfyncCpkA/mqdefault.jpg)
Thank you Mike. This is great information. Especially for pointing out Tip#6 - How anchoring impacts the estimation. As in so many subtle ways people pass on statements without realizing its impact of estimators decision!!
Thank you
Great info. Thanks a lot!
You're welcome!
@@MountainGoatSoftware I need to read a book on planning and good user stories. You have 2 books on the subject and I'm not sure which one to go for. The "user stories applied" one already had a section on planning and estimation so I'm not sure how that's different from the other book. Any help would be greatly appreciated.
@@9gager87 The information on estimating and planning is much more complete in my Agile Estimating and Planning book. But both books are incomplete compared to the articles or video courses on my site.
@@MountainGoatSoftware I believe you, but can you please clarify why?
@@9gager87 Because the books are 19 and 20 years old. I've learned new things since then and have learned better ways of explaining some things since then.
I would be grateful if you could help me answer 2 questions that have been tormenting me lately)
Is it possible not to conduct a Daily Scrum on the day of Sprint Planning? Is this a violation of the Scrum rules?
Is it good practice to conduct a Retrospective and Sprint Planning on the same day? For example, on Friday at 10 am, Retro starts, and then at 2 pm, Planning begins.
Answering your questions, 1-I would say that is a team decision. I already had teams that didn't do dailies on the same day of sprint planning and others that liked to keep the dailies. Usually, I see no point in doing the daily meeting when you have sprint planning on the same day (there are exceptions). 2 - I see no problem. Again, it is another team decision. The important is that both take place :)
Hi Andrey, BidGene gave you some perfect answers. I agree completely. I rarely do a daily scrum on the day of sprint planning. And when possible I like batching meetings so we'll do a review + retro + planning all in a row. That's hard when teams are highly distributed, though, just because of timezones.
@@BidGene Great advice! Thanks.
I would suggest an answer for both questions and it is: as long as it is useful for the team (be pragmatic)