I work with a startup and we have an upcoming project which I have decided to execute using Scrum. I have two team members who are developers (they will work on Python/Django) and one UI/UX developer.One of the Python/Django developers will be working 60% of his time on this project as he is also working on another project for which he will be devoting 40% of his time. The UI/UX developer will not be collocated with the rest of the team as he belongs to another organization. I have identified the Product Owner for this product and I will play the role of Scrum Master. I understand that we first need to have a product vision created by the Product Owner and which will be expressed in the product backlog. We will try to create fine grained user stories in this backlog. We not yet decided the duration of the sprints, but, since we feel that this would be a comparatively small project, we would be having sprints which are of 2 weeks. We would be having sprint planning meetings of approximately two hours at the beginning of each sprint. We would also be having a daily standup (we will involve the UI/UX developer via conference call) of 15 minutes.We also plan to have a sprint review and then a sprint retrospective meeting at the end of a sprint.
I have read through the theory of Scrum and I am not sure of the way estimations are done. I understand that we need to create story points for each story. But, my concern is the following - how do I estimate the total hours for this project. I had read once that 1 story point = 4 hours of estimated work, Is that the right way of estimating a scrum project?
I am sure that there are many project managers in this group who are using scrum on a daily basis. Would appreciate if someone could suggest a way to estimate this project.
Looking forward for some constructive advice. If I have made any mistakes in my understanding of a scrum project, please feel free to correct.
i had a hugh debate with Allen. I fully disagree with him. The name is #NoEstimates but when you read what they do they are making estimations. It is funny.
Finally we agree on something Sergio, that we both don't agree with Allen's article ;-) Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
I don’t really see it that way. What I interpret is taking a more generalist is approach relying on the law of averages and not looking individually at the story level, rather at the sprint level. The projections look at the number of stories completed in a sprint. Because some stories take longer, some sprints will complete less, but on the flip side, some sprints will complete more.
Additionally, taking this #NoEstimate perspective, you create a dialogue and platform of questioning the ‘normal or default ‘ thinking, or as some refer to as the comfort zone.
This may be starting a whole new discussion:). Maybe a new thread? I wish we could split and move comments to easily create a new thread. I’ll add that to my list Sante:)
...
2 replies by Sante Delle-Vergini, PhD and Sergio Luis Conte
Apr 09, 2018 5:27 PM
Sante Delle-Vergini, PhD
...
Yes splitting off to another thread would be a good feature.
Apr 09, 2018 5:32 PM
Sergio Luis Conte
...
I used a similar approach time ago into non Agile environments. I sent an email to the creator saying that if he let me a comment the name must be changed. Why? Because some people are creating a "credo" from it and are saying that "estimation is wasted and must be eliminated". That is because the hard side of estimations is not the estimation itself is the attitude you must take along the whole process. Then those people find a way to not answer to people request about "how long it will take". That attemps against the concept of value. Organizations are creating products to take an opportunity and the opportunity has an opportunity window then it is impossible to not estimate. On the other side, a human being can not survive without making estimations then it is totally anti natural.
Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Apr 09, 2018 3:39 PM
Replying to Sergio Luis Conte
...
i had a hugh debate with Allen. I fully disagree with him. The name is #NoEstimates but when you read what they do they are making estimations. It is funny.
Would love to have seen/heard that. LinkedIn or live? Link? Saving Changes...
I don’t really see it that way. What I interpret is taking a more generalist is approach relying on the law of averages and not looking individually at the story level, rather at the sprint level. The projections look at the number of stories completed in a sprint. Because some stories take longer, some sprints will complete less, but on the flip side, some sprints will complete more.
Additionally, taking this #NoEstimate perspective, you create a dialogue and platform of questioning the ‘normal or default ‘ thinking, or as some refer to as the comfort zone.
This may be starting a whole new discussion:). Maybe a new thread? I wish we could split and move comments to easily create a new thread. I’ll add that to my list Sante:)
Yes splitting off to another thread would be a good feature. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Apr 09, 2018 5:01 PM
Replying to Drew Craig
...
I don’t really see it that way. What I interpret is taking a more generalist is approach relying on the law of averages and not looking individually at the story level, rather at the sprint level. The projections look at the number of stories completed in a sprint. Because some stories take longer, some sprints will complete less, but on the flip side, some sprints will complete more.
Additionally, taking this #NoEstimate perspective, you create a dialogue and platform of questioning the ‘normal or default ‘ thinking, or as some refer to as the comfort zone.
This may be starting a whole new discussion:). Maybe a new thread? I wish we could split and move comments to easily create a new thread. I’ll add that to my list Sante:)
I used a similar approach time ago into non Agile environments. I sent an email to the creator saying that if he let me a comment the name must be changed. Why? Because some people are creating a "credo" from it and are saying that "estimation is wasted and must be eliminated". That is because the hard side of estimations is not the estimation itself is the attitude you must take along the whole process. Then those people find a way to not answer to people request about "how long it will take". That attemps against the concept of value. Organizations are creating products to take an opportunity and the opportunity has an opportunity window then it is impossible to not estimate. On the other side, a human being can not survive without making estimations then it is totally anti natural. Saving Changes...
Here's another take: "I will occasionally start a team estimating in ideal days. Some individuals are so used to being asked for estimates and responding immediately with a date that the jump to story points is difficult. In these cases, I will have the team start estimating in ideal days." Mike Cohn
In my view "some individuals" is the team, the customer or any stakeholders. Ideal days is just another unit like ideal hours. I will delve more deeply into this if I get a response to this issue from the Scrums founders :-)
But like everyone else, I'm advocate of estimating in points. Just to set the record straight. Saving Changes...
"Put your hand on a hot stove for a minute, and it seems like an hour. Sit with a pretty girl for an hour, and it seems like a minute. THAT's relativity."
