The document outlines two project governance models for a project between a vendor and customer. Model I describes the vendor taking primary responsibility for overall governance, requirements gathering, status reporting, and delivery management. Model II describes the customer taking primary responsibility for governance, receiving requirements and schedules from the vendor, coordinating status calls, and overseeing delivery management. Both models specify the responsibilities of the vendor and customer project teams.
2. Project Governance model: I
Vendor Customer
Requirement gathering,
Questionnaire, Freeze scope,
Project Cost and scheduling, Status
reporting
Vendor
Management
Proposal, SOW,
Lead
Overall Project
Governance
Freeze scope
Project Cost and scheduling, R.I,
preparing contingency & mitigation
Tech Team plans, Status reporting, Schedule and Tech Team
effort variation monitoring
CGS Coordination calls Client
3. Cont …
Prime responsibility: CGS
– Overall governance of Project teams happen from CGS
– Project teams(both & CGS) and customer interface from CGS
– Internal CGS and work coordination and status reporting
– Overall project delivery management by CGS
4. CGS DELIVERY RESPONSIBILITIES
Requirement gathering
Prepare questionnaire
Freeze scope
Project Cost and scheduling
Design and development kickoff
Risk Identification, preparing contingency & mitigation plans and tracking
Status reporting
Vendor management
Schedule and effort variation monitoring
Coordination calls
Overall project Governance
5. Reports Delivered From CGS:
Scrum Reporting -Daily
– Dashboard report
– Sprint change report
– Product burndown report
– Backlog monitoring
Weekly status reporting:
– Activities Planned Vs Completed
– Activities planned for next week
– Issues and concerns
– Delivery milestones and status
– Risk and challenges
6. Cont …
Note:
1) 10 % of project effort will be charged as Project Management effort for
projects below 500 hours or schedule less than 4 weeks
2) 8 % of project effort will be charged as Project Management effort for
projects above 500 hours or schedule more than 4 weeks
7. Project Governance Model: II
Customer Vendor
Receive project schedule from
Design and development kickoff,
Proposal, SOW,
Lead
Overall Project
Governance
Understand requirement, Prepare questionnaire
and estimates, Receive project schedule from ,
Design and development kickoff
Tech Team Risk Identification alert , Status reporting
Tech Team
CGS Vendor coordination, Attend project status calls Client
8. Cont …
Prime responsibility:
– Overall governance of Project teams happen from Client end
– Project teams(both & CGS) and customer interface from Client end
– Internal CGS and work coordination
– Overall project delivery management by Client end
9. CGS Delivery Responsibilities
Understand requirement, Prepare questionnaire and estimates
Receive project schedule from Client end
Design and development kickoff
Risk Identification alert
Status reporting
Vendor coordination
Attend project status calls
10. Reporting Model
• Daily work completion, plan Vs actual. – Stand up call with Client end.
• Weekly status reporting: Client end
– Activities Planned Vs Completed
– Activities planned for next week
– Issues and concerns
– Delivery milestones and status
– Risk and challenges
Note:
Coordination & status reporting is CGS responsibility.
No additional cost for project Management.
11. CONSTIENT GLOBAL SOLUTIONS INC.
USA
2610 Wedding ton Rdg Ne I Marietta I GA 30068
11574 Broadview Way I UT 84092
INDIA
ALTIUS I Level 2 I Olympia Technology Park I Guindy I Chennai I TN I IND 600 032
UAE
Al Maqta Oil Field Services I Post box:36864 I Abu Dhabi I UAE
Technology Center:
Holy Cross Church Premises | 76, 1st Floor | South Boag road | T.Nagar | Chennai | TN | IND 600 017
Email : kishore@constient.com
Skype: kishoresp