SOFTWARE DEVELOPMENT AND DELIVERY PROCESS (SDDP)

SNo 1

Sub Process Name

Entry Criteria

Tasks

Sub Process Description (Steps)

Verification & Validation

Exit Criteria

Sub Process Owner

Project Start Up

Proposal, Prepare the SOW, Contract project plan. available

Setup IT and Non IT infrastructure

1) Pick up the standard project plan template from QA and fill in all relevant sections of the document 2) Prepare Detailed Plan using the standard template. 3) Identify work place.

Review and release the Project Plan. Review, Release the Detailed Plan. Verify Non IT infrastructure

Project Plan released.

PM, QA

Team Building

4) Setup H/W, S/W environment as given in the proposal. 1) Request HR for manpower resource allocation. 2) Team Induction and Training.

3) Update and circulate Project Plan and detailed plan to team members. 4) Setup Timesheet for team members. 1) Prepare the presentation using the standard template.

Conduct Kick Off

Detailed Plan PM, QA released Non IT PM, Admin infrastructure setup complete Verify IT IT infrastructure PM, System Admin infrastructure setup complete Verify resource Resource allocation allocation complete Verify training Team Induction PM, HR records and Training is done and Training Records verified Verify the process Project Plan, PM, QA Detailed Plan updated and circulated Verify the setup Timesheets are PM, PMO set Review the Presentation is PM presentation completed
Page : 1

meeting 2) Follow up with the PM for the project Kick Off meeting. 3) Schedule and conduct Kick Off meeting. 4) Circulate MOM. Phase 0: Commence Project Execution 2 Requirement Analysis Project Plan released, Infrastructure setup, Team building complete and Kick Off meeting conducted. Detailed Analysis of user requirements 1) Prepare detailed requirements document using SOW. Review Detailed Requirements Document Detailed Requirements Document released QA PM, QA QA PM, QA PM, TL

Kick Off meeting conducted MOM is circulated

2) Prepare DFD and Use Case diagrams.

Review DFD and Use Case diagrams Review Test Strategy based on SOW

3) Prepare Test Strategy based on acceptance criteria given in the SOW. 1) Implement clients applied design templates if any.

DFD and Use Cases reviewed and released for delivery Test Strategy document released

PM, TL

Test Lead, PM

Phase 1: Deliver Detailed Requirement Document (DFDs, Use Cases etc.) to customer and obtain sign off. 3 Design Detailed Requirement analysis complete, DFDs, Use Create Design Document Design templates are implemented

PM, QA Designer

Page : 2

Cases available 2) Create design artefacts using DFDs and Use Cases. Review design artefacts using checklist. Design Artefacts are released Designer, Tester

Phase 2: Deliver Design Artefacts to customer and obtain sign off. 4 Construction Design Artefacts complete, Design Pages available Start coding 1) Create the new project in Project Verify the project Management System. on PMS Project Created

PM, QA PM, QA

2) Discuss the coding standards with PM and Code the application as per the standards. 3) Implement client changes if any. 4) Update the project plan according to the scope addition or any changes from client side. 5) Do configuration management for the project according to the changes.

Review the code and log defects Review the client changes. Review the project plan Review the project versions

Coding is completed, Code Review is done. Changes implemented Projected plan updated

Developer, PM

Developer, PM PM, QA

PM, QA

Phase 3: Deliver Developed Modules/Application to testing team. 5 Unit / System Testing Coded module or application is available Test the modules 1) Maintain a testing server for the application. 2) Test the modules as per the test case document. 3) Prepare test report and send it to concerned person. Verify that separate server for testing is there Review the application Review the Test Report Testing Server installed Application reviewed Test Report created

PM, TL System Admin, TL, Test Lead Tester Tester, Test Lead

Page : 3

Phase 4: Deliver Developed Modules/Application to user for UAT. 6 User Acceptance Testing Whole Application/ Module is available Test the application 1) Install the application on user side. Verify the installation process Application installed

PM TL, PM

2) Test the application on user side. 3) Maintain document for customer changes/ issues. 4) Work upon the customer issues. 5) Do configuration management for the project according to the changes. 6) Do Satisfaction Survey. 7) Do the final billing. 8) Notify all support function heads.

Review the client changes Verify the issues

Application tested Document maintained Issues verified and resolved

Tester, Customer PM, TL Developer, PM PM

Verify the survey Verify that all are notified

Survey Done Support Function heads notified

Sales, QA Sales Sales, QA PM, Sales

Phase 5: Release the final version of the application and obtain acceptance sign off. 7 Project Wind Up Project delivered and signed off Conduct Wind Up meeting 1) Prepare the presentation using the standard template. 5) Follow up with the PM for the project Wind Up meeting. 6) Schedule and conduct Wind Up meeting. 7) Circulate MOM. Phase 6: Windup Project & Release Resources Review the presentation Presentation is completed

PM

Wind Up meeting conducted MOM is circulated

QA PM, QA QA PM, QA
Page : 4