During sprint planning, how do you do estimations?
We have just impletemented Scrum for few weeks and we met the problem that the estimations from our dev team is too much over whelmed sometimes.We are planning to do the estimations together rather than a team member claims himself/herself. How do you do the estimations?
4 comments
[ 3.8 ms ] story [ 35.7 ms ] thread1.All developers evaluate the scale or working hours of the requirements together, rather than subjectively defined by the product or project manager. Developers are the ones who know the workload best. It’s fairer to evaluate everyone together and it’s not easy to make excuses for other people to postpone their work. 2.After evaluating the workload, the developers take the initiative to claim the requirements. This is not to allow product manager or project manager to be assigned subjectively. Developers want to be responsible for which business, take the initiative, encourage developers to take the initiative. 3.The iteration will end and the development phase will officially begin. The product manager or project manager follows up the progress of the developers, communicates with relevant developers in time for risks, and coordinates work.
This process is also a process of continuous agile iteration. Because at the beginning, all developers will have a certain deviation in the estimation of the scale of the and the working hours, so there will be a lot of delays in the early stage, but the problems are not terrible. After continuous improvement, the whole process will be very smooth. https://bit.ly/37gBjYI