Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 1

Project Group Members:Project Manager: Jonas ScheuringRelease Manager: Gert Jan HuismanChange Manager: Antti UimonenTest Manager: Jeremie BensimonFunc. App. Mngr: Erik Waals

19th November 2010at Hanzehogeschool

ADVISORY PRESENTATION KPNPROJECT GROUP 6

Presented by:Jonas ScheuringErik WaalsJeremie Bensimon

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 2 / 18

Introduction GC: KIP SC: Introduction SC: Suggestions Conclusion

Index

IntroductionGeneric Case:

• Key Improvement Points (KIP)

Specific Case:• Introduction• Suggestions

Conclusion

Introduction GC KIP SC Introduction SC Suggestions Conclusion

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Introduction

The main project milestones where: Interview key contacts Analyze key improvement points Set up an advisory report to KPN

Introduction GC KIP SC Introduction SC Suggestions Conclusion

Business challenges

Hanze ICT Students

Theoretical knowledge

Go Live

3 / 18

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Introduction SC Introduction SC Suggestions Conclusion

Telcom want integrated Change Management

Advise how to organize change process including overall Change Control Board

GC Introduction

GC KIP

4 / 18

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Improve the stakeholder communication

Improve the test processes

Review the change management flow

Define the responsibilities of the CCB

GC Key Improvement Points

Introduction SC Introduction SC Suggestions ConclusionGC KIP

5 / 18

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Improve the suppliers communication:

Supplier could be represented in the CAB

Each supplier should inform the CAB when a change on a product appear

GC Key Improvement Points

Introduction SC Introduction SC Suggestions ConclusionGC KIP

6 / 18

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Improvement of the test processes

Test automation

Increase test efforts

At the earliest moment

Efficiency

GC Key Improvement Points

Introduction SC Introduction SC Suggestions ConclusionGC KIP

7 / 18

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Review the Change Management Flow

GC Key Improvement Points

8 / 18

Introduction SC Introduction SC Suggestions ConclusionGC KIP

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Define the responsibilities of the CCB

• CCB should provide information to stakeholders about the change

• All the changes should be introduced in the CAB meetings before going to the CCB

• The change control board is constituted of project stakeholders or their representatives.

GC Key Improvement Points

Introduction SC Introduction SC Suggestions ConclusionGC KIP

9 / 18

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

SC Introduction

The Case

A new business release needs the implementation of more than 10 applications with dependencies: deliver a proposal how to organize such an implementation and also think of testing the chain after implementation

10 / 18

Introduction SC Introduction SC Suggestions ConclusionGC KIP

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

SC Introduction

ap1 ap2

ap6ap5

ap10

ap7

ap3

ap8

ap4

ap11ap9 ap12

11 / 18

Introduction SC Introduction SC Suggestions ConclusionGC KIP

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

SC Suggestions

Planning

Documentation global

Parties need to test their own application

Parties need to make detailed documentation.

Use standardized links between applications

12 / 18

Introduction SC Introduction SC Suggestions ConclusionGC KIP

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

SC Suggestions

What must be in the documentation

What is the chain? Who is responsible? Who has what interest? What is the business interest? Who is involved? Is it only an application? Is it used before? Are there any SLA’s? What links is there between the applications? What is effected else? Demands and constraints

13 / 18

Introduction SC Introduction SC Suggestions ConclusionGC KIP

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

SC Suggestions

• Standardized links

14 / 18

Introduction SC Introduction SC Suggestions ConclusionGC KIP

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

SC Suggestions

Testing

• Testing is decision of party

• Complete chain will be tested by the party with the biggest interest

• They test the system by tryout the input and output

• Also some performance tests are really important, i.e. simulating a gigantic workload.

• Problems will be fixed by the responsible party 

15 / 18

Introduction SC Introduction SC Suggestions ConclusionGC KIP

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

SC Suggestions

After the implementation

• Review change

• Control the chain

• Chain manager

• Documentation

• Chain manager need to know all the changes in the chain.

16 / 18

Introduction SC Introduction SC Suggestions ConclusionGC KIP

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Conclusion

We just highlighted a few points out of our advisory

A good and extensive advice needs much more analysis time

We can advice to review and evaluate IT Processes regularly

Maybe in combination of a student internship

17 / 18

Introduction GC: KIP SC: Introduction SC: Suggestions ConclusionIntroduction GC KIP SC Introduction SC Suggestions Conclusion

Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals

Feedback / Questions

?18 / 18

Introduction GC: KIP SC: Introduction SC: Suggestions ConclusionIntroduction GC KIP SC Introduction SC Suggestions Conclusion