1. Agile Configuration
Management
June 23° , 2017
Scuola Universitaria Professionale della
Svizzera Italiana
SUPSI
1
Daniele Di Lorenzo
Senior Project Manager & Configuration Manager
daniele.dilorenzo@gmail.com
2. “I have a Dream”
(Martin Luter King, 28 August 1963)
To add up the Configuration Management into adaptative
environment, like agile frameworks
2
The Dream
3. 3
The norms usually use
some elements of Agile
frameworks, and add up
these practices into
own model.
Agile frameworks provide
interesting characteristics:
• Iterations (cadence)
• Several tools
• Several software
Characteristics of Agile frameworks
5. Adaptative characterization of requirements 5
I: Independent
N: Negotiable
V: Valuable
E: Estimable
S: Small
T: Testable
User Story
Bill Wake, 2003
Task
7. Characterization Areas: CA-BA-RA 7
Configuration Area (CA)
All need information to identify and to trace the item and
the linked to it.
i.e.
• Identification ID
• Version
• Change request associati
• State of item
• Approved by
• …
Body Area (BA)
The description of the requirement.
i.e.
• Elevator Pitch
• User Story (AS A … I WANT TO …SO THAT … VERIFY
THAT …)
• Kanban board
• …
Rules Area (RA)
Set of the rules the specific item (or category of)
must follow
i.e.
• Naming to use
• Acceptance criteria and which format of
• Guarantee the INVEST/SMART characterization
• …
8. Examples of Elevator Pitch item characterization 8
Iteration XXX
ID:
VER:
CHANGE ID:
STATUS:
APPROVED BY:
BL ID:
RL ID:
CAFOR <target customer>
WHO <statement of the need>
THE <product name>
IS A <product/market category>
THAT <key benefit>
UNLIKE <primary competitor>
OUR PRODUCT <further/market differentiation>
BA
RA
Univocity of requirement
Natural language
All fields must be compiled
The naming of CI must be defined
Characterization of CI
9. Process Flow 9
Static of the Flow Dynamic of the Flow
Characterization of each category of
configuration items (CA) *
Populate CA-BA-RA areas
Definition of rules (RA)
* HP: usage of tools Elevator Pitch, Lean Canvas, Story
Mapping (User Stories and Tasks as well), Kanban
ID: EP01
VER: 01
CHANGE ID:
STATUS: DRAFT
APPROVED BY:
BL ID:
RL ID:
ID: EP01
VER: 05
CHANGE ID: CR001,
CR002
STATUS: APPROVED
& CLOSED
APPROVED BY: PO
BL ID: BL003
RL ID: RL003
Elevator Pitch
ID: ST001
VER: 01
CHANGE ID:
STATUS: DRAFT
APPROVED BY:
BL ID:
RL ID:
TRACK SM ID: SM01
ID: ST001
VER: 01
CHANGE ID:
STATUS: APPROVED
FOR DEV
APPROVED BY: PO
BL ID: BL005
RL ID: RL004
TRACK SM ID: SM01
User Story
Each iteration
Step trend of dynamic
10. Agile Configuration
Management
Daniele Di Lorenzo
Senior Project Manager & Configuration Manager
daniele.dilorenzo@gmail.com
Thank you!
Scuola Universitaria Professionale della
Svizzera Italiana
SUPSI
10