
32fa119de4269165242efae9473a195b.ppt
- Количество слайдов: 28
Requirements Engineering & Project Management Lecture 5 Project Planning & Initiation Jerzy. Nawrocki@put. poznan. pl www. cs. put. poznan. pl/jnawrocki/require/
Key Roles in XPrince Analy st Archite ct Time J. Nawrocki, Project Planning. . Project Manager Time
XPrince Artefacts A&S Plan Most Important Use Cases Requirements Spec. Mockup Architect. Vision & Tools Initial Prototype (code + test cases) Init. Project Plan Architect. Plan GUI Design Updat. Proj. Plan Accept. Tests Frame Analyst Aim & Scope. Architecture Business Model and System Scope Architect J. Nawrocki, Project Planning. . Project Manager
Agenda • • Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions • XPrince Principles • XPrince Processes • Aim & Scope • Planing in PRINCE 2 • Cooperation with Project Board J. Nawrocki, Project Planning. .
XPrince Principles • Communication between project stakeholders supported by: Planning Game, Wideband Delphi, Reviews, Reflection Workshops, 2+1 schema & shared room. J. Nawrocki, Project Planning. .
XPrince Principles • Test-driven development: Test-frist coding, automated test execution, defect-based testcases • Documentation split among the roles and limited: Architect & developers: code + test cases Analyst: business model, use-case-based SRS, acceptance tests report, user’s guide. Project manager: project plan, stage plans, reports. • Reviews of non-executable artifacts (requirements specification, test reports, test J. Nawrocki, Project Planning. .
XPrince Principles • 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 J. Nawrocki, Project Planning. .
XPrince Principles • 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 J. Nawrocki, Project Planning. .
Agenda • • Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions • XPrince Principles • XPrince Processes • Aim & Scope • Planing in PRINCE 2 • Cooperation with Project Board J. Nawrocki, Project Planning. .
Management Team in PRINCE 2 Project Board Senior Executiv Senior user e Supplier Project Assurance Project Manager Project Support Kierownik Team Manager Zespołu J. Nawrocki, Project Planning. .
PRINCE Process Model Directing a Project DP Starting up a Project SU Initiating a Project IP Managing Stage Boundaries SB Planning Controlling a PL PL PL Stage CS J. Nawrocki, Project Planning. . Managing Product Closing a Project CP
Management Team in PRINCE 2 Project Board Senior Executiv Senior user e Supplier Project Assurance Project Manager Project Support Kierownik Team Manager Zespołu J. Nawrocki, Project Planning. .
Classical Process Diagram for PRINCE 2 Directing a Project DP Starting up a Project SU Initiating a Project IP Plannin g PL J. Nawrocki, Project Planning. . Managing Stage Boundaries SB Controlling a Stage CS Managing Product Closing a Project CP
XPRINCE Process Map Directing a Project DP Startin g up Aim&Sc. Planning Aim & Scope Architectur e Architec. Planning Const Tran siructio tion Release Planning Project. Planning J. Nawrocki, Project Planning. . Closin ga Project Postmort. Planning
Agenda • • Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions • XPrince Principles • XPrince Processes • Aim & Scope • Planing in PRINCE 2 • Cooperation with Project Board J. Nawrocki, Project Planning. .
Classical Process Diagram for PRINCE 2 Aim & Scope Directing a Project DP Starting up a Project SU Initiating a Project IP Plannin g PL J. Nawrocki, Project Planning. . Managing Stage Boundaries SB Controlling a Stage CS Managing Product Closing a Project CP
Project Quality Plan Project Plan Business Case IP Planning Quality Planning a Project IP 1 IP 2 Setting up Project Controls IP 4 Setting up Project Files IP 5 Refining the Business Case and Risks IP 3 Assembling a Project Init. Doc. IP 6 Communi- Project Issue Qualit Lessons cation Controls Reg. y Reg. Learned Report Plan J. Nawrocki, Project Planning. . Project Initiation Document
XPrince Artefacts A&S Plan Most Important Use Cases Architect. Vision & Tools J. Nawrocki, Project Planning. . Temporary Maintained artefact Init. Project Plan Aim & Scope Business Model and System Scope
Con. Ops Use Cases Architec. Vision IP Business Modelling IP 1 Project Planning IP 4 Projec t Plan Architectu re Plan J. Nawrocki, Project Planning. . Most Important Use Cases IP 2 Architecture Vision & Tools IP 3 Risk Analysis Setting up Project Files IP 5 IP 6 Proje ct Web Page Project Registe rs
Agenda • • Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions • XPrince Principles • XPrince Processes • Aim & Scope • Planing in PRINCE 2 • Cooperation with Project Board J. Nawrocki, Project Planning. .
Hierarchicz Opisy na produktó struktura w produktów Projektowa nie planu PL 1 Szacowanie PL 4 Diagram Lista Zależności przepływ czynnoś między u czynnościa ci produktó mi Definiowani Identyfikacj w e i analiza produktów PL 2 a czynności i zależności PL 3 Szeregowan ie PL 5 Analizowani e ryzyka. PL 6 Scalanie planu PL 7 Harmonogram Oszacowa nie czynności J. Nawrocki, Project Planning. . Rejest r ryzyka
PRINCE 2 Lifecycle 16. 10 27. 11 Starti Initiating ng Up a Project a Projec t 23. 01 Stage 1 J. Nawrocki, Project Planning. . 8. 04 27. 05 Stage 2 Stage 3 17. 06 1. 07 Stage Closin 4 ga Project
Agenda • • Introduction XPrince Team Project Lifecycle The Analyst Role The Architect Role The Project Manager Role Scaling up Conclusions • XPrince Principles • XPrince Processes • Aim & Scope • Planing in PRINCE 2 • Cooperation with Project Board J. Nawrocki, Project Planning. .
The PRINCE Process Model Directing a Project DP Starting up a Project SU Initiating a Project IP Plannin g PL J. Nawrocki, Project Planning. . Managing Stage Boundaries SB Controlling a Stage CS Managing Product Closing a Project CP
Directing a Project Authorising Initiation Authorisin Giving g a Project ad hoc Starting up a Project SU Initiating a Project IP Directio n Plannin g PL J. Nawrocki, Project Planning. . Authorisin g a Stage or Excep. Plan Managing Stage Boundaries SB Controlling a Stage CS Managing Product Confirming Project Closure Closing a Project CP
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 J. Nawrocki, Project Planning. .
Questions? J. Nawrocki, Project Planning. .
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? J. Nawrocki, Project Planning. .