Purpose
The purpose of this procedure is to assess
the current organization from different perspectives.
Covered perspectives are:
·
structure
o
Organization
o
Department
·
process
o
Organization process
o
Department process
o
Automation level per process
o
Procedures evaluation
·
Methodologies
o
Engineering methodologies
o
Management methodologies
·
Tools
o
Planning
o
Engineering
o
Quality
·
Team evaluation
o
Technical Skills
o
Personal skills
o
Responsibilities according to skills
·
Products status
o
Business needs
o
Engineering methodology
·
Projects status
o
Backlog
o
To-Do
o
UI
o
Verify
o
Closes
Inputs
No |
Input |
Coming from/Output Of |
1.
|
CV |
Teams |
2.
|
TFS |
IT + Teams |
3.
|
Deployed
Solutions |
Development team |
4.
|
SRS |
Development Team |
5.
|
Plans |
PO and Scrum masters |
Activities
|
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
Standard Reference |
Weight |
||||||||
1.
|
Determine
Organization culture |
Process team |
|
|
|
|
|
|
||||||||
2.
|
Determine
both Organization and Department Structure. Used to
find: ·
missing positions ·
over allocated positions ·
Unutilized positions |
Process team |
|
|
|
|
|
|
||||||||
3.
|
Determine
overall process for evaluation ·
Organization process ·
Department process |
Process team |
|
|
|
|
|
|
||||||||
4.
|
Determine
Automation level per: ·
Process ·
Co-operation between processes |
Process team |
|
|
|
|
|
|
||||||||
5.
|
Determine
management Methodologies ·
Planning Tools ·
Reference point ·
Estimation technique ·
Estimation procedure ·
Follow-up phase ·
Retro's ·
Closure |
Process team |
|
|
|
|
|
|
||||||||
6.
|
Engineering
methodologies ·
Gathering Requirements techniques ·
Epics and user stories ·
Analysis models ·
Architecture models ·
Arch Patterns ·
Design patterns |
Process team |
|
|
|
|
|
|
||||||||
7.
|
Determine
used Tools for ·
Planning ·
Engineering ·
Testing ·
TPS ·
MIS ·
DSS ·
ES |
Process team |
|
|
|
|
|
|
||||||||
8.
|
Determine
Team skills ·
Technical Skills ·
Personal skills ·
Responsibilities according to skills |
Process team |
|
|
|
|
|
|
||||||||
9.
|
Determine
Products status ·
Business needs ·
Engineering methodology |
Process team |
|
|
|
|
|
|
||||||||
10. |
Determine
projects status ·
Backlog ·
To-Do ·
UI ·
Verify ·
Closes |
Process team |
|
|
|
|
|
|
||||||||
Outputs
No |
Output |
Going To/Input Of |
|
Innovative ideas |
|
|
Innovative architecture model |
|
|
Innovative Technologies |
|
02-Planning Procedure
Purpose
The
objective of this procedure is to establish a reasonable plan for performing
process improvement on the quality system. This will provide a strong
infrastructure for the quality system changes.
Inputs
No |
Criteria |
Exit Criteria Of |
1 |
Change requests |
Check for
Change Requests Bimonthly |
2 |
Daily startup
meetings |
|
3 |
Issues reviews |
|
4 |
Management
meetings |
|
5 |
Lessons learnt |
|
6 |
Task Management
Repo |
|
7 |
Bug Reports |
|
8 |
User Stories |
|
9 |
Architecture and
design models |
|
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
Standard Reference |
1. |
Create dashboard for
issues classified by status |
|
|
|
|
|
2. |
Analyze issues root
causes for each issue/type in order to set defensive model to prevent issues
as following: ·
Why we have removed issues and how to
prevent it ·
Why we have all these issues and how to
prevent the issue in the future ·
How to prevent the abuse of solution ·
How to prevent the misunderstanding of
solution ·
How the system gives users instructions
for usage. |
|
|
|
|
|
3. |
|
|
|
|
|
|
4. |
|
|
|
|
|
|
5. |
Analyze NC database and
PR defects in order to create change requests. |
SEPG |
NC database and PR defects |
CR Created |
|
|
6. |
Identify the scope and
goals |
SEPG |
All Procedure Inputs |
Identified Scope and Goals |
|
|
7. |
Determine assumptions,
risks and target projects. |
SEPG |
All Procedure Inputs |
Identified Assumptions and
Target Projects |
|
|
8. |
Define stakeholder for
each project |
SEPG |
Target Projects |
Stakeholder Identified |
|
|
9. |
Identify roles and
responsibilities. |
SEPG |
All Procedure Inputs |
Identified roles and
responsibilities |
|
|
10. |
Analyze and
Study the impact of the required changes. |
SEPG |
Impacted
CIs |
Impact
Studied |
|
|
11. |
Prioritize the
change requests |
SEPG |
Impacted
CIs and All Procedure Inputs |
Identified
Priority Level |
|
|
12. |
Set importance
criticality level on the change
requests |
SEPG |
Impacted
CIs and All Procedure Inputs |
Identified
Majority Level |
|
|
13. |
Estimate the
associated change in project effort and quality. |
SEPG |
Impacted
CIs and All Procedure Inputs |
Estimate
Change |
|
|
14. |
Evaluate the change to make the go/no-go
decision (approve/reject). |
SEPG |
Estimated
Change and Impacted CIs |
Approved/
Rejected Change Request |
|
|
15. |
Get Stakeholders approval |
Stakeholders |
Approved Change Request |
Approve changes on the project |
|
|
16. |
Define decision and escalation mechanisms |
SEPG |
Identified Organization and Structure |
Identified Mechanisms |
|
|
17. |
Take decision to apply following the QS changes in
the running projects. |
SEPG
and Stakeholders |
Impacted CIs Priority Level Majority Level |
Decision Taken |
|
|
18. |
Prepare or update the schedule for change request
tasks |
SEPG |
All outputs above |
Schedule Prepared |
|
|
19. |
Apply General Activities |
Process Related |
|
|
|
Outputs
No |
Output |
Going To/Input Of |
1 |
PI Plan |
PI_Execution_Procedure |
Metrics
·
Quality, cost, effort variance between old
and enhanced PI models.
03-Execution
Procedure
Purpose
The objective of this
procedure is to execute the change request in the process improvement planning
activities on the Quality System.
Inputs
No |
Input |
Coming from/Output Of |
1 |
Approved PI Plan |
PI_Planning_Procedure |
2 |
Approved Change Request |
PI_Planning_Procedure |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
Standard Reference |
Weight |
1. |
Record the CR
in the change log. |
SEPG |
Approved
Change Request |
Recorded
Change Request |
|
3 |
|
2. |
Implement the
change request according to the plan. |
SEPG |
Plan
for Implementing The Decision |
Implemented
CRs |
QS
templates and procedures |
|
3 |
3. |
Conduct PR and solve defects |
SEPG |
QS templates and
procedures |
Reviewed templates and
procedures |
|
|
3 |
4. |
Update Change
log by the change status |
SEPG |
Implemented
CRs |
Updated
Log |
|
3 |
|
5. |
Make a
presentation to all relevant stakeholders by these change requests. |
SEPG |
All
Procedure output |
Stakeholders
Notified |
Email |
|
|
6. |
Send these
changes to QAR in order to be considered in audits. |
SEPG |
All
Procedure output |
QARs
Notified |
Email |
|
3 |
7. |
Collect Metrics
and send it to QAM |
SEPG |
All
Procedure output |
Metrics
Collected |
|
|
3 |
8. |
Baseline
changes according to the pre-defined baselining
criteria. |
SEPG |
All
Procedure output |
Baseline
Taken |
|
|
3 |
Outputs
No |
Output |
Going To/Input Of |
1 |
Updated Quality System |
PI_Follow-up_Procedure |
04-Follow-Up
Procedure
Purpose
The
objective of this procedure is to ensure the closure of all change requests
that implemented in execution phase appeared in all affected projects or escalating
the to the top management to take the required and
suitable action.
Inputs
No |
Input |
Coming from/Output Of |
1 |
Approved Change Requests |
PI_Plan_Procedure |
2 |
Updated Quality System |
PI_Execution_Procedure |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
Standard Reference |
Weight |
1.
|
Implement the change requests. |
Author / Process Owner |
Approved Change Requests |
Implemented Change
Requests |
|
|
3 |
2.
|
Release new or revised
work product. |
Author / Process Owner |
Implemented Change
Requests |
Updated Work Product |
|
|
3 |
3.
|
Inform QAR about the
readiness to verify the implementation of the change requests. |
Author / Process Owner |
Corrected Work Product |
Readiness Notification E-Mail |
|
|
3 |
4.
|
Track the planned closure
dates for all change requests and follow-up for unresolved NCs. |
QAR |
Approved Audit Report |
Identified NCs to be
tracked |
|
|
3 |
5.
|
Schedule the follow-up
audit after the implementation of the corrective actions. |
QAR |
Identified NCs to be
tracked |
Scheduled Follow-up Audits |
|
|
|
6.
|
Audit on the corrective
actions implementation And report to SM |
Corrected Work Product |
Scheduled Follow-up Audits |
Identified Closed and
Opened NCs |
|
3 |
|
7.
|
Verify the
implementation of the change by reviewing the status of all impacted CIs. |
SEPG |
All
processes output |
Implementation
Verified |
|
3 |
|
8.
|
Escalate unresolved issues
according to the pre-defined escalation mechanism if necessary. |
SEPG |
Identified Opened NCs |
Escalation Reports |
|
3 |
|
9.
|
Prepare tracking report
to top management |
|
|
|
|
|
|
10. |
Apply General Activities |
SEPG |
|
|
|
|
Outputs
No |
Output |
Going To/Input Of |
1 |
Escalation Reports |
PI_Closure_Procedure |
2 |
Tracking Report |
PI_Closure_Procedure |
05-Closure Procedure
Purpose
The
purpose of the closure procedure is to ensure a graceful exit for the change
request, collect closure acceptance from SEPG, and record the experience gained
in practice in order to guide the enactment of other changes in the future.
Definitions
·
None
Entry Criteria (AND)
No |
Criteria |
Exit Criteria Of |
1 |
All Change Request was implemented. |
PI_Plan_Procedure |
2 |
Change Request was
escalated with decision not to implement the Change Request |
PI_Follow-up_Procedure |
Inputs
No |
Input |
Coming from/Output Of |
1 |
Approved Change Requests |
PI_Plan_Procedure |
2 |
Tracking Report |
PI_Follow-up_Procedure |
Activities
No |
Activity |
Responsible |
Input |
Output |
Temp/Solution |
Standard Reference |
Weight |
11. |
Close change if
the result of the CR verification is accepted. |
SEPG |
Verified
Change |
Closed
Change |
|
3 |
|
12. |
Identify
lessons learnt. |
SEPG |
All
Procedure Inputs |
Lessons Learnt |
|
|
3 |
13. |
Conduct meeting
to analyze process data to extract experience gained in current process
enactment. |
SEPG |
All
Procedure Inputs |
MOM |
|
|
3 |
14. |
Apply General Activities |
SEPG |
|
|
|
3 |
Outputs
No |
Output |
Going To/Input Of |
1 |
Approved Closed Change Requests |
None |
Exit Criteria
No |
Criteria |
Entry Criteria Of |
1 |
Approved Closed Change Requests |
None |
Metrics
These measures can be
useful to support the process enactment, or future enactments.
·
Actual versus planned time and effort
Subjects for Review
·
None
Records
·
None
Configurable Items
·
None