Project Execution Process
Project Execution Process
Version 1.1
2-Oct-2013
Prepared by: Suresh Thiagarajan
Startrun Training Academy
Revision History
Version
Number
1.0
1.1
Version-1.1
Description of changes
Initial version
Added POC to the process flow
2-Oct-2013
Confidential
Status
Date of
approval
Approved
Approved
28-Jun-2013
2-Oct-2013
1
Project Execution Process
Purpose: The Project Execution Process defines the methodology that is used to structure, plan, and control
the process of developing an academic projects in an educational institution.
Objective: The process facilitates consistent, high quality development and provides ‘virtual industry experience’
for students that are executing the projects.
Scope: This process is intended to be used by the students of engineering colleges.
Roles and Responsibilities: of personnel involved in the execution of the projects are listed in Table 1.
Role
Responsibilities
Project Guide
i.
ii.
iii.
iv.
v.
Establish norms for selection of projects
Review and approve a project idea
Review and approve the outputs of the project at different stages
Evaluate the completed projects
Liaise with the customer of the project (if applicable)
Project Leader
i.
ii.
iii.
iv.
v.
vi.
Primary contact of the project
Liaise with customer (if applicable)
Responsible for gathering requirements
Develops the project plan
Manages the project as per plan and resolves the issues
Liaises with Project Guide
Development
Leader
i.
ii.
iii.
Understands and analyzes project requirements and translates it into project
deliverables including design solutions
Works closely with other team members to build the final project deliverable
Fixes the defects found during testing of the deliverable
Test Leader
i.
ii.
iii.
iv.
Prepares test cases
Sets up test environment
Runs test cases and creates test reports
Manages defect tracking
Configuration
Leader
i.
ii.
iii.
iv.
Sets up a Configuration Management (CM) tool
Ensures the project team follows the configuration management activities
Ensures that the final delivery of the project is done (to the customer if applicable)
Ensures that Project Execution Process is followed
Table 1: Roles and Responsibilities
Convention to be followed in the project execution:
All the team members will be involved in all process steps to be followed for the project execution. However, the
respective Leaders will own the key areas.
Eg. Project Leader will own their responsibilities, while carrying out requirements analysis, design, development,
testing also. For areas other than project management, Project Leader will be answerable to the respective
leaders of requirements analysis, design, development and testing. Same rule applies to all other leaders also.
Version-1.1
2-Oct-2013
Confidential
2
Project Execution Process
The project execution life cycle is depicted in Figure – 1:


Project selection norms established
List of probable project ideas (if any)
1.
Project Guide
Project Leader
If not feasible, modify scope.
2.
3. Project Leader
Project Leader
Form the project team.
Approve the project idea
selected by the project team
Prepare the project plan
and track it during project
execution
Gather / update
requirements to realize
the project idea.
Refer Note 1
Refer Note 2
Refer Note 3
Prepare
POC and
check for
feasibility?
Feasible
4. Development Leader
7.
6.
Test Leader
Execute the test cases,
document the results and
tracks the defects found
Test Leader
5.
Prepare / Update test cases
and sets up testing
environment
Development Leader
Refer Note 4
Refer Note 5
Refer Note 6
Refer Note 7
8.
No
Defects
found in
testing?
Develop / update design
solution of the project
Develop / update the final
project deliverable
Configuration Leader
9.
Deliver the final deliverable of
the project.
Configuration Leader
Prepare the project report
Refer Note 9
Refer Note 8
Yes
Go to
3



Final Project Deliverable
Project Report
Project Workbook
Figure 1: Project Execution Life Cycle
Version-1.1
2-Oct-2013
Confidential
3
Project Execution Process
Note 1:

Project team consists of 3 or 4 students.

Project ideas shortlisted based on the norms set will be reviewed by the Project Team and Project
Guide and a suitable project idea is selected.

The project idea might be for a customer or an academic project

The project charter is prepared with the required details using Guidelines_Project Workbook -> Project
Charter.

Review the project charter with Project Guide. The Minutes of Meeting and action items (if any) raised
during the review are documented using Guidelines_Project Workbook -> MoM and -> Action items
Note 2:

The project plan contains the effort estimate and the schedule of tasks to be performed using
Guidelines_Project Workbook -> Project Plan

The Configuration Leader sets up the Configuration Management (CM) tool with required folders, user ids
and their access for these folders. Refer Guidelines_Project Workbook -> Configuration Management
Setup.

The CM tool shall be used by all team members of the project.

Review the project plan with Project Guide. The Minutes of Meeting and action items (if any) raised during
the review are documented using Guidelines_Project Workbook -> MoM and -> Action items
Note 3:




Collect the requirements (software, hardware, mechanical, electrical, functional, non functional) required
to realize the project idea. Document the requirements gathered using Guidelines_Project Workbook ->
Requirements Analysis.
Identify each of the requirements with a requirements ID. Eg. Software and UI requirements: SR001,
SR002…. And all other requirements: HW001, HW002 …..
Review the Requirements Analysis with Project Guide (and the customer, if applicable). The Minutes of
Meeting and action items (if any) raised during the review are documented using Guidelines_Project
Workbook -> MoM and -> Action items
Configuration Leader to conduct the checks upto this stage using Guidelines_Project Workbook ->
Delivery Document and track any ‘fail’ checks to closure.
Note 4:


Develop and document the detailed design features (of software, hardware, mechanical, electrical)
using Guidelines_Project Workbook.
Review the Design solution with Project Guide and Project Leader. The Minutes of Meeting and action
items (if any) raised during the review are documented using Guidelines_Project Workbook -> MoM and
-> Action items
Note 5:

Develop the final deliverable of the project (software, hardware, electrical or mechanical systems)
Note 6:

Test cases to test the final deliverable are written (software, hardware, electrical, mechanical systems)
and the test cases are written for all the requirements identified in the requirements analysis document.
Version-1.1
2-Oct-2013
Confidential
4
Project Execution Process
Note 7:
 Test cases are executed using the testing environment set up and the results are documented using
Guidelines_Project Workbook -> Test cases
 Defects found during testing are tracked to closure using the project team members
 Review the test cases and results with Project Guide and Project Leader. The Minutes of Meeting and
action items (if any) raised during the review are documented using Guidelines_Project Workbook ->
MoM and -> Action items
 Configuration Leader to conduct the checks upto this stage using Guidelines_Project Workbook ->
Delivery Document and track any ‘fail’ checks to closure.
Note 8:
 The final deliverable with supporting documents is submitted to the Project Guide (and to the customer,
if applicable).
 Wherever applicable, the customer feedback is addressed and an approval is obtained.
 A backup of the project with all the intermediate and final deliverables shall be created and archived.
Note 9:





The project report shall be reviewed by Project Guide.
Include the ‘requirements coverage’ metrics in the project report.
Use the Project report template, “Template_Project Report”.
Configuration Leader to conduct the checks upto this stage using Guidelines_Project Workbook ->
Delivery Document and track any ‘fail’ checks to closure.
Approved report shall also be archived.
Version-1.1
2-Oct-2013
Confidential
5
Project Execution Process
Definitions and acronyms:
Definition / Acronym
Description
CM
Configuration Management
MoM
Minutes Of Meeting
UI
User Interface
References and interfaces with other process:
Reference
Description
Guideline_Project WorkBook
Workbook to capture requirements, design, test
cases and defects;
Template_Project Report
Used for preparing the final project report
Metrics:
Metric
Requirements Coverage
Version-1.1
2-Oct-2013
Definition
Unit
Number of requirements tested &
passed / Number of requirements
agreed for development
Confidential
In percentage
6