To be or not to be Agile ?

1. TO BE
OR NOT
TO BE
AGILE…!
“It's a bad plan that admits of no modification”

2. ABOUT
PRESENT
ER
• Myself Bharat Bhambhaney , having 20 Years of Software Industry
Experience . Worked with all facets of IT projects and services.
• Core competencies include planning IT strategies and project
execution
• Owner of NEET Software (MyOwnOutlet is our eCommerce
solution initiative)
• I have worked on senior and middle level managerial positions in
this tenure and very much comfortable to implement and
recommend IT solutions to the enterprise customers.
• Specialties: • Agile methodology
(Contributor in the book “The art of agile practice”, written by
Mr. Bhuvan Unhelkar”)
• Undergone lot of trainings related to project management and
Agile

3. DISCLAIM
ER
• Shared views in this presentation are my personal and
purely based on my experience with my clients and
projects I worked on.
• Any images / brand or phrases used in this
presentation are for learning purpose only.

4. TAKE
AWAY
I am still learning…..
• Is there a world beyond Agile ?.
• How the key areas like project nature , stakeholder’s nature
, budgeting & estimation , impacts your choice of doing
Agile v/s others.
• How you can win customer’s confidence by getting them in
the market earlier and faster.
• How Agile is used to make an organization a better place to
work eventually.

5. FACTORS
AT
BUSINES
S
ACCOUN
T LEVEL
Key Factors to be considered…
• Definable or Highly uncertain
• LOW / HIGH
• Degree of change
• Frequency of delivery
• Stake holder’s future / business urgency based on the
project ?
• Stake holder’ are open to change / Not open for change .

6. SAY NO
TO AGILE
?
WHY Doing AGILE IS NOT FOR EVERYONE
• When your client has clear development goals.
• Lets talk about Development of Point of sales systems or Accounting
system
• I want a 5 page website with basic information covered
• Your customer requires approvals at each stage of
development.
• Like proof-of-concept type of projects

7. SAY NO
TO AGILE
?
WHY AGILE IS NOT FOR EVERYONE
• Your customer doesn’t want to hear about Agile - Don't
use agile methodology
Business-oriented people who are more interested in
their
core business .
• Your team is not having self-organizing developers
• A well-trained team, aware of Agile principles and practices,
is one of the most important aspects of any Agile project

8. SAY NO
TO AGILE
?
What about Re-Engineering projects ?
(One of USA based agriculture company came to us through some
common reference and they had a lot of issues with existing platform
and at the same time they had a new backlog. )
• When we do Re-engineering , basically we are improving the
structure and design of software.
• So from an Agile point of view Re-engineering is highly confusing.
• Here, Agile is not compatible with re-engineering but Agile is an
alternative to re-engineering. HOW ??
• Agile expects us to change the approach as we develop our product,
not after.

9. SAY NO
TO AGILE
?
One more NO , When we work on maintenance projects but not
always
Ticket based approach where we have lot of bug tickets then new enhancements
For client , top priority is to solve errors then to develop new features .
In such cases being agile approach will be more useful then doing agile
Follow the process, highly adaptable to the changing requirements and environment.

10. Budgeting &
Estimation
Agile Vs Others
How Agile is different
“Needs a budget not the estimate. it’s a
reverse process”
We did a small survey with 10 software companies (Size
10-100 team members) , 7 out of such companies shared
that their cost estimation gets influenced based on their /
client’s approach of doing Agile.
Budget is a hard number always. Whereas estimation
is an open philosophy.

11. Budgeting &
Estimation
Agile Vs Others
How Agile is different (A case study of
eCommerce client)
Our clients wants to get eCommerce site having focused on daily
subscription-based needs like Milk Basket etc..
There could have been two approaches.
1. They could have taken a reference of any existing site
and their features and asked us to get the estimation done.
2. They could have decided a budget and must have
features to launch and look for funding

12. Budgeting &
Estimation
Agile Vs Others
Swipe in and Swipe out approach
“MUST HAVE” approach was preferred with priority-based
backlog.
• Theme with defined UX
• Product management
• Interactive User registration process
• Subscription management
• Reports to trends
• Wallet based payment
• Payment gateway integration
• Subscription and delivery
charges management
• One time buying facility
• Checkout for onetime buying
• Web version.

13. Budgeting & Estimation
Agile Vs Others
Get into the market early
With this they were able to generate revenue or get ready for funding , The
budget was in alignment with the organization’s funding limits in order to
ensure the funding is available till first launch.
With any other approach then agile , considering the same budget they
would have not be able to strategize their product launch.

14. Budgeting &
Estimation
Agile Vs Others
Is Agile less variable ?
Yes as it covers risk of change request and modifications
which causes most of the credit of over budgeting of any
software typically done via waterfall.

15. UNNOTICED
BENEFIT OF
AGILE
• Team culture – Its all about pressure vs productivity
• It changes everything within the organization , changing
mindset of the individual developer to decision maker.

16. UNNOTICED
BENEFIT OF
AGILE
• Cross functional team ready
• Future project planning and capacity

17. Questions ? Queries are welcome

18. Thank you
Connect with me
+ 91- 9998877700
info@myownoutlet.com