Estimations advanced

AGENDA

Estimations Introduction

Estimations by Test Cases

Estimations by UCP

Estimations by Development

Estimations in Agile

Estimations Introduction

What time do you need to eat the WATERMELON?

Режем арбуз на 20 кусков = 10 мин.
Едим 1 кусок =

THE TRIANGLE RULE

У нас хорошая
документация (SRS)?

У нас есть подобный опыт или эксперты

TROUBLES

- no method gives estimation correct on 100%
- every

Bad News: People too optimistic

300 days??? It’s too much!

Bad News: Customers too pessimistic

SOLUTION

Estimations by Development

PROJECT

Testers

Developers

Relationship

Testing working days = (Development working days) / 3
Testing engineers =

Advantages

Very simple

Very quick

Minimum information required

Minimum thinking required

Is tester – developer ratio constant?

Problems

Relationship may be not linear

Not proportional

When method is useful

No info on functionality
Number of developers known
Past data

Projects where developer time is sold

When method works

Long-term planning

Very quick, first,

Estimations by Test Cases method

When New Project Begins…

Do Estimations

Think How to Test

Collect Questions

Begin Test Cases

Rather exact
Good to get started with estimations
Easy to justify (no mystic)
Widely

Algorithm

1. Create Test Cases Outline

Any format ok
Divide until you can count

I can’t divide this!
What does it mean?

Probably you’ve just found

Ssom
Some test cases may already exist
Number of passes:
Simple: 1-1.5
Average: 2
Complex:

Depends on tester
Novice vs. senior
“exploration” vs. following tests as written
Depends on

Just track it:
Tests per hour
Tests per day
Tests created
Tests tested

Learn Your Figure!

So, I can pass 1 test in 5 min
30 test cases

What’s Wrong?

Not included:
Bug reporting, verification
Troubleshooting
Reports
Emails
Meetings
Risks ( illness, build failed, some tests

Depending on project/customer:
Test cases per day, not per hour
We count average

HOW CAN I DO ESTIMATIONS FOR THE WHOLE PROJECT?

Estimations by UCP methods

Detailed Requirements

Estimation by Test Cases

Don’t have Requirements

?

Estimation by Use Case Points

Troubles

Will not work for Maintenance project
Little REAL experience in EPAM
Different

Benefits

Widely recognized, Used in testing and development
Doesn’t require detailed specifications
Works

Start

Identify, classify and weight “actors”

Identify, classify and weight use cases

1. Determine the number of “actors” in the System

UAW =Unadjusted Actor

2 simple * 1 = 2 2 average * 2 = 4 3

2.IDENTIFY, CLASSIFY AND WEIGHT USE CASES

2.IDENTIFY, CLASSIFY AND WEIGHT USE CASES

E.g.: 25 simple * 1 = 25 20

3.IDENTIFY AND WEIGHT TECHNICAL FACTORS

3.IDENTIFY AND WEIGHT TECHNICAL FACTORS
E.g.:
TFactor = Sum of Weight * Value

4.IDENTIFY AND WEIGHT ENVIRONMENTAL FACTORS

E.g.: EF-Factor = Sum of (Weight * Value)

5.CALCULATE ADJUSTED USE CASE POINTS

Use Case Points are calculated using

CONVERTING POINTS INTO TIME

Karner:
1 UCP= 20-28 hours
1 week=35 hours
Add

SUMMARY. PROS AND CONS

This UCP Method gives us concept about testing

Estimations in Agile

Release planning

Iteration planning

в пингвинах

в часах

Оценка в часах

Оценка в пингвинах, крокодилах, попугаях…
Выбираем эталон в 5 пингвинов.
Оцениваем

Чем меньше задача, тем точнее оценка:
Разбивайте большие хотелки на меньшие
Для каждой

PLANNING POKER

Customer describe the story
Everybody gives a card
Estimate approx. the