Standard Development Life Cycle
Is the project even feasible to do? Is it cost justified? Can the project be finished in time? Is
there a return on the investment? Will you get more savings in return than the cost of
designing and developing the process? All these questions need to be answered.
In the feasibility phase you need to identify your resources for the tasks to come. At the same
time you need to check any competing projects that will interfere with the resources you
For example, if the accounting department is your primary resources for input and those
individuals have been assigned to some other task, it could very well interfere with the time
line of the project. It may not even be feasible to start the project.
You will also need to do an "AS IS" study. What is the design you are going to mimic? Are all
the processes defined? A major step in this phase is to do a storyboard. Work with users in
each department affected in the project and document all steps and processes.
For each Process you will need
Finally you will need to:
Generalize current system flow (AS IS)
Evaluate current running cost
Evaluate cost of all NEW Resources
(Hardware, Software, Business Users, Developers,Training, Travel)
High level cost of each Process to design
After all the tasks above are complete
For each AS IS Process that was defined, you will need to identify with the new system how
they will be handled or how it will be replaced.
All the As Is processes will be the Basis of the Analysis Phase. Each task will either be
redesigned or if able carried forward.
Benefits of the Feasibility Phase.
- Knowledge of what will need to be replaced(AS IS)
- Upfront valuation of the project
- Knowledge of competing projects
- Knowledge of core project team