This document discusses common risks in software development projects that can lead to failure and how to avoid them. It outlines three main risks: 1) Bad project estimates that result in projects taking much longer than planned to complete. To avoid this, an accurate feature-by-feature estimation is done upfront. 2) Poor functional requirements that don't accurately capture needs. To avoid this, requirements are analyzed and validated through prototypes. 3) Lack of change management that results in additional costs when changes are needed. To avoid this, a clear change management policy is agreed upon beforehand to allow for changes within budget. Careful project planning can help avoid these risks and increase chances of project success.

1. Approach
to software development

2. Let’s pretend…

3. YOU MADE AN EXCELLENT
BUSINESS IDEA
Now you need someone to
create software for you
Mobile app, Web service, Enterprise system… whatever

4. Looks like not a big deal...
But where is the trap?

5. The truth is that…
68% of software projects fail!
Nothing personal. Just facts.

6. BUSINESS GIVES NO SECOND CHANCE
In case of failure you lose your time and miss great opportunities
even if you fortunate to get some of your money back

7. Now let’s study what
are the risks that make
software projects fail
And how to avoid them

8. Risk #1
“Large team works hard
for 6 months but the
app is still far from
complete”
Reason:
Bad project estimates at the
start

9. WHAT WE DO
We give you an accurate
feature-by-feature estimation so
you can define and manage
project scope before it starts
How it works:
You choose features to implement and
features to postpone until the scope
meets you timeframes and budget

10. Risk #2
“It is done as you said
but it works completely
wrong!”
Reason:
Poor functional requirements
In your head the puzzle always fits
together. But as the development starts
you realize that there are blind spots and
conflicts

11. WHAT WE DO
We involve analysts to study
your requirements and make
them complete and coherent
How it works:
We make feature lists, screenflow diagrams
etc. to reveal and correct all the defects
making your requirements just perfect
We use prototypes to get a common vision
of results before the development starts

12. Risk #3
“You got an idea on how
to improve the app but
developer asks for extra
charge”
Reason:
Lack of change management
skills
Newbies try to avoid changes. That is wrong.
Actually changes are not a problem. Moreover
changes are essential for a successful project.
You just need to know how to cope with it.

13. WHAT WE DO
We know that changes are
necessary and know how
to stay within the budget
How it works:
Before the project starts we
agree on the change
management policy so it allows
you to change and improve your
requirements without breaking
the process

14. Chose carefully.
Chose someone who knows the risks.
Chose someone who has the plan for that.
Chose SSP Software.

15. Please visit our
website to learn more
about SSP Software
http://www.ssp-soft.com