Activity study: Understand, analyze and document the
processes, tasks and activities of the function
Requirement collection: Collate, analyze, and prioritize
user and manager issues with current system
Evaluation of alternatives: Help in build or buy decisions.
Decide between alternatives for system changes – build new customized software system,
make enhancements to existing system, buy software products.
Scope definition: Define project scope. The project
size and scope is limited by time and cost considerations.
Build RFPs: Build Request for Proposals with clear demarcation
of features and priorities.
Evaluate responses to RFPs: Assess and compare vendor
responses to RFPs. View demos and evaluate trial versions of out-of-the-box products.
Vendor contracts: Define penalty clauses for delayed
delivery; service level agreements for support; link payment schedule to completion;
user acceptance criteria; and clauses such as ownership of source code for customized
software.
Requirement specifications: Prepare detailed software
requirement specifications that includes functional, technical architecture and
screen level details.
Requirement validation: Validate requirements for compliance
with user requirements collected.
Development: Work with the vendor to facilitate development
as per the project schedule.
Delivery: Ensure that delivery criteria in terms of
functionality, documentation and performance are met. This includes user acceptance
testing.
Transition from legacy system: Transition includes migration
and conversion of data. User training: Training users in use of the new system.
Release management: This includes processes for version
control, release cycles for emergency, major and minor releases.
Change management: This includes processes for requirement
changes when a project is in progress.
Root-cause analysis: This analysis is performed for
completed or abandoned or suspended projects to analyze causes of failures and design
remedies to salvage the project.