1. Project Management with XPrince www.cs.put.poznan.pl/jnawrocki/require Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki „Trabrennen” in Austria

2. J.Nawrocki, XPrince (1) Software Crises LOOPLOOP ate oor quality ver budget vertime Loop Loop is dangerous.

3. J.Nawrocki, XPrince (1) Disciplined approach More discipline! Requirem. Design Coding Testing ISO 9000 IEEE Std 1 2 3 4 5

4. J.Nawrocki, XPrince (1) Disciplined approach to project management 1975: PROMPT, Simpact Systems Ltd 1979: PROMPT becomes a standard of CCTA Managing Successful Projects with PRINCE 2 1989: CCTA introduces PRINCE CCTA = the Central Computer and Telecommunications Agency, UK 1996: CCTA publishes PRINCE2 PRINCE = PRojects IN Controlled Environments

5. J.Nawrocki, XPrince (1) Too much discipline kills initiative and flexibility

6. J.Nawrocki, XPrince (1) Agile software development – 90s People & communication Customer collaboration Responding to change Tommorow or never! O K Working software

7. J.Nawrocki, XPrince (1) XP Tom DeMarco "XP is the most important movement in our field today." Extreme Programming (XP) = a lightweight (agile) a lightweight (agile) software development methodology software development methodology

8. J.Nawrocki, XPrince (1) XP Interesting practices of XP: strong customer orientation strong customer orientation increments & short releases increments & short releases test-first coding test-first coding refactoring refactoring planning game etc. planning game etc.

9. J.Nawrocki, XPrince (1) XP Frederick P. Brooks IBM OS/360 Manager (1964-65) No silver bullet!

10. J.Nawrocki, XPrince (1) Weaknesses Discipline (Celebrity )Agility (XP) Excessive paper work Slow decision process Low flexibility Change-resistance Assumption of on-site customer Lack of written documents Too short planning perspective

11. J.Nawrocki, XPrince (1) The solution Addison-Wesley, 2004. Barry Boehm Richard Turner Balancing Agility and Discipline A Guide for the Perplexed „ every successful venture in a changing world requires both agility and discipline ”

12. J.Nawrocki, XPrince (1) XPrince e X treme Pr ogramming in c ontrolled e nvironments XPrince origins XP PRINCE 2Rational Unified Process

13. J.Nawrocki, XPrince (1) Presentation Plan Introduction Team Structure Project Lifecycle Requirements Engineering with UC Workbench Developing the Software „Trabrennen” in Austria

14. J.Nawrocki, XPrince (1) Presentation Plan Introduction Team Structure Project Lifecycle Requirements Engineering with UC Workbench Developing the Software „Trabrennen” in Austria

15. J.Nawrocki, XPrince (1) XP Team

16. J.Nawrocki, XPrince (1) XP Team Customer Coach Tracker Tester Programmers

17. J.Nawrocki, XPrince (1) Management Team in PRINCE 2

18. J.Nawrocki, XPrince (1) Management Team in PRINCE 2 Project Board Senior user ExecutiveSenior Supplier

19. J.Nawrocki, XPrince (1) Management Team in PRINCE 2 Project Board Senior user ExecutiveSenior Supplier Project Manager Report Plan

20. J.Nawrocki, XPrince (1) Management Team in PRINCE 2 Project Board Senior user ExecutiveSenior Supplier Project Manager Project Assurance Report Plan

21. J.Nawrocki, XPrince (1) Kierownik Zespołu Management Team in PRINCE 2 Project Board Senior user ExecutiveSenior Supplier Project Manager Project Assurance Team Manager Project Support Report Plan Report Work pack.

22. J.Nawrocki, XPrince (1) Roles in RUP

23. J.Nawrocki, XPrince (1) Roles in RUP Project Manager Tester Developer Analyst Architect

24. J.Nawrocki, XPrince (1) XPrince Team

25. J.Nawrocki, XPrince (1) XP Prince 2 XPrince Team

26. J.Nawrocki, XPrince (1) XP Prince 2 Kierownik Zespołu XPrince Team Project Board Senior user ExecutiveSenior Supplier Manager = Coach Project Assurance Developers Architect = Coach Analyst = Client

27. J.Nawrocki, XPrince (1) Presentation Plan Introduction Team Structure Project Lifecycle Requirements Engineering with UC Workbench Developing the Software „Trabrennen” in Austria

28. J.Nawrocki, XPrince (1) PRINCE 2 Lifecycle

29. J.Nawrocki, XPrince (1) PRINCE 2 Lifecycle 16.1027.1123.018.0427.0517.061.07 Starting Up a Project Initiating a Project Stage 1Stage 2Stage 3Stage 4Closing a Project

