Advisory Presentation KPN Project Group 6

1. Advisory Presentation KPNProject Group 6 19th November 2010 at Hanzehogeschool Presented by: Jonas Scheuring Erik Waals JeremieBensimon Project Group Members: Project Manager: Jonas Scheuring Release Manager:Gert Jan Huisman Change Manager:AnttiUimonen Test Manager: JeremieBensimon Func. App. Mngr: Erik Waals

2. Introduction Introduction GC: KIP GC KIP SC: Introduction SC Introduction SC: Suggestions SC Suggestions Conclusion Conclusion Index Introduction Generic Case: • Key Improvement Points (KIP) • Specific Case: • Introduction • Suggestions Conclusion

3. Introduction GC KIP SC Introduction SC Suggestions Conclusion • Introduction Theoreticalknowledge Business challenges • The main project milestones where: • Interview key contacts • Analyze key improvement points • Set up an advisory report to KPN Hanze ICT Students Go Live

4. Introduction GC KIP SC Introduction SC Suggestions Conclusion • GC Introduction Telcom want integrated Change Management Advise how to organize change process including overall Change Control Board

5. Introduction GC KIP SC Introduction SC Suggestions Conclusion • GC Key Improvement Points • Improve the stakeholder communication • Improve the test processes • Review the change management flow • Define the responsibilities of the CCB

6. Introduction GC KIP SC Introduction SC Suggestions Conclusion • GC Key Improvement Points Improve the suppliers communication: • Supplier could be represented in the • CAB • Each supplier should inform the CAB • when a change on a product appear

7. Introduction GC KIP SC Introduction SC Suggestions Conclusion • GC Key Improvement Points Improvement of the test processes • Test automation • Increase test efforts • At the earliest moment Efficiency

8. Introduction GC KIP SC Introduction SC Suggestions Conclusion • GC Key Improvement Points Review the Change Management Flow

9. Introduction GC KIP SC Introduction SC Suggestions Conclusion • GC Key Improvement Points 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.

10. Introduction GCKIP SCIntroduction SC Suggestions Conclusion • 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

11. Introduction GCKIP SCIntroduction SC Suggestions Conclusion • SC Introduction ap1 ap2 ap3 ap4 ap5 ap6 ap7 ap8 ap9 ap10 ap11 ap12

12. Introduction GCKIP SC Introduction SCSuggestions Conclusion • SC Suggestions • Planning • Documentation global • Parties need to test their own application • Parties need to make detailed documentation. • Use standardized links between applications

13. Introduction GCKIP SC Introduction SCSuggestions Conclusion • 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

14. Introduction GCKIP SC Introduction SCSuggestions Conclusion • SC Suggestions • Standardized links

15. Introduction GCKIP SC Introduction SCSuggestions Conclusion • 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

16. Introduction GCKIP SC Introduction SCSuggestions Conclusion • SC Suggestions • After the implementation • Review change • Control the chain • Chain manager • Documentation • Chain manager need to know all the changes in the chain.

17. Introduction Introduction GC: KIP GC KIP SC: Introduction SC Introduction SC: Suggestions SC Suggestions Conclusion Conclusion • 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

18. Introduction Introduction GC: KIP GC KIP SC: Introduction SC Introduction SC: Suggestions SC Suggestions Conclusion Conclusion Feedback / Questions ?