2. Shailesh Gogate
VP and Co-Founder
Faichi Solutions LLC
sgogate
Biz Dev guy with expertise across
- Software Product Engineering services
- Digital Solutions for Enterprises.
Have shared and defended many estimates, won and lost clients across the
world; over 20 years in IT industry.
The Presenter, Who?
3. Estimates and the “Push”
• Sales / Customer breathing down the neck
• Want it tomorrow / ASAP
• Budgetary estimates
• with Sprint plans (tentative is fine )
• Parameters of dilemma
• Unknowns
• Types of resources
• Degree of difficulty
5. What do you need?
– Detailed Estimations
– Deliverables (Work Breakdown Structure)
– Milestones
– Project Overview
– Resource loading
– Sprint Plan
6. Detailed Estimations
Pain points:
• Inadequate analysis — Team starts to create estimate and
then realizes they don’t know what sequence they should
follow to complete their analysis.
• Erroneous Estimates — Sometimes delivery cycle is not
viewed in a sequence, resulting in incorrect estimates.
• Estimating similar projects is Redundant and Time
Consuming/ Wasting.
• Significant Manual Effort in factoring Task Complexity and
Hours Calculations.
7. Deliverable Predictions
Pain points:
• Manual calculations — Calculate all development efforts
manually.
• Only one type of estimation — Estimation without
pessimistic or optimistic approach.
9. Project Overview
Pain point:
Aggregate data from multiple spreadsheets — To conclude
the project overview, you are perhaps aggregating data from
multiple spreadsheets.
12. Solution
Need a tool that:
• Expedites estimation process and also automates sprint
planning.
• Leverages the knowledge, expertise, and experience gained by
working on diverse projects.
• Allows project to be split into Drupal specific elements, e.g
content types, views, taxonomy requirements, menus, blocks,
panels, services, SOLR, and similar.
• Equips us with ample proficiency in estimating projects
(extensive experience with Drupal elements).
• Over a period of time, enables you to learn from past estimates
and improve estimations in near future [wish list].
• Reduces guess-timation based on past experience and execution.
13. Dashboard
List of projects that
have been estimated
in the past
Project templates
Entry point for
estimating a new
project
14. Add New Task
Adding details of the
task and number of
hours for each phase
such as Analysis &
Design, Development,
Project Management,
Deployment etc.
19. Generate Sprint – Manage Resources
Manage resources that will be
working on this project.
Automated Sprint Plans will be
generated based on this.
20. Generate Sprint
Default
Automated
Sprint Plan is
generated by
systemLow & High
Estimate Sprint
Plans are also
available
User can do
changes in the
Sprint Plan &
save the same
Sprint Plan can
be exported in
PDF to be sent
to the client
21. Why do you need automation?
• Estimation of software projects has been a pain point for
the industry over the years.
• Gartner reports: Failure rate among software development
projects is close to 30%
• McKinsey reports: Around 66% of software development
projects go by cost overrun and around 44% of the projects go
by the time overrun.
• We are creating this tool that expedites the entire
estimation process and also assists you in the planning
phase.
22. FAICHI SOLUTIONS LLC
USA:
640 WEST CALIFORNIA AVENUE
SUITE 210
SUNNYVALE, CA 94086
Ph: (408) 769-4941
INDIA:
504 ACCORD IT PARK, BANER
ROAD, PUNE, MAHARASHATRA-
411045
Questions?
sgogate@faichi.com
twitter.com/sgogate