1. Secrets!
of Successful !
Custom Software Projects!
From Steven A. Lowe CEO @ Innovator, LLC!
10!

2. Successful custom
software project
practices are like
common sense.

3. Successful custom
software project
practices are like
common sense.
Which explains the
ridiculously high failure rate.

5. The common culprits?

6. It’s the way we
know how to do it.

7. Fear of
change.

8. Old and outdated
standards.

9. Unconvinced that new or
different methods will work.

10. What’s the definition
of insanity again?

11. I never
said that.

12. If you’ve worked on more than a couple
of software projects, the odds are that
you’ve been on a project that

13. You know all too well
what doesn’t work.
So let’s talk about
what does.

14. of successful custom software projects that not
only meet their goals, but remain in service for
many years.
10! Secrets!Here are

15. Without clear objectives, it is difficult
to know what “success” looks like,
or, when you’ve actually arrived.
Clear Objectives!1

16. Software projects are not a spontaneous vacation
where the journey is the reward.

17. It is about the destination.

18. Only with clearly defined
business objectives is it
possible to lay out a clearly
defined roadmap on how to
get there …

19. … and deal with obstacles
that appear along the way.

20. Commitment!
A custom software solution is not a decision
lightly made and easily changed.
2!

21. Commitment!
A custom software solution is not a decision
lightly made and easily changed.
It requires a commitment to the path and a
willingness to see it through.
2!

22. The rewards are well worth it,
but only for those that persevere with clarity.

23. A change in business goals or executive
support, conflicting objectives, market
changes, loss of key personnel, failing
to perform a risk analysis …

24. … all can easily derail a project and waste a lot of money.

25. Measurable ROI!
If you cannot estimate, much less
measure, the return on investment
(ROI) of a custom software project, it
probably doesn’t have any, and should
not be done.
3!

26. Projects without a
persuasive business
case will not receive
adequate resources,
support, or withstand
the challenge of change.

27. Stakeholder Involvement!
People resist change that is done to them,
but embrace change that they are a part of.
4

28. Stakeholder Involvement!
People resist change that is done to them,
but embrace change that they are a part of.
Make sure all of the stakeholders are
involved in the project, and that their goals
are in alignment with the project goals.
4

29. Unengaged stakeholders lose interest and stop contributing.

30. Project Champion!
A project Champion is a senior
executive with financial authority who
believes strongly in the purpose and
path of the project, and will fight to get
it funded and completed.
5

31. Projects without Champions
are difficult to start, and
rarely finish.

32. Adequate Budget!
Custom software development costs
money. Sometimes, it costs a great deal of
money. It is also often the cornerstone of a
strategic advantage and the lifeblood of
operations.
6

33. Remember to budget for
supporting software,
required and replacement
hardware, training, and
ongoing maintenance.

34. Budget overruns are
a key factor in
project failure and
abandonment.

35. Planning and budgeting for every
scenario greatly minimizes risk.

36. The Right Team!
The right system cannot be
developed by the wrong team.
7

37. The Right Team!
The right system cannot be
developed by the wrong team.
Make sure the development team
has the appropriate domain
knowledge and skill levels to be
successful.
7

38. If your team has knowledge, or skill-set gaps,
add qualified members and arrange access to
subject matter experts.

39. Realistic Expectations!
Rome wasn’t built in a day; your custom
software system won’t be either.
Software development is part science,
part craft, part art, and hard work.
8

40. Realistic Expectations!
Rome wasn’t built in a day; your custom
software system won’t be either.
Software development is part science,
part craft, part art, and hard work.
8
None of these should be rushed; to do
so sacrifices quality and risks failure.

41. Be patient, and work
with the development
team to ensure that
both sides have a
mutual, realistic
understanding of the
process, timelines, and
goals.

42. Training & Maintenance Plans!
Once the software is completed, who will use it?
9!

43. Training & Maintenance Plans!
Once the software is completed, who will use it?
How will they know how to use it?
9!

44. Training & Maintenance Plans!
Once the software is completed, who will use it?
How will they know how to use it?
Who will maintain it?
9!

45. Training & Maintenance Plans!
Once the software is completed, who will use it?
How will they know how to use it?
Who will maintain it?
How will they know how to maintain it?
9!

46. Include plans for
these issues early in
the project.

47. Otherwise, a very costly
and time consuming
software project could
end-up like this cute,
abandoned child’s toy.

48. Which brings us to #10

49. 10! Lifetime Support!
Custom software systems can remain in
service for decades.

50. 10! Lifetime Support!
Custom software systems can remain in
service for decades.
Make sure your plans include provisions for
periodic maintenance, incidental and
emergency support, and someone to care for
and enhance the system over its entire
lifespan.

51. Change
Request
Change
Request
Change
Request
Change
RequestChange
Request Change
Request
New hardware, changes in external
interfaces, and requests for enhanced
functionality place demands on custom
software not considered during the initial
development.

52. The software
must grow with
you, not on you.

53. A custom software system
without planned and funded
lifetime support will lose
end-user satisfaction, not
perform as intended, and
fail to support changing
business needs.

54. Custom
software
systems …

55. Are long-term, strategic investments:
know the reason you're doing it.

56. Can be disruptive to the status quo:
so get everyone affected involved
and excited.

57. Must learn and grow with the
business: so plan for the system to
live long and prosper.

58. Steven A. Lowe
@nov8r!
Know any secrets that we haven’t shared here?
Click to join in the conversation
Innovator, LLC
nov8r.com