Project management is the controlled process of initiating, planning, executing, and signing off a project. At cygnet Infotech, we follow two SDLC mainly Agile and Iterative Incremental Life Cycle.
The list of phases and deliverables that are provided for Large Projects has been mentioned below.
The phase execution will vary as per the SDLC type selected for project execution i.e. parallel execution of phases or one after the other.
| Project Estimation |
|
This phase applies to all software projects and its objective is to establish effort estimation by studying the requirement, checking the feasibility, searching for third party controls/component, if required.
Key Task to be performed
- PM/PL/TL/Developer do Feasibility Study, if required
- PL/TL identify Work Products and Tasks
- PL/TL identify Unit of Measure (UOM)
- PL/TL Estimate the Effort
- PM/PL Review Estimation
- PL/TL Update Estimation
- PM Approve Estimation
|
|
Input:
Estimation Procedure
Estimation Guideline
Estimation Rational
Requirement Feasibility Study Template
Estimation Template
Output:
Requirement Feasibility Studies
Estimation Sheet |
|
| Project Initiation |
|
Upon Client approval on effort estimation Project is initiated in the organization.
Key Task to be performed
- MM & PM will have project initiation meeting, Project Code & PIN (Project Initiation Note) generation and PL selection
- Center Head/MD Approval of PIN (Project Initiation Note)
- PM will create Project on Project Server-SharePoint and Mantis (Bug Tracking Tool)
|
|
Input:
Project Initiation Procedure
Project Initiation Note Form
Output:
Project Initiation Note |
|
| Project Planning |
|
This phase consists of, steps to be executed for process tailoring to suit the project requirements, planning project activities and preparation of project plan, test plan & project schedule.
PM & PL prepares the Project Process Tailoring Form and it’s reviewed & approved by SEPG Head.
PL prepares Project Plan and it’s reviewed & approved by PM.
Project Plan will include:
- Plan Required Resources, Knowledge, Skills, Software, Hardware, Third Party Tools / Components / SDKs
- Identify, Plan & Involve Relevant Stakeholders
- Identify Risks & Plan Mitigation/Contingency Actions
- Plan usage of Organizational Process Assets
- Develop Quality Assurance Plan, identify Quality Control method for Validation & Verification using Peer, Supervisory & External Review
- Plan Monitoring, Reporting and Controlling Mechanism
- Plan Integration Strategy
- Develop Configuration Management Plan
- Develop Measurement and Metrics Plan by considering Organizational Quality Objective like Productivity, Review Defect Density, Test Defect Density, Effort Variance, Schedule Variance, etc
- Develop Training Plan
- Identify Test Approach
- Identify Testing Environment
- Identify Suspension Criteria & Resumption Requirements
PL prepares Project Schedule including all SDLC Phases and it’s reviewed by PM.
PM, PL & Project Team does Kickoff Meeting to start execution of Project. |
|
Input:
Project Management Procedure
Risk Management Procedure
Project Tailoring Guidelines
Project Management Guideline
Risk Management Guideline
Configuration Management Guideline
Measurement Guideline
Project Process Tailoring Form
Project Plan Template
Test Plan Template
Project Schedule Template
Output:
Project Process Tailoring Form
Project Plan
Resource Requisition Form/MOM
Project Schedule |
|
| Size Estimation |
|
PM and PL calculates initial size of the project which will be used to measure & track defined targets against Organizational Quality Objective like Productivity, Review Defect Density, Test Defect Density, Effort Variance, Schedule Variance, etc |
|
Input:
Estimation Procedure
Estimation Guideline
Estimation Rational
Output:
Estimation Sheet |
| Requirement Analysis |
|
- This phase consists of bridging the gap between the project domain and the technical domain. This phase requires maximum client interaction.
- PM, PL and SPA communicate with client for requirement gathering and clarification.
- Analyst team prepares Scope Document, Scenario Diagram(s)/ Flow Diagram(s) & SRS and it’s reviewed & approved by PM/PL & Client.
- Upon Client approval on Scope Document, Scenario Diagram/System Flow Diagram & SRS, Mock-up/Prototype is prepared and it’s reviewed & approved by PM/PL & Client.
- Upon Client approval on Mock up/Prototype, SPA prepares Requirement Traceability Matrix for SRS & Mock-up and it is reviewed by PM/PL.
|
|
Input:
Requirement Analysis Procedure
GUI Guideline
SRS Template
SRS & Mock-up Review Checklist
Output:
Scope Document
Scenario Diagram(s)/System Flow Diagram(s)
SRS
Mock-up/Prototype
Requirement Traceability Matrix
|
|
| Size Estimation |
|
PM and PL calculates size after Requirement Analysis Phase which will be used to measure & track defined targets against Organizational Quality Objective like Productivity, Review Defect Density, Test Defect Density, Effort Variance, Schedule Variance, etc |
|
Input:
Estimation Procedure
Estimation Guideline
Estimation Rational
Output:
Estimation Sheet |
| Detail Design |
|
- This phase consists of converting client requirement to low level to developable modules by creating Module Integration Diagram & Functional Documents.
- PL prepares Module Integration Diagram and it’s reviewed by PM.
- Project Analyst prepares Functional Documents and it’s reviewed by Team Lead Analyst & PL.
- At the same time Test Cases are prepared by Software Tester on the bases of SRS, Mock-up/Prototype & Functional Documents which contains testing scenarios and it’s reviewed by Testing Team Lead.
- Team Lead Analyst & Testing Team Lead updates RTM for Functional Documents and Test Cases Name.
|
|
Input:
Detail Design Procedure
Testing Procedure
Functional Document Guideline
Testing Guideline
Functional Document & Test Case Review Checklist
Output:
Module Integration Diagram
Global Functional Document
Functional Document
Test CaseRequirement Traceability Matrix |
|
| System Design |
|
- This phase consists of defining the architecture/framework, entities, and database for a system to satisfy specified requirements.
- PL prepares System Architecture/Framework and it’s reviewed by PM.
- PL/TL prepares Entity Relationship Diagram using Visio and it’s reviewed by PM/PL.
- PL/TL creates Database using ERD & Visio.
- PL/TL updates RTM for Database/Schema Name & Tables and it is reviewed by PM/PL.
|
|
Input:
System Design Procedure
Framework Designing Guideline
Database Design Guideline
Entity Relationship Diagram /Database Review Checklist
Output:
System Architecture
/Framework
Entity Relationship Diagram
Database
Requirement Traceability Matrix |
|
| Coding & Unit Testing |
|
- In this phase, the client's requirement and designs are translated into Code.
- Each developer follows the coding standards and uses the Global Functional Document & Functional Documents for Development.
- Once development of the module is completed, Unit Testing is done by developer and result is logged into the Mantis.
- Functional Documents are converted in Unit Test Log.
- PL/TL performs Code Review periodically.
- TL & Developers updates RTM for Source Code File Name and Unit Test Logs.
|
|
Input:
Coding Procedure
Backend Coding Standard Frontend Coding Standard
Code Review Checklist
Unit Testing Checklist
Output:
Source Code
Unit Test Log
Unit Testing Bug Reporting and Tracking (Mantis)
Requirement Traceability Matrix |
|
| Testing |
|
- This phase is essential to test and measure the quality of an already developed application using approach of an End-User and it defines the quality by measuring correctness, completeness & security.
- GUI, UI & Validation Testing, Functional Testing, Integration Testing, System Testing, Performance Testing is perform by testing team by referring Flow Diagram(s), SRS, Mock-up & Test Cases.
- Test result is logged into the Mantis and Test Cases are converted in Test Log.
- Testing is performed on internal testing server, production server and hosting/live server.
- Testing Team Lead updates RTM for Test Logs.
|
|
Input:
Testing Procedure
Testing Guideline
Mantis Guideline
Testing Checklist
Output:
Test Log
Testing Bug Reporting and Tracking (Mantis)
Requirement Traceability Matrix |
|
| Release & Deployment |
|
- The source code labeling of the release is done with the help of Version Control software VSS/JEDI.
- Release can be Internal or External. Internal Release or Short Release is done on internal testing server or production server. External Release is done on hosting/live server.
- Release email is send to testing team for both internal and external release.
- In case of External release, a Release email is sent to both Testing team & Client along with the Release Note.
- PL/TL prepares Installation Manual and it’s reviewed by PM/PL, if it’s Client-Server application.
- Analysis team prepares User Manual/Help Manual if it is agreed by client in Business agreement. This User Manual is reviewed & approved by PL and Client both.
|
|
Input:
Build Creation Procedure
Source Code Labeling Guideline
User Manual/Help Manual Guideline
Output:
Release Note
Installation Manual
User Manual/Help Manual
Application/Software |
|
| Acceptance Testing |
|
- Acceptance testing is done by Client.
- Acceptance testing bugs is logged into the Mantis, resolved by developers, tested by testers and release to Client.
|
|
Input:
Project Management Procedure
Output:
Acceptance Testing Bugs Reporting and Tracking (Mantis) |
|
| Support & Maintenance |
|
- After getting Sign-Off email from Client, support phase gets started and PM, PL, MM/ME and project team give support to Client (This will be Free Support as per the Proposal).
- After support period gets over MM/ME communicates with Client for further Maintenance Support Agreement (This will be Paid Support).
- Type of Supports offered:
- Technical support
- Deployment support
- Training support
- Data entry support
|
|
Input:
Project Management Procedure
Output:
Project Closure Report |
|
| Size Estimation |
|
PM and PL calculates size after project closure which will be used to measure & track defined targets against Organizational Quality Objective like Productivity, Review Defect Density, Test Defect Density, Effort Variance, Schedule Variance, etc |
|
Input:
Estimation Procedure
Estimation Guideline
Estimation Rational
Output:
Estimation Sheet |
| Feasibility Study |
|
- Throughout the SDLC, feasibility study is conducted as per the requirement changes, if requirement is not seems to be feasible or difficult for implement.
- Appropriate actions are performed and knowledge transition is conducted throughout the organization.
|
|
Output:
Feasibility Study Form |
|
| Artifacts/Docs Review |
|
- All artifacts/documents (SRS, Mock-up, Functional Documents, Test Cases, etc) which are going to be generated in different phases of SDLC are reviewed by Peer and Supervisor.
- Few documents (Scope Document, SRS, Mock-up, etc) required to be reviewed by Client and approval is taken after review.
- Review defects are logged on Project Server-SharePoint, the concerned person resolves the defects and again Peer or Supervisory review take place.
- Review Checklists are utilized to perform reviews. The review evidence is generated by completing the checklist with appropriate Yes/No answers for each review point.
|
|
Input:
Review Procedure
Review Checklist
Review Defects Form (on Project Server) Guidelines
Output:
Review Defects |
|
| Project Progress Review |
|
- Project Progress Review is done weekly or fortnightly or periodically on basis of Project Size and Project Status Report is prepared.
- Monitor the following activities:
- Project & Milestone progress against planning
- Project Risks & Issues
- Stakeholders Involvement
- Accomplishments and Results against documented estimates and plans
- Critical Dependencies for the Project
- Plan and Monitor corrective & preventive actions.
- Collect Process & Application Measurement/Metrics Data like Schedule Variance, Effort Variance, Review Defect Density, Testing Defect Density, etc; analyze collected data and Process & Application performance.
- Quantitatively manage the project’s defined process to achieve the project’s established quality and process-performance objectives.
- Updating the Project Schedule based on the actual accomplishments and results.
|
|
Input:
Project Progress Reporting and Monitoring Procedure
Measurement - Data Collection and Analysis Procedure
Project Status Report Form
Output:
Project Status Report |
|
| Issue Management |
|
- The purpose of the Issue Management is to log issues with the resolution found for the same which can later help to resolve the issues in time and with precision if faced in future.
- Issues can be related to Standards, Environment, Clients, Stakeholders, System Admin, HR, Senior Management or any Technical Issue.
- This type of Issue Management can be a learning experience for the organization in managing the future projects and filling up the knowledge repository. This knowledge repository then can be used to conquer any of such issues if faced again.
|
|
Input:
Issue Management Guideline
Output:
Issues |
|
| SQA Reviews |
|
- The purpose of Software Quality Assurance is to ensure that the Quality & Information Security Process implementation is carried out at the organizational level for the functional departments as well as project level.
- SQA Review is done phase wise or periodically on basis of Project Size.
- This review is applicable to all the phases of project SDLC, to all the functional departments for process compliance.
|
|
Input:
SQA Procedure
SQA Review Checklist
Output:
SQA Review Report |
|
| Change Management |
|
- Change Management starts if client ask for any functional change which is increasing Scope of the Project. Change Management is applicable till project is not completed.
- As changes are introduced, it’s created on Project Server-SharePoint with Impact Analysis by PL; studied by PM & PL and decision is taken to either Accept or Reject those changes.
- PL estimates efforts & schedule variation.
- MM/ME perform cost variation and get confirmation for it from Client.
- The Change Request Number are incorporated in the RTM bedside the affected modules.
|
|
Input:
Change Management Procedure
Change Management Guideline
Output:
Change Management & Impact Analysis Logs |
|
| Configuration Management |
|
- The purpose of Configuration Management is to establish and maintain the integrity of work products using configuration identification, configuration control, and configuration status accounting and configuration audits.
- Configuration Management Audit is done phase wise or periodically on basis of Project Size.
|
|
Input:
Configuration Management Procedure
Configuration Management Guideline
Configuration Management Audit Checklist
Output:
Baseline-Configuration Status Report
Configuration Management Audit Report |
|
| Decision Analysis |
|
- The purpose of Decision Analysis is to analyze decisions using a formal evaluation process and it is a structured approach to evaluating identified alternative solutions against established criteria, which reduces the subjective nature of the decision and has a higher probability of selecting a solution that meets multiple demands of stakeholders.
- Decision Analysis can be use for selection among architectural or design alternatives, use of commercial-off-the-shelf components, supplier selection, engineering support environments or associated tools, test environments, logistics and production, make-or-buy decisions, and other critical decisions.
|
|
Input:
Decision Analysis and Resolution Procedure
Decision Analysis and Resolution Guideline
Output:
DAR Evaluation Recommendation Report
DAR Form |
|
| Senior Management Review |
|
- Senior Manager Review takes place weekly or fortnight or periodically on basis of Project Size.
- PM & PL inform Senior Management about project status, risks, change management, issues, etc.
|
|
Input:
SEPG Monthly Report
Project Status Report
Output:
Minutes of Meeting |
|
| Cause Analysis |
|
- Cause Analysis is done As and When Required/On Need Basis or on Project Closure.
- All review defects, testing defects & issues are maintained on Project Server-SharePoint and root cause is analyzed and corrective and preventive actions are conducted.
- The analysis reports are spread across organization level for appropriate knowledge transition.
|
|
Input:
Project Management Procedure
Output:
Cause Analysis & Resolution Report |
