Change Management

1
Change Management
Requirements Engineering Project
Management Lecture 10

• Jerzy.Nawrocki_at_put.poznan.pl
• www.cs.put.poznan.pl/jnawrocki/require/

2
XPrince Roles and Changes
Project Manager
Changing requirements
Team dynamics
3
Agenda

• CMM and Change Management
• Requirements Management Practices
• Situational Leadership

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

4
Agenda

• CMM and Change Management
• Requirements Management Practices
• Situational Leadership

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

5
Software Configuration Item (SCI)

• SCI Information that is created as part of the
  software engineering process. R.Pressman
• Types of SCIs
• computer programs (source code or exec)
• documents (also requirem. specification)
• data (e.g. test cases)

?
6
Baseline IEEE 610-1990

• A specification or product that has been formally
  reviewed and agreed upon,
• that thereafter serves as the basis for
  further development, and
• that can be changed only through formal change
  control procedures.

7
Baseline or SCI?
Engineering
SCI
Change it!
8
Software Configuration Control Board (SCCB)

• Authorises
• the establishment of software baselines,
• the identification of configuration items,
• the creation of products from the baseline
  library.
• Represents the interests of the project manager
  and all groups affected by changes to baselines.
• Reviews and authorises changes.

SCCB
9
CMM Change Management

• Ac5. Change requests problem reports for all
  SCIs are
• initiated,
• recorded,
• reviewed,
• approved, and
• tracked
• according to a documented procedure.

Remove 2nd floor!
10
Change Control
Err
User
No
11
Change Control
Err
Developer
User
S.C. Manager
Yes
SCCB
12
Change request
Change request Change request number
............................ Sender
..................................................
....... Senders e-mail .........................
.................. Date .........................
..................................... Urgency
................. Importance .............. Desc
ription .........................................
........ .........................................
.............................. ...................
..................................................
..
Evaluator .......................................
.............. Evaluate by ........... Type
(in/external) .......
13
Change report
Change report Change request number
.......................... Evaluator
..................................................
. Evaluators e-mail ............................
......... Date ..................................
.......................... Urgency
................ Importance .............. Is
the change justifiable? ..........................
Main risk factors ..............................
......... Possible implementor
.............................. Change implement.
effort (expect) ......... Change evaluation
effort (actual) ............
14
Agenda

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

• CMM and Change Management
• Requirements Management Practices
• Situational Leadership

15
Requirements Management
The requirements document
Requirements elicitation
Reqs analysis negotiation
Describing requirements
System modelling
Requirements validation
Requirements management
RE for critical systems
16
Basic guidelines

• Uniquely identify each requirement

17
Basic guidelines

• Uniquely identify each requirement

Tag
18
Basic guidelines
Requirements Management Policy Goal Understand
the requirements Obligatory practices 1. Define
specialised terms using the template available at
www.cs.put.poznan...

• Uniquely identify each requirement
• Define policies for requirements management

19
Basic guidelines

• Uniquely identify each requirement
• Define policies for requirements management

• Define traceability policies

20
Traceability policy
Problems

• Traceability information
• Who is responsible

Visions
Requirements (FURPS)
Acceptance test cases
User documentation
Design
Code
21
Basic guidelines

• Uniquely identify each requirement
• Define policies for requirements management

• Define traceability policies
• Maintain a traceability manual

22
Intermediate guidelines

• Use a database to manage requirements
• Define change management policies
• Identify global system requirements

23
Advanced guidelines

• Identify volatile requirements
• Record rejected requirements

24
Change management styles
Disciplined (formal)
Agile (informal)
25
Agenda

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

• CMM and Change Management
• Requirements Management Practices
• Situational Leadership

26
Management Styles

• Democratic, people-oriented
• Autocratic, result-oriented

27
Effective Management

• Goal setting
• Praising
• Reprimanding

28
Goal Setting
SMART
Specific and measurable Motivating Attainable Rele
vant Trackable
29
Praising
Catch people doing things right. Praise them. Do
it frequently.
30
Reprimanding

• Critisize the behaviour, not the person.
• Talk about the facts. Gossips and impressions
  must be checked.
• Concentrate on most important aspects of the
  problem.
• Present the problem.
• Say what you feel.
• Break for a moment.
• Express your positive attitude towards the
  person.

31
Motivation Dynamics
32
Skills and Knowledge
33
Management Dynamics
Motivating
Detached
Directive
34
Summary
At last!

• Disciplined approach to change managment (CMM)
• Requirements management practices
• Team dynamics management

35
Questions?
?
36
Quality assessment

• 1. What is your general impression? (1 - 6)
• 2. Was it too slow or too fast?
• 3. What important did you learn during the
  lecture?
• 4. What to improve and how?