Marcus UdokangProject Manager| Aivaz ConsultingCalgary, Alberta, Canada
In Scrum you estimate during refinement. If you estimate, it might be an indicator that you possibly need more detail in your stories. If the story estimates are too high, maybe they are not clear, or need to be split into multiple stories? Would like to hear your experience or opinion on high or low estimates, and how to get estimating right, or close to right as possible. Should we just not estimate at all? Is estimating crucial in dealing with the complexity and uncertainty of delivery stories? Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Just finished reading the Brain by David Eagleman. Good read, easier to digest than Kahneman.
I learned from both of them that we are human because we cannot help predicting and estimating. All the time. That’s a key element which makes us human.
Agile in my view is totally predictable, in particular Scrum. We agree on a number of sprints for a defined period of time, some rituals and shift most uncertainty to the product owner. The scrum master takes care of our troubles. Easy going.
Commitment is required to be a responsible, trustworthy individual and to create safety for others (team, management, clients).
Estimates are just a specific form of commitment. Saving Changes...
Marcus UdokangProject Manager| Aivaz ConsultingCalgary, Alberta, Canada
@Andrew, much appreciate this point of view. Very valuable to know.
Marcus Saving Changes...
Edgar AlvarezCEO| Actitud & TalentoQuito, Pichincha, Ecuador
Estimating is necessary, especially for business relationships. We could not assume that our clients understand: "I cannot tell you how much it will cost" or "I cannot tell you how long it will last."
Generally for internal projects, with all the own resources, not estimating can be completely valid.
I think we must balance the paradigm and the practices of what to estimate, how to do it and especially when to do it.
Estimation is part of planning, it is recommended to read about “Agile planning onion”.
...
1 reply by Maria Lekha Johnson
Jul 28, 2020 9:19 AM
Maria Lekha Johnson
...
It will be interesting to know about "Agile planning onion". Never heard of that term before :) I will read about this :)
Saving Changes...
Marcus UdokangProject Manager| Aivaz ConsultingCalgary, Alberta, Canada
@Edgar, much appreciate the comment. The Agile Planning Onion is always a great model. Saving Changes...
Wayne MackRetired| RetiredSouth Riding, Va, United States
First, recognize that if a team is doing refinement estimates, then if a project is being used, it is already underway and project estimates for schedule and budget have already been completed.
Second, if the desire is for the development team to determine a plan of attack for accomplishing work and breaking it into smaller work packages, then have that discussion. Do not have an estimation discussion and hope the plan of attack will arise; it usually does not.
Refinement estimation is a different level of estimation introduced by Scrum. It is not project estimation nor is it task completion tracking. Saving Changes...
Marcus UdokangProject Manager| Aivaz ConsultingCalgary, Alberta, Canada
Yes I don't know how I can do a project without estimating - even if internal or external. Estimate gives me a number - some idea of how much time the task would take. Also estimate is just that - an estimate and it is subject to change based on assumptions and constraints. Sometimes we overestimate and many times we underestimate, but again, to begin with, we have some effort hours that we know we must spend. Saving Changes...
Estimating is necessary, especially for business relationships. We could not assume that our clients understand: "I cannot tell you how much it will cost" or "I cannot tell you how long it will last."
Generally for internal projects, with all the own resources, not estimating can be completely valid.
I think we must balance the paradigm and the practices of what to estimate, how to do it and especially when to do it.
Estimation is part of planning, it is recommended to read about “Agile planning onion”.
It will be interesting to know about "Agile planning onion". Never heard of that term before :) I will read about this :)
...
1 reply by Sergio Luis Conte
Jul 28, 2020 9:29 AM
Sergio Luis Conte
...
I will not write this because @Edgar comment, who is a person I know and I respect a lot. I understand @Edgar point. But @Lekha let me say: unfortunately more and more people are invented buzzwords outside there which contributes to general confusion mainly in the Agile field. I am saying unfortunately because the general confusion jeopardize the work for people like me and others whom are working with Agile from long time ago but mainly the needs of people that are trying to find a new job.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Jul 28, 2020 9:19 AM
Replying to Maria Lekha Johnson
...
It will be interesting to know about "Agile planning onion". Never heard of that term before :) I will read about this :)
I will not write this because @Edgar comment, who is a person I know and I respect a lot. I understand @Edgar point. But @Lekha let me say: unfortunately more and more people are invented buzzwords outside there which contributes to general confusion mainly in the Agile field. I am saying unfortunately because the general confusion jeopardize the work for people like me and others whom are working with Agile from long time ago but mainly the needs of people that are trying to find a new job. Saving Changes...
Marcus UdokangProject Manager| Aivaz ConsultingCalgary, Alberta, Canada
