Star Knowledge Project Framework & Governance

Purpose

Value Proposition

Pre-Sales

Project Governance

Project Management

© Star Knowledge Technology Alliance Team, LLC – All Rights Reserved 2

The purpose of this Customer Briefing Profile is to provide current and future Star
Knowledge customers with an understanding of key presales and project activities and
processes:

Value Proposition

Presales

Project Governance

Project Management


Star Knowledge objectives focus on the professional management of customer projects
with a ‘quality-first attitude.’ Key areas of focus include:

Technical, PM and QM Resources

Software Development & Testing

Deliverable Quality

Project Budget

Project Timeframes

Risks, Problems & Uncertainties

Scope and Approach Changes

Status Reporting


The primary Star Knowledge goal is to successfully deliver each customer project by:

Embedding quality into every project’s fabric

Providing proactive communications

Following industry standards and best practices

Adhering to agreed timeframes

Concluding on-budget (hours and dollars)

Meeting agreed milestones

Matching 100% agreed customer requirements

Developing zero defect software


Decreased software development expense

Shorter development times

No budget overruns

Higher quality software

Increased software reliability

Enhanced employee productivity

Improved worker morale and less stress


Statement Master
Understand Project
Proposal of Work Services
& Agree Sizing
(SOW) Agreement

Decision Point


Prepare Project Information Document
(PID) to identify prospect (customer)
software development requirements
Conduct Q&A and Clarification Session
to corroborate understanding of:
Software development requirements

Business activities, processes and overall
context

Technical environment

Out-of-scope areas and restraints

Budget considerations
Agree to conduct project sizing


Carry out software development sizing
exercise with below deliverables:
Technical Approach

Work Effort

Elapsed Time

Assumptions
Corroborate, change as required, and
baseline sizing exercise
Agree to create proposal


Prepare proposal for software
development services based on sizing
baseline including:
Understanding of Customer Request &
Requirements

Current Technical Environment

Proposed Technical Approach

Proposed Scope of Work

Project Organization

Financial Considerations & Timing

Consultant Professional Profiles


Prepare Statement of Work (or Work
Order) following:
New customer approval of proposal

Current customer request for additional
services under exiting MSA
SOW Includes:
Agreed Project Scope

Deliverables / Milestones

High Level Work Plan

Project Governance

Information Requirements

Assumptions


Adapt Master Services Agreement
(MSA) to individual customer including:
Description of Services and Deliverables

Service Levels and Timetable

Compensation & Payment

Term of Agreement

Ownership & Property Rights

Indemnity Liability and Disclaimers

Confidentiality and Non Disclosure

Warranty

General Provisions

Schedule for Work Orders


Project Project Quality Status User
Management Management Reporting Acceptance
Management
Office (PMO)

* Based on: Decision Point
PMI - PMBOK


Star Knowledge Project Management
Office (PMO) objectives:

Oversight of customer software
development projects

Provide independent project quality
assurance

Develop and mainatin PM & QM
standards, methodology, tools and
best practices
Project Management Office (PMO)
Standards & Plan
(v1.2 – 022212)


Star Knowledge Project Management
objectives:
Prepare and maintain customer Project
Plan for project life

Ensure project approach and environment
is appropriate to customer’s business and
technical requirements

Manage customer deliverables and UAT

Supervise project control processes: risk,
Project Management problems, and change orders
Standards & Plan
(v1.1 – 022210) Create and review project status reports
with stakeholders throughout project life


Star Knowledge Quality Management
objectives:
Define “quality” in clear, measurable terms
for each customer project

Ensure project is in alignment with agreed
quality standards

Monitor software code to ensure zero
defect deliverables

Identify and eliminate costly and non-
Quality Management productive re-work
Standards & Plan
(v1.1 – 022210)


Star Knowledge Status Reporting
objectives:

Prepare Weekly Status Report with:
Project Status & Snapshot

Project Tasks Outstanding

Project Risk Register

Project Problem Register

Project Change Order Register

Planned Project Tasks – Next Week
Status Reporting
Standards & Plan
Conduct Weekly Status Meeting
(v1.1 – 022210)
Conduct Ad-Hoc Meetings, as
Required


Star Knowledge User Acceptance
Testing (UAT) objectives:
Create Software Testing Criteria and Plan

Create UAT Test Scripts

Conduct UAT

User Acceptance Testing (UAT)
Standards & Plan
(v1.1 – 022210)


Initiate Plan Execute Monitor Close-Out

* Based on:
PMI - PMBOK
Decision Point


Key customer supported activities in
this phase include:
Agree business and/or technical problem
or opportunity

Understand business and technical
environments and context

Confirm scope of development

Agree technical approach

Initiate Size software development work effort,
fees, and timeline

Create Proposal, Statement of Work (or
NOTE: This Phase incorporates all prospect / Work Order) and MSA
customer activities outlined in Presales section


this phase include:
Set-up technical environment: Star
Knowledge and Customer Site

Identify and assign PM, QM and technical
resources

Create Project Plan (Aligned to SOW or
Work Order)

Conduct Kick-off Meeting
Plan
Agree PM and QM processes and controls

Conduct Transfer of Information


Key customer supported activities in this
phase include:
Create technical specifications

Create test criteria and test scripts

Develop and test software

Conduct User Agreement Tests (UAT)

Obtain customer sign-off on approved
deliverables

Execute Create end user and system admin
operations manuals

Create and conduct end user and system
admin training sessions


this phase include:
Create Weekly Status Reports

Conduct Weekly Status Meetings

Conduct agreed QM tests

Identify and record project problems in
project problem register

Identify and record risk problems in project

Monitor risk register

Complete Project Change Order for
changes to agreed project plan


this phase include:
Obtain customer sign-off on Project
Closure Certificate

Conduct Lessons Learned Session

Return all customer documentation and
files as stipulated in MSA

Close-Out


Star Knowledge Project Framework & Governance

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (20)

Similar to Star Knowledge Project Framework & Governance

Similar to Star Knowledge Project Framework & Governance (20)