Capgemini India. 2 Project Execution Process  Onsite team will gather the requirements from client and put them in Business Requirements specification.

Slides:



Advertisements
Similar presentations
Roadmap for Sourcing Decision Review Board (DRB)
Advertisements

Acceptance Testing.
INFO 638Lecture #81 Software Project Management Cycle plan and build INFO 638 Glenn Booker.
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
Effective Project Management: Traditional, Agile, Extreme
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
Copyright  Larry Dribin, Ph.D. SE470_EngFlows_v1.ppt SE470 EngFlows - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
Test Plan A document that indicates what testing will occur, how it will occur, and what resources will be necessary for it to occur. A test plan also.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Degree and Graduation Seminar Project Management Processes
Where Agile Business Meets Agile Development DSDM Offshore Steve Messenger Patrick Vermeij.
Project Requirements COP 4331 OO Processes for Software Development © Dr. David A. Workman School of EE and CS University of Central Florida March 22,
Condor Technology Solutions, Inc. Grace RFTS Application Extension Phase.
Software Testing Lifecycle Practice
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Test Organization and Management
Database testing Prepared by Saurabh sinha. Database testing mainly focus on: Data integrity test Data integrity test Stored procedures test Stored procedures.
1 Phase Implementation and Test Plan. Making your implementation plan First Steps  Consider your use case diagram and your prioritization of use cases.
Software Quality Assurance Lecture #4 By: Faraz Ahmed.
Software Testing Life Cycle
© Mahindra Satyam 2009 Defect Management and Prevention QMS Training.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
WFO Planning Tool RFC & FCT
Process Management  Identify and involve stakeholders  Find common vision and mission  Define roles and responsibilities  Monitor/evaluate team effectiveness.
Project Life cycles BTEC National.
Project Tracking and Monitoring QMS Training. 2 Objective To track and monitor the progress of the project and take appropriate corrective actions to.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
© Mahindra Satyam 2009 Configuration Management QMS Training.
Software Development Life Cycle (SDLC) Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.
MIS 7003 MBA Core Course in MIS Professor Akhilesh Bajaj The University of Tulsa Introduction to S/W Engineering © All slides in this presentation Akhilesh.
Chapter 2: Testing in Software Life Cycle MNN1063 System Testing and Evaluation.
IAEA International Atomic Energy Agency Methodology and Responsibilities for Periodic Safety Review for Research Reactors William Kennedy Research Reactor.
Requirements Engineering. Requirements engineering processes The processes used for RE vary widely depending on the application domain, the people involved.
Day 3 in the pmProject Management Project Management (PM) ADJUST.
WHAT IS USER ACCEPTANCE TEST? HOW IT IS DIFFERENT FROM SYSTEM TESTING?.
WebAuditor Training Kit. Introduction-WebAuditor  Process Automation tool for automating all internal quality audit activities.  Web based tool with.
FCT Refresher: Getting the Support You Need By: Lauren Stanisic.
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
Contact US: ID: Phone Number:
March 23, SPECIAL EDUCATION ACCOUNTABILITY REVIEWS.
Software Testing-STLC
© Mahindra Satyam 2009 Inspections and Reviews QMS Training.
Interset Support Overview March 2017
Software Configuration Management (SCM)
Software Verification and Validation
Dinesh Rawat , Software Test Manager
8.3 Control Quality The process of monitoring and recording results of executing quality activities to assess performance and recommend necessary change.
Inputs Outputs Tools and Techniques.
Different Types of Testing
V-Shaped SDLC Model Lecture-6.
Pega 9/14/2018 8:48 AM Definition of Done = ready for PO acceptance
SQA Role during Software Requirements Phase
Strategies For Software Test Documentation
Fundamental Test Process
Development Lifecycle
A summary of part 1 of Chapter 7 CEP 812 Kay Paff March 24, 1999
LESSON 01 Hands-on Training Execution
QA Reviews Lecture # 6.
Name of Project Manager Date
The Software Testing Life Cycle
Software Testing Lifecycle Practice
Project Management Techniques Project Management Life Cycle
Project Model Otto Husby Cimple AS.
Planning Services Meeting Client Communications
Project Name Here Kick-off Date
Presentation transcript:

Capgemini India

2 Project Execution Process  Onsite team will gather the requirements from client and put them in Business Requirements specification (BRS).  Onsite team will interact with offshore and decide the design and implementation strategy and together prepare Technical specification document (TSD).  BRS and TSD will be shared with offshore testing resource.  SRMS request will be raised by onsite. Offshore team will accept if timelines are agreeable. Otherwise offshore initiates negotiation with onsite on times lines to be agreed.  Testing resource will use the Requirements document and Technical specification document to prepare Test Cases and Test Reviews. This document includes Defect log where all the defects will be logged over the course of testing.

3  Test cases and Reviews will be shared with onsite and take inputs if we miss any thing. Once they agree Test Cases and Reviews are finalized.  Development team lead will allocate the resources and times lines for each phase of project in SRMS.  Development team at offshore will start doing development using BRS and TSD.  Over the course of development each deliverable will be monitored and reviewed by developers and team leads to check whether we are following the BRS and TSD.  Once development is done development team lead will update Tester and initiate the testing process. Development team will hand over the back end queries for data validation used as part of development. These will be used as base queries by tester and he will do changes as required by the test cases.

4  Tester will do the complete testing of deliverables. This includes back end data validation and front end presentation layer testing. Check list for all the deliverables is followed.  Tester will update the development team if any defects found and log the defects in defects log.  Development team will resolve defects and deliverables will be passed to tester again. This process will go till the deliverables pass test cases completely.  Once Testing is done deliverables will be passed for peer review by other team lead who will verify the requirements and deliverables. If defects found any will be logged in defect log and development iteration will happen till all the defects are fixed.  The deliveries will be sent to onsite for onsite review. Offshore team leads will do walk through to onsite on the deliverables.

5  Onsite will do the review and log defects if any found. This we are maintaining in a separate excel sheet.  After this deliverables will be passed to client IM review.  If defects found any at IM review will taken as immediate action items and development team will resolve the defects on priority basis. Defects are logged in defect log. These defects will be considered as post delivery defects.  Final delivery note will be sent to onsite on SRMS.  All the documents pertaining to project like BRS, TSD, Test cases and Test Reviews will be uploaded to Project Work Room (PWR).  Deliverables will be moved to production. If any defects found at the production will be considered as post production issues and addressed immediately.

6 Change Request process  Over the course of IM review if client needs any change to deliverables they will be considered as change requests.  Change request will be analyzed and times lines will be given based on the complexity of change.  Change request will follow the same process of development with respect to testing and review.