In Our career ladder, we all must have seen much type of projects; based on my learning and knowledge I have segregated them in three different types -
1.) Complete Projects - Projects where Development, Testing, and Support is being done by one organization only.
2.) Pure Testing Projects - Project where Development has been done by some other organization and Testing has been given to some other organization.
3.) Support Projects - Projects where Development and Testing has been done by some other organization but after release, support is being given to some other organization.
We all must agree upon that the type of business is different in above stated project so we need to define different type of processes for each and every type of project so that they can be completed successfully.
Lets Take them one by one and see what and how we can do differently -
1.) Complete Projects
The process defines how the projects of type Complete development are executed. Various activities from requirements scoping till acceptance by customer for these type of Projects are dealt as below –
Inputs / Entry Criteria
| S. No | Input / Entry Criteria |
| 1 | Project trigger with request for study |
Process Description
| Phase | Entry Criteria | Task | Exit Criteria |
| Pre-Initiation | Request From Customer | An assigned resource(s) conducts a study of the requirement and that may involve a customer site visit, discussions with customer, system study at site etc. He may seek help of Sales or any other senior management personnel for any feasibility checks. This resource(s) will work with the BDM to prepare a proposal along with an initial effort estimation and schedule to go with the proposal. This proposal is presented to the client by the BDM and the BDM works with the client to get the approval on the same. If required, the BDM will seek the help of the individual who created the proposal or the Senior management team for any help. | Proposal/SOW. |
| Initiation | Project Approval by mail Proposal / SOW | Project initiation setup Resource Allocation Kick Off | Minutes of Kick off meeting Kick Of Meeting Presentation Project Initiation Document (PID) |
| Planning | Kick Off Meeting Presentation PID Proposal | Plan the project in detail Resource Planning Infrastructure planning | Approved Project Management Plan document Schedule (mpp) TSD |
| Test Planning | Base Documents from Client (BRD, HLDD etc..) TSD Schedule | Prepare the Test scenarios Expand each Test Scenario into various Test Plans Expand each Test Plan into Test Scripts Update Requirements Traceability Matrix | Signed off Test Scenario document (Template as mentioned in TSD), Signed off Test Plan Document v.v Signed off Test Scripts Document v.v Updated Requirements Traceability Matrix |
| Automation Planning | Base Documents from Client (BRD, HLDD etc..) TSD Schedule | Record identified Test scripts in Automated test tool identified in Test Strategy Document Customize / Parameterize them as appropriate | Signed off Automated Test scripts |
| Test Execution | Schedule TSD Signed off Test Scenario Document Signed off Test Plan Signed off Test Scripts Document | Execute test Scripts as planned in Test Strategy Document, records defects in the Defect Report. Repeat above step for number of rounds as planned in the Test Strategy Document Regression testing will be done on a need basis | Defect Reports |
| Release | TSD Defect Reports | Consolidation of defects and preparing the final defect report. Release audit is done prior to the release and all audit issues are tracked to closure Release is approved by PM/PD after verification of release test and audit issues. | Release Notes Release Audit checklists Final Defect Report |
| Closure | Project Management Plan document TSD | Records findings of testing, including final exit criteria, conditional sign-off etc. | Project Metrics Report Final Sign-Off Project Closure Note. |
Above shall be the overall flow of activities in the Pure Testing projects. There are some common activities and elements to all the activities:
a) Supplemental to this process sheet, individual guidelines are available for testing, configuration management and build. These together govern these activities in projects.
b) PMPD outlines the List of work products and List of Quality records applicable for the product.
c) All work products shall be reviewed and audited. Reviews concentrate on the content of the work products and provide the value addition. Review issues are recorded in Defect reports and tracked to closure. Audits concentrate on adherence and conformance to the defined standards, guidelines and formats. Work product audit findings are done as per the WPA checklists for the work product and findings are recorded in Work product audit report. Reviewers and Work product auditors are identified along with the activity in the schedule and are conducted as per the schedule. Work product auditors are generally a person inside or outside the project other than the author and they are trained in performing the work product audits. Reviewers are mostly peers or managers. Work product audit findings are tracked to closure before the work product passes to the next stage of consumption.
d) Throughout the engineering life cycle, there would be some critical decisions and they pass through the Decision Analysis process and DAR sheet is maintained to record all critical decisions in the project, alternate solutions taken and the final decision. This is described in the DAR process sheet.
e) Project tracking and monitoring is done as per Project Management Process and Project quantitative management is done as per Measurement process. Associated records are maintained as per the process for Pure Testing Projects.
Outputs / Exit Criteria
| S. No | Outputs / Exit Criteria |
| 1 | Proposal/ Statement of Work (as part of Pre-initiation phase) |
| 2 | PID |
| 3 | PMPD /Schedule |
| 4 | TSD with test plan, scenarios, scripts |
| 5 | Quality Records like Project initiation document, Weekly Activity Reports, Timesheets, Project Metrics Reports, Project Analysis Reports, Defect Reports, WPA Reports, WPA Checklists, Change Track sheets, DAR reports, CAR reports, Project Closure Note |
Key Deliverables and Relevant Stakeholders
| S. No | Deliverable | Author | Reviewer | Stakeholders |
| 1 | Proposal / Statement of Work | Marketing Manager / Executive | Project Director Senior Management Customer | Customer Marketing Manager Project Director Senior Management |
| 2 | Project Management Plan Document (PMPD) | Project Manager | Project Director | Project Director Project Manager Project Team (DEV, Test, Quality Facilitators) |
| 3 | Schedule | Project Manager | Project Director | Project Director Project Manager Project Team (DEV, Test, Quality Facilitators) Senior Management Customer |
| 4 | BRD | Customer | Project Manager Project Team (More for understanding perspective to test) | Business Analyst Project Manager Project Director Customer Project Team |
| 5 | TSD | Project Team | Project Manager Project Director | Project Team Test Team |
2.) Pure Testing Projects
The process defines how the projects of type pure testing are executed. This type of projects has their scope restricted to testing of customer given applications and products. Various activities from requirements scoping until acceptance by customer for these types of Projects are dealt as below –
Inputs / Entry Criteria
| S. No | Input / Entry Criteria |
| 1 | Project trigger with request for testing |
Process Description
| Phase | Entry Criteria | Task | Exit Criteria | |
| Pre-Initiation | Request From Customer | An assigned resource(s) conducts a study of the requirement and that may involve a customer site visit, discussions with customer, system study at site etc. He may seek help of Sales or any other senior management personnel for any feasibility checks. This resource(s) will work with the BDM to prepare a proposal along with an initial effort estimation and schedule to go with the proposal. This proposal is presented to the client by the BDM and the BDM works with the client to get the approval on the same. If required, the BDM will seek the help of the individual who created the proposal or the Senior management team for any help. | Proposal/SOW. | |
| Initiation | Project Approval by mail Proposal / SOW | Project initiation setup Resource Allocation Kick Off | Minutes of Kick off meeting Kick Of Meeting Presentation Project Initiation Document (PID) | |
| Planning | Kick Off Meeting Presentation PID Proposal | Plan the project in detail Resource Planning Infrastructure planning | Approved Project Management Plan document Schedule (mpp) TSD | |
| Test Planning | Base Documents from Client (BRD, HLDD etc..) TSD Schedule | Prepare the Test scenarios Expand each Test Scenario into various Test Plans Expand each Test Plan into Test Scripts Update Requirements Traceability Matrix | Signed off Test Scenario document (Template as mentioned in TSD), Signed off Test Plan Document v.v Signed off Test Scripts Document v.v Updated Requirements Traceability Matrix |
|
| Automation Planning | Base Documents from Client (BRD, HLDD etc..) TSD Schedule | Record identified Test scripts in Automated test tool identified in Test Strategy Document Customize / Parameterize them as appropriate | Signed off Automated Test scripts |
|
| Test Execution | Schedule TSD Signed off Test Scenario Document Signed off Test Plan Signed off Test Scripts Document | Execute test Scripts as planned in Test Strategy Document, records defects in the Defect Report. Repeat above step for number of rounds as planned in the Test Strategy Document Regression testing will be done on a need basis | Defect Reports |
|
| Release | TSD Defect Reports | Consolidation of defects and preparing the final defect report. Release audit is done prior to the release and all audit issues are tracked to closure Release is approved by PM/PD after verification of release test and audit issues. | Release Notes Release Audit checklists Final Defect Report |
|
| Closure | Project Management Plan document TSD | Records findings of testing, including final exit criteria, conditional sign-off etc. | Project Metrics Report Final Sign-Off Project Closure Note | |
Above shall be the overall flow of activities in the Pure Testing projects. There are some common activities and elements to all the activities:
a) Supplemental to this process sheet, individual guidelines are available for testing, configuration management and build. These together govern these activities in projects.
b) PMPD outlines the List of work products and List of Quality records applicable for the product.
c) All work products shall be reviewed and audited. Reviews concentrate on the content of the work products and provide the value addition. Review issues are recorded in Defect reports and tracked to closure. Audits concentrate on adherence and conformance to the defined standards, guidelines and formats. Work product audit findings are done as per the WPA checklists for the work product and findings are recorded in Work product audit report. Reviewers and Work product auditors are identified along with the activity in the schedule and are conducted as per the schedule. Work product auditors are generally a person inside or outside the project other than the author and they are trained in performing the work product audits. Reviewers are mostly peers or managers. Work product audit findings are tracked to closure before the work product passes to the next stage of consumption.
d) Throughout the engineering life cycle, there would be some critical decisions and they pass through the Decision Analysis process and DAR sheet is maintained to record all critical decisions in the project, alternate solutions taken and the final decision. This is described in the DAR process sheet.
e) Project tracking and monitoring is done as per Project Management Process and Project quantitative management is done as per Measurement process. Associated records are maintained as per the process for Pure Testing Projects.
| S. No | Outputs / Exit Criteria |
| 1 | Proposal/ Statement of Work (as part of Pre-initiation phase) |
| 2 | PID |
| 3 | PMPD /Schedule |
| 4 | TSD with test plan, scenarios, scripts |
| 5 | Quality Records like Project initiation document, Weekly Activity Reports, Timesheets, Project Metrics Reports, Project Analysis Reports, Defect Reports, WPA Reports, WPA Checklists, Change Track sheets, DAR reports, CAR reports, Project Closure Note |
Key Deliverables and Relevant Stakeholders
| S. No | Deliverable | Author | Reviewer | Stakeholders |
| ||||
| 1 | Proposal / Statement of Work | Marketing Manager / Executive | Project Director Senior Management Customer | Customer Marketing Manager Project Director Senior Management |
| ||||
| 2 | Project Management Plan Document (PMPD) | Project Manager | Project Director | Project Director Project Manager Project Team (DEV, Test, Quality Facilitators) |
| ||||
| 3 | Schedule | Project Manager | Project Director | Project Director Project Manager Project Team (DEV, Test, Quality Facilitators) Senior Management Customer |
| ||||
| 4 | BRD | Customer | Project Manager Project Team (More for understanding perspective to test) | Business Analyst Project Manager Project Director Customer Project Team | |||||
| 5 | TSD | Project Team | Project Manager Project Director | Project Team Test Team | |||||
3.) Support Projects
The process defines how the projects of type Support are executed. Support projects have their scope restricted to bug fixation and enhancements given by client. Various activities from requirements scoping till acceptance by customer for these type of Projects are dealt as below -
Inputs / Entry Criteria
| S. No | Input / Entry Criteria |
| 1 | Project trigger with request for Maintenance and/or Production Support |
Process Description
| Phase | Entry Criteria | Task | Exit Criteria |
| |||||
| Pre-Initiation | Request From Customer | Study the application being considered for support. Most likely, resource with required skills will be available as the application will have been developed by Company | Effort/resource estimation Establish / Identify base documents |
| |||||
| Client Study Estimation | SOW and/or Proposal | Reviewed and approved SOW / Proposal |
| ||||||
| Initiation | Project Approval by mail | Kick Off | Minutes of Kick off meeting Kick Of Meeting Presentation Project Initiation Document (PID) |
| |||||
| Project Management Planning | Client Study Kick Off Meeting Presentation PID | Plan Key Elements | Resource Planning Infrastructure Setup Project Conditioning |
| |||||
| Elements of Plan | Project Management Plan / Schedule | Approved Project Management Plan Review / WPA Checklists and Reports |
| ||||||
| CR Receipt (bug fixes, modifications, enhancement) | Project Management Plan Base Documents | Register CR | Acknowledgement to customer |
| |||||
| Assessment | Project Management Plan Base Documents | Request additional information if necessary Analyze CR if information is sufficient Analyze CR if it requires additional effort | Some requests may require additional information to arrive at a plan for action. Request sent to the customer for additional information Some may be duplicates of requests already received and completed from another customer. These requests will be closed after providing the necessary explanation to the customer. Some requests for modifications / enhancements may require an effort estimate to be provided which will have to be approved by the customer for work to start. Support Maintenance Log shall be used for bugs and small enhancements. If enhancement is a major enhancement, then, IAD is prepared and linked to the Maintenance Support Log (or) |
| |||||
| Development | Project Management Plan Base Documents Customer input | Start development of the bug/enhancement. Incorporate as patch which can be delivered to customer | Program Patch | ||||||
| Testing | Project Management Plan Base Documents Program Patch | Create Test scripts to test the CR Deploy patch in customer clone environment and execute Test scripts. | Defect Log Verified Program Patch | ||||||
| Release | Project Management Plan Base Documents Verified Program Patch | Prepare Release Note for Patch Dispatch Patch and Release note to Customer for UAT Record results of UAT Release audit is done prior to the release and all audit issues are tracked to closure Release is approved by PM/PD after verification of release test and audit issues. | User Accepted Patch Release Note Release Audit Checklists | ||||||
| Patch Closure | Project Management Plan Base Documents | Close CR in | Closure status to Customer for Patch | ||||||
| Project Closure | Project Management Plan TSD Final Closure of the project out of Support mode (* typically when product is withdrawn from production or closure of contract) | Prepare Closure note, Analysis report, metrics as on date Archive defects and artifacts done at Company end | Project Closure Note Project Analysis Report | ||||||
a) Supplemental to this process sheet, individual guidelines are available for requirements, design, coding, testing, configuration management and build. These together govern these activities in projects.
b) PMPD outlines the List of work products and List of Quality records applicable for the product.
c) All work products shall be reviewed and audited. Reviews concentrate on the content of the work products and provide the value addition. Review issues are recorded in Defect reports and tracked to closure. Audits concentrate on adherence and conformance to the defined standards, guidelines and formats. Work product audit findings are done as per the WPA checklists for the work product and findings are recorded in Work product audit report. Reviewers and Work product auditors are identified along with the activity in the schedule and are conducted as per the schedule. Work product auditors are generally a person inside or outside the project other than the author and they are trained in performing the work product audits. Reviewers are mostly peers or managers. Work product audit findings are tracked to closure before the work product passes to the next stage of consumption.
d) Throughout the engineering life cycle, there would be some critical decisions and they pass through the Decision Analysis process and DAR sheet is maintained to record all critical decisions in the project, alternate solutions taken and the final decision. This is described in the DAR process sheet.
e) Project tracking and monitoring is done as per Project Management Process and Project quantitative management is done as per Measurement process. Associated records are maintained as per the process for Support Projects.
Outputs / Exit Criteria
| S. No | Outputs / Exit Criteria |
| 1 | Proposal/ Statement of Work (as part of Pre-initiation phase) |
| 2 | PID |
| 3 | PMPD /Schedule |
| 4 | Impact analysis and design document (as appropriate) |
| 5 | Quality Records like Project initiation document, Weekly Activity Reports, Timesheets, Project Metrics Reports, Project Analysis Reports, Defect Reports, WPA Reports, WPA Checklists, Change Track sheets, DAR reports, CAR reports, Project Closure Note |
| S. No | Deliverable | Author | Reviewer | Stakeholders |
| 1 | Proposal / Statement of Work | Marketing Manager / Executive | Project Director Senior Management Customer | Customer Marketing Manager Project Director Senior Management |
| 2 | Project Management Plan Document (PMPD) | Project Manager | Project Director | Project Director Project Manager Project Team (DEV, Test, Quality Facilitators) |
| 3 | TSD | Project Team | Project Manager Project Director | Project Team Test Team |
| 4 | Impact Analysis and Design Document (IAD) | Project Lead | Project Manager | Project Team Test Team |
No comments:
Post a Comment