Developement Project Management stages and details

Project Start-up

Software Development Process Flow – Project Start-up
The Project Start-up step incorporates the following stages:
Entry Criteria
The Development Agreement/Proposal is received.
Tasks
Software estimation
Project Initiation and preparation/update
Project Management Plan (PMP)
Inspection of PMP
Phase-end Review
Validation and Verification
Approved Project Budget Sheet
Reviewed PMP
Project details made available using the Time Sheet System
Exit Criteria
Approval and release of Project Management Plan
Approved Project Budget Sheet
Phase Deliverables
Approval and release of Project Management Plan


Software Development Process Flow – Requirement Analysis
This step incorporates the following stages:
Entry Criteria
The Project Management Plan is made available to the client.
Tasks
Prepare Software Requirements Specifications (SRS).
Define Acceptance Criteria & prepare Acceptance Plan.
Provide the Phase-end Review.
Inspect the Software Requirements Specifications (SRS) Document.
Validation and Verification
In this stage, the SRS is completely reviewed and fine-tuned according to client requirements.
Exit Criteria
In this stage, the agreed SRS is made available to the client along with the Acceptance Plan.
Phase Deliverables
SRS
 
Software Development Process Flow – High-level Design
This step incorporates the following stages:
Entry Criteria
Agreed Software Requirement Specifications are available.
Project Management Plan is available.
Tasks
Prepare High-level Design (HLD).
Examine the HLD.
Initiate the Phase-end Review.
Validation and Verification
Review of High-level Design is validated, verified, and incorporated.
Exit Criteria
High-level Design documentation is made available.
Phase Deliverables
High-level Design document is delivered to the client with all feedbacks effectively incorporated.
Software Development Process Flow – Low-level Design
This step incorporates the following stages:
Entry Criteria
Project Management Plan is available.
HLD document is available.
Tasks
Prepare Program Specifications.
Provide a Structured Walk through.
Prepare the Test Plan and Test Cases.
Provide a Structured Walk through the Phase-end Review.
Validation and Verification
Review Test Plan.
Review Program Specification.
Review Unit Test Cases.
Review Functional Test Cases.
Review Acceptance Test Cases.
Exit Criteria
Program Specifications are released.
Unit Test Cases are released.
Functional Test Cases are released.
Acceptance Test Cases are released.
Phase Deliverables
Program Specifications
Unit Test Cases and Test Data
Functional Test Cases and Test Data
=============================

Software Development Process Flow – Testing
This step incorporates the following stages:
Entry Criteria
Project Management Plan is available.
Successfully Unit Tested Code is available.
High Level Design, Low Level Design, and Unit Test Cases are available.
Tasks
Conduct testing.
Prepare user documents.
Inspection of user documents.
Provide Phase-end Review.
Validation and Verification
Review functional test results.
Review User Documentation.
Exit Criteria
Tested System is released.
User Documentation is completed.
Phase Deliverables
Test results

Upgrade or reimplementation or Implementation initiation

Whatever your Oracle Financials project, be it an R12 Upgrade , an R12 reimplementation, or a fresh greenfield Implementation.  It is important that you select the right partner and this starts with the RFI, RFQ, RFP & RFT documents.

So what are they ?

• RFI - Request for Information
• RFQ - Request for Quotation
• RFP - Request for Proposal
• RFT - Request for Tender

RFI – Request for Information

This document is the starting point in the procurement process.  You have identified a wide list of suppliers that you think can provide the product or services you require and need to qualify them through to the next stage of the procurement process. The purpose is simply to understand and qualify the potential suppliers, not the specific solutions.  As this is the initial document it does not need to be a long one. Aim for 5-6 pages.

 

The RFI should include:

• Company background and overview
• High level explanation of
  • Requirements giving rise to the RFI ( ie. Products or services giving rise to the RFI )
  • Current systems and issues
  • Where you want to be once the project has been completed. 

RFI Should not include

• Details of other suppliers the RFI has been submitted to. 

What the customer wants from RFI Response	What the supplier wants from an RFI
To gain a general understanding of the competition in the market. Provide enough information for pre-qualification by procurement department. Provide the basis of short listed vendors for the next phase. Supplier references.	To Qualify you as a customer. Understanding of your business, its current issues and what you want to achieve from the project. Specifics on what products and technology the customer is interested in. Estimate of project budget.

 A sample RFI Template document for free download can be found here.