Small Business Best Practices Series

How to quickly build low risk, high value

business applications following agile methodology

Agenda

• Introduction• Presentation• Q & A session

Introduction

ExpertMetrix.com• Marketplace for sourcing IT and

Business Process services.• In-depth analysis on service

providers.• Only established providers, no

freelancers.

DeltaMinds Software• Located in Kolkata, India• Offers web and mobile application

development services. • Expert in E-Commerce and

Telecom domains.

How to quickly build low risk, high value business applications following agile methodology

Too much competition

Changing business dynamics

New ideas emerging

Higher customer demands

• Create enough value.• Faster time to market.• Early feedback from customers.• Quickly respond to changes.• Evolve continuously.

To Survive..

The Success Mantra..

So you have an idea..

The idea is analyzed, reviewed and agreed and the end result is, a long list of requirements.

Requirements specification

Increase revenueDecrease costImprove ROI

8 Steps of Traditional Development Methodology...

Requirement Analysis

Solution Architecture

Approve Tech Specification

CodingSystem TestingUser Acceptance Testing

Deploy

Review & Approve Requirements

Defects

The Leakages...

Requirement Analysis

Solution Architecture

Approve Tech Specification

CodingSystem TestingUser Acceptance Testing

Deploy

Review & Approve Requirements

Defects

The Problems...

Requirement Analysis

Solution Architecture

Approve Tech Specification

Coding

System Testing

User Acceptance Testing

Deploy

Review & Approve Requirements

Have we considered?

• New ideas can emerge anytime , not just at the beginning.

• Opportunities and threats come and go unexpectedly. We must respond to them quickly.

• Longer time to market.• No early feedback from

customers.

1

2

3

4 5

6

7

8

Pitfalls in Traditional Approach..

• Two-thirds of IT projects are challenged.

• 189% of the projects go over budget.

• 220% of the projects miss their schedules.

• Only 61% of planned features get delivered.

• Poor quality.

• Slow.

• Expensive.

Source: Standish Group, CHAOS reports

Move to Agile..

Agile software development is an iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

Better

Faster

Cheaper

Collaboration

Working Software

Respond to Change

Agile Way..

RequirementsAnalysis

• Bring stakeholders under one umbrella.• Create small , coherent, cross-functional teams.• Bigger features to smaller ‘Stories’.• Prioritize stories based on business value.• Work in shorter duration ‘Time-Boxes’ (maximum

6 weeks).• Deliver a working system (i.e. value) at the end

of each ‘Time Box’.

Build

Test

Design

Deploy

Time Box

Little More on User Stories..

• Stories define a business requirement in one or two sentences.

• It captures who, what and why of a business requirement e.g. Customer wants to sort a product list by price to find the cheapest product first.

• Create a story card on a post-it note and write how to test this feature at the back of the card.

Collaborative Workshops

Right Prioritization..

Story Boards..

Time Boxes..

UnderstandPlan

Design & BuildSystem Test

UAT

UnderstandPlan

Design & BuildSystem Test

UAT

UnderstandPlan

Design & BuildSystem Test

UAT

6 weeks 6 weeks 6 weeks

Value Value Value

Adaptive Planning..

Benefits of following Agile methods

traditional

Agile

Time Time Time Time

Agile Statistics..

• 67% increase in productivity.

• 65% more quality.

• 49% improvement on cost.

Comparison of Financial Benefits with other methods....

In Summary..

• Faster time to market.

• Continuous Delivery.

• Better Quality.

• Reduced Waste.

• Higher Value.

• Lower Risk.

• Better ROI.

• Higher Morale.

Thank you!

• Have questions on Agile methods?

email us at: support@expertmetrix.com.

• Like to become a member of ExpertMetrix? email us at: support@expertmetrix.com.

• Find us on the web at www.expertmetrix.com.