ESTIMATION

IN AGILE
The Way We Do It
Table of Contents
Estimation in Agile 03

Discovery Phase 05

1. Stakeholder Interviews 06

2. Define High Level Product Backlog 07

3. Information Architecture 08

4. Prioritization 09

5. MVP Backlog 11

6. Estimation 12

Contact Us 13
Estimation in Agile
Ensuring a successful software delivery within the constraints of “The Iron Triangle” has
been an enigma that each software development methodology has aimed to solve.

Scope

Schedule Cost

These 3 dimensions of scope, cost, and schedule are interdependent. In any scenario, it
is possible to make only one of these 3 dimensions constant. For developing a software
within a certain cost, the scope and schedule will have to be kept variable. Similarly, if the
schedule or a deadline is a constant, the scope and cost need to be variable.

No matter how much we want we cannot fix all the three or even two. It would, otherwise,
elude the DNA of software development. Taking a step back: the Iron Triangle is a
legacy handed down to the software development world by the world that built cars and
buildings - a world where cost, scope and schedule was based on properties.

These could be estimated in detail prior to manufacturing, planning that could further be
handed off to the builders -- plans that did not change after the assembly process started.

3
Software delivery is another world. Requirements or the scope keeps changing. Hence,
the biggest questions that arise are - How do we estimate the cost? How do we plan for
the schedule? Enter the proponents of the Agile methodology who endorsed the fact that
change is at the core of software development; so, rather than fight change, we learn to
manage change, almost celebrate change!

The Agile methodology, at its core, uses the technique of breaking down the work into
small batch sizes and uses continuous market feedback to guide progress. So, unlike the
assembly line where the customer does not see the product till the end, in Agile, a small
increment of the product is available for a “show and tell” at short intervals. Decisions can
be made if the plan is adhered to or there are course corrections. Build what is needed not
what was planned.

The cost involved in this methodology is essentially the cost of the dedicated team that
comes together to deliver.

Planning and Design Development Testing Delivery

In a real world, even though we appreciate the merits of Agile, and we embrace the fact
that changes will take place, we want to carve out a budget to estimate our spending.
When we start with a project, we have a limited horizon. At Net Solutions, we propose a
short discovery phase to tide over this problem.

4
Discovery Phase
The discovery phase takes up the essential tenet of the Agile methodology that entails
breaking down the requirements into small batch sizes. This is an exercise that consumes
typically 2-4 weeks, depending upon the complexity of the business problem. The
discovery phase unfolds as follows:

Stake Holders

Business
Owner

Scrum Product
Master Owner

Scrum Team

5
 01

Stakeholder Interviews
The Business Analyst (BA) allocated for the discovery team revisits any existing
documentation you share initially, and frames the gaps and queries out of it.

The BA then conducts regular workshops with the stakeholders to discuss the gaps and
clarify doubts in the system workflow. These workshops can be conducted over a call with
the client or client visits our premises to have one-on-one sessions.

6
 02

Define High Level Product

Backlog
The Business Analyst (BA) allocated for the discovery team revisits any existing
documentation you share initially, and frames the gaps and queries out of it.

The BA then conducts regular workshops with the stakeholders to discuss the gaps and
clarify doubts in the system workflow. These workshops can be conducted over a call with
the client or client visits our premises to have one-on-one sessions.

Product Backlog
Evaluate feedback, Evolves
update backlog

Scrum Team Product Increment

Implements top
backlog items
Give
Feedback

Users

7
 03

Information Architecture
Depending upon the complexity of the problem the application is intended to solve, a UX
anchor is taken onboard, along with the BA, for the discovery phase. UX Analyst’s prime
deliverable is to understand not just you, but also your customer(s). The UX analyst works
on personas of the possible user group who could use the application, the ecosystem in
which the personas will be using the application and touchpoints of the user personas with
the system.

The deliverables here would be Ecosystem maps, Personas, User Journeys & Storyboards.
The primary deliverable from the UX Anchor would be to provide a complete Information
Architecture for the application giving an overview of the system

8
 04

Prioritization
The discovery team then works on the high level backlog, once validated by the
stakeholder. MoSCoW Analysis is employed as the prioritization method to decide which
requirements to complete first, which ones must come later and which ones to exclude. The
backlog items are divided into ‘must haves’, ‘should haves’, ‘could haves’ & ‘won’t have’.

The items with highest business value and lowest effort involved are often the items that
qualify the ‘must haves’ criteria. The items that are of higher priority and will need some
effort to be delivered are deemed as ‘should haves’.

All the backlog items that might be desirable in

terms of scope but are of lower business value
are segmented as ‘could haves’. The items that
are agreed upon to be moved to later releases
are filtered out, as ‘wont have’ now.

Must Have
Minimum
Usable
Subset
Business
Should Have Case

Could Have
Contingency

9
Get a Free,
1-Hour Long,
1:1 Consultation.

Book Your Free Consultation

10
10
 05

MVP Backlog
Based upon the prioritization activity, the BA assembles the requirements as ‘must haves’
to the backlog and sections it as the requirements for achieving a Minimum Viable Product
(MVP).

The MVP backlog might also contain few items from the ‘should have’ items making sure that
product is competitive enough in the market.

Product Backlog Minimal Viable Product

Feedback Users

11
 06

Estimation
The discovery team estimates the MVP backlog to define the estimated cost and timeline for
the first Release. This is followed to build, rinse and repeat till we arrive at an estimate that
fits the business need.

This also allows a flexibility to load and off-load features as the product development starts.
Remember we committed to endorse change as we get a better view of the horizon.

12
Contact Us
Say Yes to Agile Development.

Helping you grow your business is our priority.

Our team of experts is here to answer any
questions you might have to make your Agile
journey a cakewalk.

Request Free Consultation

TORONTO NEW YORK LOS ANGELES

111 Queen Street, East 101 Avenue of the Americas, 11601 Wilshire Blvd
South Building Suite 450 8th Floor, New York City, 5th Floor
Toronto, ON - M5C 1S2, New York, 10013 Los Angeles, CA 90025
+1 (416) 720-1790 +1 (305) 767-3821 +1 (305) 767-3821

LONDON CHANDIGARH
Aldgate Tower Site No. 15, Phase 1,
2 Leman Street Rajiv Gandhi Technology
Fourth Floor Park Chandigarh
London, E1 8FA UT - 160101,
+44 (208) 610-9966 +91 (172) 431-5000