Rational Suite and CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki [email protected] Requirements.
Project Management with XPrince Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki...
-
Upload
egbert-bennett -
Category
Documents
-
view
214 -
download
0
Transcript of Project Management with XPrince Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki...
Project Management with XPrince
Project Management with XPrince
www.cs.put.poznan.pl/jnawrocki/require
Requirements Eng. & Project ManagementLecture 10
Jerzy Nawrocki
„Trabrennen” in Austria
J.Nawrocki, XPrince (1)
Software Crises
L
O
O
P
ate
oor quality
ver budget
vertime
Loop
Loop is dangerous.
J.Nawrocki, XPrince (1)
Disciplined approach
More discipline!
Requirem.
Design
Coding
Testing
ISO 9000
IEEE Std
IEEE Std
IEEE Std
1
2
3
4
5
J.Nawrocki, XPrince (1)
Disciplined approach to project management
1975: PROMPT, Simpact Systems Ltd
1979: PROMPT becomes a standard of CCTA
Managing Successful Projects Managing Successful Projects with PRINCE 2with PRINCE 2
1989: CCTA introduces PRINCE
CCTA = the Central Computer and Telecommunications Agency, UK
1996: CCTA publishes PRINCE2
PRINCE = PRojects IN Controlled Environments
J.Nawrocki, XPrince (1)
Too much discipline kills initiative and flexibility
J.Nawrocki, XPrince (1)
Agile software development – 90s
People & communication
Customer collaboration Responding to change
Tommorow or never!
O KO K
Working software
J.Nawrocki, XPrince (1)
XP
Tom DeMarcoTom DeMarco
"XP is the most important movement in our field today."
Extreme ProgrammingExtreme Programming (XP) (XP) = =
a lightweight (agile) a lightweight (agile)
software development methodologysoftware development methodology
J.Nawrocki, XPrince (1)
XP
Interesting practices of XPInteresting practices of XP: : • strong customer orientationstrong customer orientation• increments & short releasesincrements & short releases• test-first codingtest-first coding• refactoringrefactoring• planning gameplanning game etc. etc.
J.Nawrocki, XPrince (1)
XP
Frederick P. BrooksIBM OS/360 Manager (1964-65)
No silver bullet!
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
J.Nawrocki, XPrince (1)
The solution
Addison-Wesley, 2004.
Barry BoehmRichard Turner
Balancing Agilityand Discipline
A Guide for the Perplexed
„every successful venture in a changing world requires both agility and discipline”
J.Nawrocki, XPrince (1)
XPrince
eXtreme Programmingin controlled environments
XPrince origins
XP
PRINCE 2 Rational Unified Process
J.Nawrocki, XPrince (1)
Presentation Plan
• Introduction• Team Structure• Project Lifecycle• Requirements Engineering
with UC Workbench• Developing the Software
„Trabrennen” in Austria
J.Nawrocki, XPrince (1)
Presentation Plan
• Introduction• Team Structure• Project Lifecycle• Requirements Engineering with
UC Workbench• Developing the Software
„Trabrennen” in Austria
J.Nawrocki, XPrince (1)
XP Team
J.Nawrocki, XPrince (1)
XP Team
Customer
Coach
Tracker
Tester
Programmers
J.Nawrocki, XPrince (1)
Management Team in PRINCE 2
J.Nawrocki, XPrince (1)
Management Team in PRINCE 2
Project Board
Senior user
Executive Senior Supplier
J.Nawrocki, XPrince (1)
Management Team in PRINCE 2
Project Board
Senior user
Executive Senior Supplier
Project Manager
Report
Plan
J.Nawrocki, XPrince (1)
Management Team in PRINCE 2
Project Board
Senior user
Executive Senior Supplier
Project Manager
Project AssuranceReport
Plan
J.Nawrocki, XPrince (1)
Kierownik ZespołuKierownik Zespołu
Management Team in PRINCE 2
Project Board
Senior user
Executive Senior Supplier
Project Manager
Project Assurance
Team Manager
Project Support
Report
Plan
Report
Work pack.
J.Nawrocki, XPrince (1)
Roles in RUP
J.Nawrocki, XPrince (1)
Roles in RUP
Project Manager
Tester
Developer
Analyst
Architect
J.Nawrocki, XPrince (1)
XPrince Team
J.Nawrocki, XPrince (1)
XP
Prince 2
XPrince Team
J.Nawrocki, XPrince (1)
XP
Prince 2
Kierownik ZespołuKierownik Zespołu
XPrince Team
Project Board
Senior user
Executive Senior Supplier
Manager = Coach
Project Assurance
Developers
Architect = CoachAnalyst=Client
J.Nawrocki, XPrince (1)
Presentation Plan
• Introduction• Team Structure• Project Lifecycle• Requirements Engineering with
UC Workbench• Developing the Software
„Trabrennen” in Austria
J.Nawrocki, XPrince (1)
PRINCE 2 Lifecycle
J.Nawrocki, XPrince (1)
PRINCE 2 Lifecycle
16.10 27.11 23.01 8.04 27.05 17.06 1.07
Starting Up a
Project
Initiating a Project
Stage 1 Stage 2 Stage 3 Stage 4 Closing a
Project
J.Nawrocki, XPrince (1)
XP Lifecycle
J.Nawrocki, XPrince (1)
Release 2Release 1
XP Lifecycle
Increment 1 Increment 2 Increment 1 Increment 2
J.Nawrocki, XPrince (1)
RUP Phases
J.Nawrocki, XPrince (1)
RUP Phases
Inception ElaborationElaboration Construction Transition
J.Nawrocki, XPrince (1)
XPrince Lifecycle
J.Nawrocki, XPrince (1)
XPrince Lifecycle
16.10 27.11 23.01 8.04 27.05 17.06 8.07Starting
Up a Project
Aim and Scope
Architecture
Release 1
Release 2
Release 3
Closing a
Project
Business Modelling
Increment 1
Increment 1
Increment 1
Increment 1
Scope Elabor.
Increment 2
Increment 2
Increment 2
Increment 2
Transition Transition Transition
J.Nawrocki, XPrince (1)
Team Growth
16.10 27.11 23.01 8.04 27.05 17.06 8.07Starting
Up a Project
Aim and Scope
Architec-ture
Release 1
Release 2
Release 3
Closing a
Project
ManagerAnalyst
Architect + 1 Dev.All the developers
J.Nawrocki, XPrince (1)
XPrince Lifecycle
16.10 27.11 23.01 8.04 27.05 17.06 8.07Starting
Up a Project
Aim and Scope
Architecture
Release 1
Release 2
Release 3
Closing a
Project
Business Modelling
Increment 1
Increment 1
Increment 1
Increment 1
Scope Elabor.
Increment 2
Increment 2
Increment 2
Increment 2
Transition Transition Transition
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 + PMProject Approach
SU5
Plan for Project Initiat.
SU6
PM
Supervisor
J.Nawrocki, XPrince (1)
Project Mandate
Customer name: ……………………………………Customer representative: …………………………. e-mail: ……………………………………………. phone: …………………………………………….Project title: …………………………………………..
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 + PMProject Approach
SU5
Plan for Project Initiat.
SU6
PM
J.Nawrocki, XPrince (1)
XP
Prince 2
Kierownik ZespołuKierownik Zespołu
XPrince Team
Project Board
Senior user
Executive Senior Supplier
Manager
Project Assurance
Developers
ArchitectAnalyst
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 + PMCust + PM
Project Brief
SU4
Project Approach
SU5
Plan for Project Initiat.
SU6
J.Nawrocki, XPrince (1)
Project Management Team
Executive: Jerzy Nawrocki [email protected] (61) 665 29 80Senior supplier: Bartosz Walter [email protected] (61) 665 29 80Senior User: Executive
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 + PMCust + PM
Project Brief
SU4
Project Brief
Cust + PMCust + PMProject Approach
SU5
Plan for Project Initiat.
SU6
PMPM
J.Nawrocki, XPrince (1)
Metoda FAST / JAD
„„Klie
nt”
Klient”
FAST = Facilitated Application Specification TechniqueJAD Joint Application
Development
Prowad
zący
Prowad
zący Analityk
Analityk
J.Nawrocki, XPrince (1)
Agenda – Project Brief
PrologMeetingEpilog
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 agendaQuestions: 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.
J.Nawrocki, XPrince (1)
Summary
CCombinombination ofation of agileagile methodology (XP) with methodology (XP) with disciplineddisciplined ones (PRINCE 2 and RUP)ones (PRINCE 2 and RUP) is is possiblepossible
Tool support (UC Workbench) is Tool support (UC Workbench) is importantimportant
Flexible approach to pair Flexible approach to pair programmingprogramming
J.Nawrocki, XPrince (1)
Questions?