AGILE Practice

Ideal Team Size

~ 6 to 7 Members .

Agile Team structure:

One Scrum Master
One Business Analyst
Three Developers
Two QA folks

Estimation Techniques
Activities (Prod. Development)
Requirement management : 20
Design & Coding : 50
Testing QA : 20
Documentation : 5
Release: 5

Bible
A typical story, will contains work deliverables all entire SDLC from - Req. Analysis +
Design + Coding + QA + Documentation.
Ideal scenario :
7 Members ,
70 Points as the team velocity
14 calendar days.
Team hours per sprint 112 * 7 = 784 hours
Then one Agile point should be = Total hours / Team velocity , ie, 784 / 70 =~ 11

Custom set for PRODUCT

14 working days per sprint
Then 14 days mean 112 hours per person.
Team hours per sprint 112 * 4 = 448 hours
Team velocity 40 points

Then Ideal point / hours achievable = 448/ 40 ~ 11.2 . Which means 1 point will finish in
approx. 11 hrs.

By that logic, Team of 4 has 32 hours in a day so that approx. 32/11 = 3 points per day by the
team

Use Case Point Estimation

Factors Considered:
Technical Complexity (Simple, Average,
Complex)
Environmental Complexity
Productivity Factor (How many actors are
involved).
Dependency on other team member
(Sequential work)

Work Buckets
Requirement Analysis
Design and Coding
Testing
What we do in sprints:
Stand up Meetings
Retrospective meetings.
Excerpts from those meetings are uploaded in
confluence.

Estimation Techniques
3 kinds of work
New requirement : work involved

Requirement gathering
Analysis & elicitation
Acceptance criteria
Solution Design
Technical design
Coding
Test Scenario/case preparation
Product documentation
Testing & release

Enhancements

Requirements enhancements
Impact study
Design enhancements
Updating of all testing & TW artefacts
Implementation
Testing & release

Bug fixes
Other than the exiting bugs we wont be taking into planning
All the newly reported bugs (internal) has to be addressed within same sprint by utilizing buffer time ,
Retesting and integrated testing along with other deliverables

Retrospection
Things that went well:
We are the first team to visualize and execute Agile
process.
We are able to execute as per our planning (mostly).
We are able to write our on SRS (Technical / functional
spec) even though we rarely got proper business
requirement.
Things that did not go well:
Adhoc requests impacted the sprint execution.
Lack of proper business requirement had an impact on
functional requirement.