30. J.Nawrocki, XPrince (1) XP Lifecycle

31. J.Nawrocki, XPrince (1) Release 2Release 1 XP Lifecycle Increment 1Increment 2Increment 1Increment 2

32. J.Nawrocki, XPrince (1) RUP Phases

33. J.Nawrocki, XPrince (1) RUP Phases Inception ElaborationConstructionTransition

34. J.Nawrocki, XPrince (1) XPrince Lifecycle

35. J.Nawrocki, XPrince (1) XPrince Lifecycle 16.1027.1123.018.0427.0517.068.07 Starting Up a Project Aim and Scope Architect ure Release 1 Release 2 Release 3 Closing a Project Business Modelling Increment 1 Scope Elabor. Increment 2 Transition

36. J.Nawrocki, XPrince (1) Team Growth 16.1027.1123.018.0427.0517.068.07 Starting Up a Project Aim and Scope Architec- ture Release 1 Release 2 Release 3 Closing a Project Manager Analyst Architect + 1 Dev. All the developers

37. J.Nawrocki, XPrince (1) XPrince Lifecycle 16.1027.1123.018.0427.0517.068.07 Starting Up a Project Aim and Scope Architect ure Release 1 Release 2 Release 3 Closing a Project Business Modelling Increment 1 Scope Elabor. Increment 2 Transition

38. J.Nawrocki, XPrince (1) Starting-up a Project (SU) Project Exec and Project Manager SU1 SU Project Mandate Design of a Project Management Team SU2 Designation of the Project Manag. Team SU3 Cust + PM Project Brief SU4 Cust + PM Project Approach SU5 Plan for Project Initiat. SU6 PM Supervisor

39. J.Nawrocki, XPrince (1) Project Mandate Customer name: …………………………………… Customer representative: …………………………. e-mail: ……………………………………………. phone: ……………………………………………. Project title: …………………………………………..

40. J.Nawrocki, XPrince (1) Starting-up a Project (SU) Project Exec and Project Manager SU1 SU Design of a Project Management Team SU2 Designation of the Project Manag. Team SU3 Cust + PM Project Brief SU4 Cust + PM Project Approach SU5 Plan for Project Initiat. SU6 PM

41. J.Nawrocki, XPrince (1) XP Prince 2 Kierownik Zespołu XPrince Team Project Board Senior user ExecutiveSenior Supplier Manager Project Assurance Developers Architect Analyst

42. J.Nawrocki, XPrince (1) Starting-up a Project (SU) Project Exec and Project Manager SU1 SU Design of a Project Management Team SU2 Management Team Designation of the Project Manag. Team SU3 Cust + PM Project Brief SU4 Project Approach SU5 Plan for Project Initiat. SU6

43. J.Nawrocki, XPrince (1) Project Management Team Executive : Jerzy Nawrocki nawrocki@put.poznan.pl (61) 665 29 80 Senior supplier : Bartosz Walter bartosz.walter@cs.put.poznan.pl (61) 665 29 80 Senior User : Executive

44. J.Nawrocki, XPrince (1) Starting-up a Project (SU) Project Exec and Project Manager SU1 SU Design of a Project Management Team SU2 Designation of the Project Manag. Team SU3 Cust + PM Project Brief SU4 Project Brief Cust + PM Project Approach SU5 Plan for Project Initiat. SU6 PM

45. J.Nawrocki, XPrince (1) Metoda FAST / JAD„Klient” FAST = Facilitated Application Specification Technique JAD Joint Application Development Prowadzący Analityk

46. J.Nawrocki, XPrince (1) Agenda – Project Brief Prolog Meeting Epilog 0 Sprawdzenie obecności i zatw. agendy 5’ 1 Krótka charakterystyka klienta 5’ 2 Na czym polega problem? 15’ 3 Kogo ten problem dotyczy? 5’ 4 Implikacje problemu 10’ 5 Koncepcja rozwiązania problemu 10’ 6 Sprawy organizacyjne 10’ Info for customer: Aim of the meeting (scope) + draft agenda Questions: Participants? How long? (<90’) Time & place? Report: Project title. Time & place of the meeting. Participants. Decisions made (next meeting?). Scope. Ask for: Scope confirmation + opinion on feasability of the proj.

47. J.Nawrocki, XPrince (1) Summary Combination of agile methodology (XP) with disciplined ones (PRINCE 2 and RUP) is possible Combination of agile methodology (XP) with disciplined ones (PRINCE 2 and RUP) is possible Tool support (UC Workbench) is important Tool support (UC Workbench) is important Flexible approach to pair programming Flexible approach to pair programming

48. J.Nawrocki, XPrince (1) Questions?