1. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 1 Project Group Members: Project Manager: Jonas Scheuring Release Manager: Gert Jan Huisman Change Manager: Antti Uimonen Test Manager: Jeremie Bensimon Func. App. Mngr: Erik Waals 19th November 2010 at Hanzehogeschool Presented by: Jonas Scheuring Eric Waals

2. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 2 / IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion Index Introduction Generic Case: Key Improvement Points (KIP) Specific Case: Introduction Suggestions Conclusion

3. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 3 Introduction The main project goals where: ‐ Interview key contacts ‐ Analyze key improvement points ‐ Deliver an advisory report to KPN IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion

4. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 4 GC: Key Improvement Points IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion

5. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 5 GC: Key Improvement Points IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion

6. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 6 GC: Key Improvement Points IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion

7. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 7 SC: Introduction IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion 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

8. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 8 SC: Introduction IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion ap1ap2 ap6ap5 ap10 ap7 ap3 ap8 ap4 ap11ap9ap12

9. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 9 SC: Suggestions IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion Planning Documentation global Parties need to test their own application Parties need to make detailed documentation. Use standardized links between applications

10. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 10 SC: Suggestions IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion 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 link is there between the applications? What is effected else? Demands and constraints

11. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 11 SC: Suggestions IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion Standard links

12. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 12 SC: Suggestions IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion 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.

13. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 13 SC: Suggestions IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion After the implementation Review change Control the chain Chain manager Documentation Chain manager need to know all the changes in the chain.

14. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 14 Conclusion IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion

15. Jérémie Bensimon, Gert Jan Huisman, Jonas Scheuring, Antti Uimonen, Erik Waals 15 Feedback / Questions IntroductionGC: KIPSC: IntroductionSC: SuggestionsConclusion