Project Planning

1
Project Planning Initiation
Requirements Engineering Project
Management Lecture 5

• Jerzy.Nawrocki_at_put.poznan.pl
• www.cs.put.poznan.pl/jnawrocki/require/

2
Key Roles in XPrince
Project Manager
Time
Time
3
XPrince Artefacts
Aim Scope
Business Model and System Scope
AS Plan
Most Important Use Cases
Architect. Vision Tools
Init. Project Plan
Architecture
Requirements Spec.
Initial Prototype (code test cases)
Architect. Plan
Mockup
Accept. Tests Frame
GUI Design
Updat. Proj. Plan
Project Manager
4
Bibliography

• X

?
5
Agenda

• XPrince Principles
• XPrince Processes
• Aim Scope
• Planing in PRINCE 2
• Cooperation with Project Board

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

6
XPrince Principles
Individuals interactions over processes and
tools

• Communication between project stakeholders
  supported by
• Planning Game,
• Wideband Delphi,
• Reviews,
• Reflection Workshops,
• 21 schema shared room.

7
XPrince Principles
Working software over comprehensive documentation

• Test-driven development Test-frist coding,
  automated test execution, defect-based test-cases
• Documentation split among the roles and limited
• Architect developers code test cases
• Analyst business model, use-case-based SRS,
  acceptance tests report, users guide.
• Project manager project plan, stage plans,
  reports.
• Reviews of non-executable artifacts (requirements
  specification, test reports, test cases etc.)

8
XPrince Principles
Customer collaboration over contract negotiation

• Planning Game
• Analyst (on-site customer frequently does not
  work)
• User stories Use cases
• Mockups
• Short releases ( 6 weeks)
• Acceptance tests
• Risk management
• External (business) Customer (Executive)
  Analyst
• Technical (internal) Architect
• Organizational (internal) Project Manager

9
XPrince Principles
Responding to change over following a plan

• Planning Game
• User stories
• Releases split into a number of increments (e.g.
  two increments, 3 weeks each)
• Version management system
• Status-of-chage reporting tools (Bugzilla, issue
  register)
• Automatic regression testing

10
Agenda

• XPrince Principles
• XPrince Processes
• Aim Scope
• Planing in PRINCE 2
• Cooperation with Project Board

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

11
Management Team in PRINCE 2
Project Board
Senior user
Executive
Senior Supplier
Project Assurance
Project Manager
Project Support
Kierownik Zespolu
Kierownik Zespolu
Team Manager
12
PRINCE Process Model
Starting up a Project SU
13
Management Team in PRINCE 2
Project Board
Senior user
Executive
Senior Supplier
Project Assurance
Project Manager
Project Support
Kierownik Zespolu
Kierownik Zespolu
Team Manager
14
Classical Process Diagram for PRINCE 2
Directing a Project DP
Managing Stage Boundaries SB
Starting up a Project SU
Initiating a Project IP
Closing a Project CP
Controlling a Stage CS
Planning PL
Managing Product Delivery
15
XPRINCE Process Map
Starting up
16
Agenda

• XPrince Principles
• XPrince Processes
• Aim Scope
• Planing in PRINCE 2
• Cooperation with Project Board

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

17
Classical Process Diagram for PRINCE 2
Directing a Project DP
Managing Stage Boundaries SB
Starting up a Project SU
Initiating a Project IP
Closing a Project CP
Controlling a Stage CS
Planning PL
Managing Product Delivery
18
Project Plan
Business Case
Project Quality Plan
IP
Planning Quality
Planning a Project
Refining the Business Case and Risks
IP1
IP2
IP3
Setting up Project Con- trols
Setting up Project Files
Assembling a Project Init. Doc.
IP4
IP5
IP6
Communi-cation Plan
Issue Reg.
Project Controls
Quality Reg.
Project Initiation Document
Lessons Learned Report
19
XPrince Artefacts
Aim Scope
Business Model and System Scope
AS Plan
Most Important Use Cases
Architect. Vision Tools
Init. Project Plan
Temporary artefact
Maintained artefact
20
ConOps
Use Cases
Architec. Vision
IP
Business Modelling
Most Important Use Cases
Architecture Vision Tools
IP1
IP2
IP3
Project Planning
Risk Analysis
Setting up Project Files
IP4
IP5
IP6
Project Plan
Project Web Page
Architecture Plan
Project Registers
21
Agenda

• XPrince Principles
• XPrince Processes
• Aim Scope
• Planing in PRINCE 2
• Cooperation with Project Board

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

22
Hierarchiczna struktura produktów
Diagram przeplywu produktów
Zaleznosci miedzy czynnosciami
Lista czynnosci
Opisy produktów
Projektowanie planu
Definiowanie i analiza produktów
Identyfikacja czynnosci i zaleznosci
PL1
PL2
PL3
Analizowanie ryzyka
Szeregowanie
Szacowanie
PL6
PL4
PL5
Scalanie planu
PL7
Harmonogram
Oszacowanie czynnosci
Rejestr ryzyka
23
PRINCE 2 Lifecycle
16.10 27.11 27.11 23.01 8.04 27.05 17.06 1.07
Starting Up a Project Initiating a Project Initiating a Project Stage 1 Stage 2 Stage 3 Stage 4 Closing a Project



24
Agenda

• XPrince Principles
• XPrince Processes
• Aim Scope
• Planing in PRINCE 2
• Cooperation with Project Board

• Introduction
• XPrince Team
• Project Lifecycle
• The Analyst Role
• The Architect Role
• The Project Manager Role
• Scaling up
• Conclusions

25
The PRINCE Process Model
Directing a Project DP
Managing Stage Boundaries SB
Starting up a Project SU
Initiating a Project IP
Closing a Project CP
Controlling a Stage CS
Planning PL
Managing Product Delivery
26
Directing a Project
Authorising a Project
Authorising Initiation
Authorising a Stage or Excep. Plan
Giving ad hoc Direction
Confirming Project Closure
Managing Stage Boundaries SB
Starting up a Project SU
Initiating a Project IP
Closing a Project CP
Controlling a Stage CS
Planning PL
Managing Product Delivery
27
Summary

• XPrince tries to implement the Agile Manifesto.
• XPrince process are more specific than PRINCE 2
  ones.
• Project Initiation is based on Aim Scope
  specification supported with planning.
• Whole team should participate in planning

At last!
28
Questions?
?
29
Quality assessment

• 1. What is your general impression? (1 - 6)
• 2. Was it too slow or too fast?
• 3. What important did you learn during the
  lecture?
• 4. What to improve and how?