- Главная
- Разное
- Дизайн
- Бизнес и предпринимательство
- Аналитика
- Образование
- Развлечения
- Красота и здоровье
- Финансы
- Государство
- Путешествия
- Спорт
- Недвижимость
- Армия
- Графика
- Культурология
- Еда и кулинария
- Лингвистика
- Английский язык
- Астрономия
- Алгебра
- Биология
- География
- Детские презентации
- Информатика
- История
- Литература
- Маркетинг
- Математика
- Медицина
- Менеджмент
- Музыка
- МХК
- Немецкий язык
- ОБЖ
- Обществознание
- Окружающий мир
- Педагогика
- Русский язык
- Технология
- Физика
- Философия
- Химия
- Шаблоны, картинки для презентаций
- Экология
- Экономика
- Юриспруденция
How to make great software estimates презентация
Содержание
- 1. How to make great software estimates
- 2. And it begins… How long does it
- 3. estimating These are all questions we ask
- 5. How long it will take It
- 6. Experience Have I ever worked on this
- 7. Experience starts the process of asking yourself these questions with each problem.
- 8. experience The person with the most practice
- 9. Knowledge Do you know what language you
- 10. What do I know that I can leverage in this estimate?
- 11. Knowledge The culmination of everything we know
- 12. UNDERSTAND “I didn’t understand the problem”
- 13. Never start coding if you do not understand what you are trying to code.
- 14. Understand the problem Know the end
- 15. When will We ship?
- 16. Not YET We have only figured out
- 17. SO When will it be ready?
- 18. Your Confidence Is the most important component
- 19. And what should you not apply to an estimate?
- 20. Speed Do not build “acceleration” or “in
- 21. No Copying NEVER use someone else’s estimates
- 22. No Guessing Guessing is for the lazy
- 23. SO REMEMBER…
- 24. Good estimates Will tell you how long
- 25. Greg Thomas http://www.rambli.com
And it begins…
How long does it take to build this widget? When will you be done? Do I know what am I doing? Where do I start? What did they
Слайд 2And it begins…
How long does it take to build this widget?
When
will you be done?
Do I know what am I doing?
Where do I start?
What did they ask for?
Did I think this through?
Have I missed something?
Am I as fast as Jeff?
Do I know what am I doing?
Where do I start?
What did they ask for?
Did I think this through?
Have I missed something?
Am I as fast as Jeff?
Слайд 3estimating
These are all questions we ask ourselves when we, as developers,
are presented with a new problem and asked to provide an estimate as to how long it will take AND when it will be ready.
Слайд 5
How long it will take
It starts with looking at your experience,
knowledge and gaining a keen understanding of the problem.
It starts with 3 Core Tenants
It starts with 3 Core Tenants
Слайд 6Experience
Have I ever worked on this component?
What language am I using?
Do
I know this language?
Is this a hard problem?
Do I know the platform?
Do we have requirements?
Is this a high-priority?
When does it need to be done?
Is this a hard problem?
Do I know the platform?
Do we have requirements?
Is this a high-priority?
When does it need to be done?
Слайд 8experience
The person with the most practice in that particular area of
development will always yield the most “near” accurate estimation as to what needs to be done and how.
Experience grows over time and increases with each success and failure.
You want to fail, to get better.
http://www.rambli.com/2015/10/factors-of-software-estimation-experience/
Experience grows over time and increases with each success and failure.
You want to fail, to get better.
http://www.rambli.com/2015/10/factors-of-software-estimation-experience/
Слайд 9Knowledge
Do you know what language you are using?
Do you know the
underlying framework and architecture?
Do you have Domain Knowledge to your field?
Do you have expertise on the platform you are building on?
Do you have Domain Knowledge to your field?
Do you have expertise on the platform you are building on?
Слайд 11Knowledge
The culmination of everything we know applied to what we know
about the problem and our experience.
http://www.rambli.com/2015/10/factors-of-software-estimation-your-knowledge/
http://www.rambli.com/2015/10/factors-of-software-estimation-your-knowledge/
Слайд 12UNDERSTAND
“I didn’t understand the problem”
“I’m not 100% sure what to do
here”
“It should just work”
“It didn’t do this last time”
“It should just work”
“It didn’t do this last time”
All statements that are uttered after you have started coding, but failed to take the time to understand the problem you are trying to solve.
Слайд 14
Understand the problem
Know the end user and identify what they expect
Learn
the platform/architecture that you are building on
Write down your assumptions and vet them with your users, peers and team.
There is no “should” when you Understand.
http://www.rambli.com/2015/10/factors-of-software-estimation-understand-the-problem/
Write down your assumptions and vet them with your users, peers and team.
There is no “should” when you Understand.
http://www.rambli.com/2015/10/factors-of-software-estimation-understand-the-problem/
Слайд 16Not YET
We have only figured out how long it
will take
to accomplish our task
By Understanding the Problem, leveraging
our Experience and applying our
Knowledge we have created an estimate
that we feel can stand by.
But it is not shipping time!
By Understanding the Problem, leveraging
our Experience and applying our
Knowledge we have created an estimate
that we feel can stand by.
But it is not shipping time!
Слайд 18Your Confidence
Is the most important component to any estimate. How confident
are you in your estimate? 75%? 80% ? 50%?
Whichever the percentage, that is your SLUSH, which is the amount
of extra time you think you might need to accomplish this task.
Whichever the percentage, that is your SLUSH, which is the amount
of extra time you think you might need to accomplish this task.
http://www.rambli.com/2015/11/factors-of-software-estimation-slush/
Слайд 20Speed
Do not build “acceleration” or “in the zone” time to your
estimates. You are only as fast as you are going now. Building in future “I’m gonna know it by then” numbers will only hurt you down the road.
Слайд 21No Copying
NEVER use someone else’s estimates as yours. You don’t have
their experience, knowledge or understanding of the problem.
They are not yours, you are already behind if you take them as your own.
They are not yours, you are already behind if you take them as your own.
Слайд 22No Guessing
Guessing is for the lazy – “I don’t know, say
200 hours” – this means nothing, this helps with nothing, it might as well have been 2 hours as the result will have been the same.
Слайд 24Good estimates
Will tell you how long and when you will deliver
Bad
estimates
Will give you nothing
Will give you nothing
