|
|
|
|
|
|
|
|
|
|
|
|
|
|
Tip #1
The most important question you can
ask your customer:
Why do you need this project?
Go beyond what and when - ask why.
If you can fulfill "why," what and when are much easier to attain. |
|
|
Tip #2
There is nothing more powerful
than a team on a mission.
Develop your mission based on why
the customer needs the system. Communicate your mission verbally, in writing,
in cyberspace, and in your actions. |
A goal without
a deadline
is a dream. |
|
Tip #3
The secret to getting your computer
projects done correctly the first time is to work with technical people
who focus on completion.
Starting and working with a relentless
focus on successful completion is as important as finishing with that same
focus. |
|
|
Tip #4
The best way to save money on your
computer projects is to complete them correctly the first time.
No matter what your initial cost is,
get the right people and do the project correctly the first time. It will
cost less than redoing the project or maintaining a substandard system. |
|
|
Tip
#5
The primary goal of every project
development team must be to get the project done on time, within budget,
and with a smile on everyone's face.
With this as your primary goal, your
chances of completing the project on time, on budget, and correctly the
first time, go way up. |
|
|
Tip
#6
User involvement is a critical
and ongoing part of systems development. It must begin on day one.
Do not wait until the end of the project
to get user feedback. Getting user commitment before you spend money is
your best assurance that the money is well spent. |
|
|
Tip
#7
Completion is a team sport!
It takes more than one person to complete
a computer project. The whole team - programmers, users, vendors, management,
and others - must be committed to playing on the same team. To achieve
this, positive communication and a clear focus on completion are key. |
|
|
Tip #8
Make your list and check it twice!
In fact make two lists.
One for "Accomplishments" and one
for "Action Items." We agree it is important to know what still has to
be done on a project. It is just as important to know what has been achieved.
Check both lists every day. |
|
|
Tip #9
If your software is not properly
tested - it is not done!
Testing should be designed to find
and fix problems.
Be rigorous in developing and executing
your test plan. Don't just test 'normal' processes, test everything. If
you don't find the bugs - your user will! |
|
|
Tip #10
Every software project needs a
plan!
Project plans must be accurate
and in writing.
The purpose of a project plan is to
define how a project will be completed. This includes clear definition
of the tasks, realistic time estimates, assignment of the right people
to each task and the commitment to keeping them there through completion." |
What is this
game?
Do I want to
play?
How do I win?
What do I need
to do to win?
Am I willing
to do what it
takes to win?
We are responsible
for how we
communicate
with the
customer |
|
Tip #11
Time, money, and the ability to
have exactly what you want are competing factors in determining your best
path to successful completion.
Prioritize them according to your
needs.
Remember...every project is different!! |
|
|
Tip #12
Project Completion does not happen
by accident.
You must define, communicate, plan,
implement, and improve it.
When your computer projects are not
getting done on time, doing the same things in the same way with more intensity
rarely fixes the problem. You need revolutionary ideas and completion-focused
processes. |
|
|
Copyright
1999-2003, Completed Systems, Inc. All Rights Reserved |