More Related Content
Similar to How to configure Change management flow Whizible SEM
Similar to How to configure Change management flow Whizible SEM (20)
How to configure Change management flow Whizible SEM
- 2. © Compulink Systems Ltd. All Rights Reserved. 2
Agenda
Basic Definitions
Conceptual Workflow
Configuration
Managing Change Requests
- 3. Basic Definitions
Change Request
A change requirement that is posted by any of the resources or the customer of a project is
known as a Change Request. A work around suggested by any project resource is known as
Internal Change Request and any work around suggested by the customer is known as
External Change Request.
Work Product
Work Product is a logical entity that is the constituent of the product of the project e.g. ASP
Page, DLL, etc.
Impact Analysis
Impact analysis is the process of identifying work-products that may be affected by
proposed changes. This requires a representation model that can formalize the knowledge
about the various dependencies between work-products.
Change Management
The Change Management provides the facility to document and track any changes made in
the project. The change may be internal (initiated within the Organization) or external
(change required by the Customer). The user can also upload documents against the Change
Request and conduct an Impact Analysis on the product.
© Compulink Systems Ltd. All Rights Reserved. 3
- 4. © Compulink Systems Ltd. All Rights Reserved. 4
Agenda
Basic Definitions
Conceptual Workflow
Configuration
Managing Change Requests
- 5. Conceptual Workflow
CONFIGURATION
PROJECTS
Define types of Impact Analysis
Identify Work Product Types
Post Change Requests
Carry out Impact Analysis for Change
Requests
Create Tasks for change request mapping
Upload requirement collaterals (documents)
© Compulink Systems Ltd. All Rights Reserved. 5
- 6. Configuration : Corporate Level
Define Impact Analysis Type
Define Work Product Types
© Compulink Systems Ltd. All Rights Reserved. 6
- 7. Define Impact Analysis Type
• The effects of
change requests
are evaluated and
analyzed by
carrying out Impact
Analysis for the
same.
• All such standard
types of Impact
Analysis are
captured in the
Impact master at
corporate level.
© Compulink Systems Ltd. All Rights Reserved. 7
- 8. Define Work Products
• Managing the change
is about correctly
identifying the work
products affected after
incorporating those
changes.
• Use Work Product
master to capture the
generic work products
that are usually the
constituent of the
projects across the
organization e.g. ASP
Page, SP, Trigger, View
etc.
© Compulink Systems Ltd. All Rights Reserved. 8
- 9. Managing Change Requests
Add Change Request
Edit Change Request
Carrying Out Impact Analysis
Identify Work Products Affected
Compute Modification Efforts
Creating Tasks
Upload Documents
Convert To Deliverable
Graphs
Resource Statistics
© Compulink Systems Ltd. All Rights Reserved. 9
- 10. Add Change Request
© Compulink Systems Ltd. All Rights Reserved. 10
• Any change
requests raised by
internal resources
or customer are
added under
Change Requests
feature.
- 11. Add Change Request
• Populate following required
details about change request:
Change Request: Enter subject
of change request.
Change Requestor: Name of the
person who raised the change.
Change Requested Date: The
date on which the change
request is posted.
Description: Details of changes
to be incorporated.
Benefits: Enter the resultant
benefits of the change.
Category: Select the origin of
the change request I.e. raised by
internal project resource,
(external) customer or other
source.
Change Status: Select the
present status of the change
request.
© Compulink Systems Ltd. All Rights Reserved. 11
- 12. Edit Change Request
• In the edit mode of
change request, few
more attributes appear
on the screen.
• The details about the
Approval or Rejection
of change requests are
captured.
• Some additional tabs
also appear on the
screen viz.
Impact Analysis,
Work Products
Affected
Tasks
Modification Efforts
Documents
© Compulink Systems Ltd. All Rights Reserved. 12
- 13. Carrying Out Impact Analysis
• For every change request,
Impact Analysis is carried out to
evaluate the impact of the
changes on the work products.
• The details about the same
can be captured under Impact
Analysis tab.
• Planned Start Date is the
planned date of change
implementation.
• Select the Change Size from
the drop down which is
populated with predefined
values.
• Mark the Regression Testing
Required(Y/N) checkbox to
indicate, if the testing should be
conducted to ensure that the
change has not affected the
existing functionality.
© Compulink Systems Ltd. All Rights Reserved. 13
- 14. Identify Work Products
• Work Products that will be
affected after incorporating
the changes can be added
under Work Products
Affected tab.
• On the Work Product
specification page, select the
Work Product Type.
• Select the type of Impact
Analysis from the Type drop
down.
• Specify the name of the
affected work product in the
Work Products Affected field.
• Specify the modifications
that will be made the affected
work product in the
Modification Details field.
© Compulink Systems Ltd. All Rights Reserved. 14
- 15. Modification Efforts
• Specify the phase wise
break up of estimated
efforts for modifications
under Modification
Efforts tab.
• Phase drop down is
populated with the
project phases
identified under
PROJECTS > Project
Management > Plan >
WBS > Phases.
© Compulink Systems Ltd. All Rights Reserved. 15
- 16. Create Tasks
• For incorporating the
changes, the
corresponding tasks
should be created for
the project resources
under Tasks tab.
• The same screen for
creation of Assigned
Tasks appears.
• Populate the required
required details for the
tasks.
© Compulink Systems Ltd. All Rights Reserved. 16
- 17. Upload Documents
• Any reference
documents for the
change requests can be
uploaded under
Documents tab.
• Map the Document
Category and Sub
Category to the uploaded
document.
• Use the Attach URL link
under the tab, to enclose
the URL of the reference
sites for the change
request.
© Compulink Systems Ltd. All Rights Reserved. 17
- 18. Convert To Deliverable
• The approved Change
Request can be used for
creating project deliverable
with the help of Convert To
Deliverable link.
• Deliverable creation appears.
• Select the Deliverable Type
from the drop down.
• Based on the selected
deliverable, the mandatory
fields configured for the
deliverable type appear on the
screen.
• By default, the Change
Request subject is mapped to
deliverable Title and the
description of Change Request
is mapped to its Description.
© Compulink Systems Ltd. All Rights Reserved. 18
- 19. © Compulink Systems Ltd. All Rights Reserved. 19
Graphs
• In the Graphs section following two
graphs are displayed…
Planned Tasks vs. Completed Tasks
Open Issues for Change Request
• Planned Tasks vs. Completed Tasks:
This bar graph displays the count of
planned tasks against the completed
tasks under the change request.
• Open Issues for Change Request:
This Pie graph displays the number of
issues that are open and to which the
selected change request is mapped.
- 20. Resource Statistics
• Under the Resource Details
section, you can view the
statistic with respect to the
task assignment under the
change request to the various
project resources.
© Compulink Systems Ltd. All Rights Reserved. 20