Project Planning & Initiation Requirements Engineering & Project Management Lecture.

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements Engineering.
Project Management with XPrince (2) Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki „Trabrennen”
Project Management with XPrince Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki „Trabrennen” in.
Agile development By Sam Chamberlain. First a bit of history..
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Estimation of Defects and Effort Requirements Engineering & Project Management Lecture.
Agile
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
Chapter 30 Agile Requirements Methods. Mitigating Requirements Risk  The entire requirements discipline within the software lifecycle exists for only.
COMP 350: Object Oriented Analysis and Design Lecture 2
... And you actually want to “go live” with that?
Chapter 1 The Systems Development Environment
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Chapter 30 Agile Requirements Methods. Mitigating Requirements Risk  The entire requirements discipline within the software lifecycle exists for only.
Project Planning Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxilliary.
Human Factor in Project Management Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki Prince Jozef.
UML - Development Process 1 Software Development Process Using UML (2)
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Quality Connection 2002, Helsinki Poznan University of Technology Poznan,
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Use Cases Requirements Engineering & Project Management Lecture 2.
Better Systems? That means improvement of the development process! M.H.J. Vucsan 2005 Statistics Netherlands.
Agile Software Development Chapter 3 – Lecture 1 Adrián Susinos.
Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.
Software Testing Life Cycle
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Unified Process versus Extreme Programming. Outline Compare and contrast UP and XP  Processes / Disciplines  Management  Artefacts Risk management.
Industrial Software Project Management Some views on project managing industrial and business software projects.
Requirements Verification & Validation Requirements Engineering & Project Management.
Introduction to XPrince Requirements Engineering & Project Management Lecture 1.
Systems Analysis Lecture 2 Analysing the Business Case Feasibility Scope 1 BTEC HNC Systems Support Castle College 2007/8.
PRINCE 2 for Managers Copyright, 2003 © Jerzy R. Nawrocki
Copyright © Jerzy R. Nawrocki The Requirements Document and IEEE 830 Requirements Engineering.
Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
VirtuCo :: Process description ::. :: Reference ::
Software Engineering Saeed Akhtar The University of Lahore Lecture 5 Originally shared for: mashhoood.webs.com.
Prince2 1. What does Prince2 stand for: PRojects IN Controlled Environments How many processes are there? How many separate sub-processes are there?
K.Ingram 1 Sept 2007 Agile Software Development. K.Ingram 2 Sept 2007 Contents Agile Software Development: 1.What is it? 2.Agile’s Values, Principles,
University of Sunderland CIFM02 Unit 4 COMM02 Project Planning Unit 4.
University of Sunderland CIF 301 Unit 4 CIF 301 Project Planning Unit 4.
RUP and Elaboration Phase Copyright, 2003 © Jerzy R. Nawrocki Requirements Engineering.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management.
Project Management with XPrince Requirements Eng. & Project Management Lecture 11 Jerzy Nawrocki „Trabrennen” in.
Project management Topic 1 Project management principles.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Change Management Requirements Engineering & Project Management Lecture 10.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
University of Sunderland ENGM91 Unit 4 ENGM91 Project Planning Unit 4.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
Configuration Management (II) Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Software Testing Process
CS223: Software Engineering Lecture 16: The Agile Methodology.
1 Ringbourne Management Ltd An Overview for Project Managers.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Overview PRINCE Hogeschool Rotterdam. 2 Project definition  A project is a temporary organization that is created for the purpose of delivering.
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Web Applications and Services.
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Peopleware Requirements Engineering & Project Management Lecture 7.
Embedded Systems Software Engineering
Chapter 5 Agile Development Moonzoo Kim KAIST
Requirements Engineering Lecture 4
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Information Technology Project Management – Fifth Edition
Introduction to PRINCE 2
Requirements Engineering Lecture 2
Attend|Learn|Grow Taking Your Career to the Next Level
Guidance notes for Project Manager
Joint Application Development (JAD)
Presentation transcript:

Project Planning & Initiation Requirements Engineering & Project Management Lecture 5

J.Nawrocki, Project Planning.. Key Roles in XPrince Project Manager Analyst Architect Time

J.Nawrocki, Project Planning.. Architecture Aim & Scope XPrince Artefacts Business Model and System Scope Most Important Use Cases Architect. Vision & Tools Requirements Spec. Mockup Accept. Tests Frame Initial Prototype (code + test cases) GUI Design A&S Plan Init. Project Plan Architect. Plan Updat. Proj. Plan Analyst Architect Project Manager

J.Nawrocki, Project Planning.. Bibliography X 

J.Nawrocki, Project Planning.. 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

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 test-cases 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 cases etc.)

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 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

J.Nawrocki, Project Planning.. Kierownik Zespołu Management Team in PRINCE 2 Project Board Senior user ExecutiveSenior Supplier Project Manager Project Assurance Team Manager Project Support

J.Nawrocki, Project Planning.. PRINCE Process Model Starting up a Project SU Controlling a Stage CS Managing Product Delivery Managing Stage Boundaries SB Initiating a Project IP Closing a Project CP Planning PL Planning PL Planning PL Directing a Project DP

J.Nawrocki, Project Planning.. Management Team in PRINCE 2 Project Board Senior user ExecutiveSenior Supplier Kierownik Zespołu Project Manager Project Assurance Team Manager Project Support

J.Nawrocki, Project Planning.. Classical Process Diagram for PRINCE 2 Directing a Project DP Managing Stage Boundaries SB Starting up a Project SU Controlling a Stage CS Planning PL Managing Product Delivery Initiating a Project IP Closing a Project CP

J.Nawrocki, Project Planning.. XPRINCE Process Map Archi- tecture Starting up Directing a Project DP Aim&Sc. Planning Aim & Scope Closing a Project Release Const- ruction Transi- tion Architec. Planning Release Planning ProjectPlanning Postmort. Planning

J.Nawrocki, Project Planning.. 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

J.Nawrocki, Project Planning.. Classical Process Diagram for PRINCE 2 Directing a Project DP Managing Stage Boundaries SB Starting up a Project SU Controlling a Stage CS Planning PL Managing Product Delivery Initiating a Project IP Closing a Project CP Aim & Scope

J.Nawrocki, Project Planning.. Setting up Project Con- trols Planning Quality Planning a Project Refining the Business Case and Risks Setting up Project Files Assembling a Project Init. Doc. IP1IP2IP3 IP4IP5 IP6 IP Project Quality Plan Project Plan Business Case Project Controls Communi- cation Plan Project Initiation Document Quality Reg. Issue Reg. Lessons Learned Report

J.Nawrocki, Project Planning.. Aim & Scope XPrince Artefacts Business Model and System Scope Most Important Use Cases Architect. Vision & Tools Temporary artefact Maintained artefact A&S Plan Init. Project Plan

J.Nawrocki, Project Planning.. Project Planning Business Modelling Most Important Use Cases Architecture Vision & Tools Risk AnalysisSetting up Project Files IP1IP2IP3 IP4IP5 IP6 IP ConOpsUse CasesArchitec. Vision Architecture Plan Project Plan Project Registers Project Web Page

J.Nawrocki, Project Planning.. 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

J.Nawrocki, Project Planning.. Projektowanie planu Definiowanie i analiza produktów Identyfikacja czynności i zależności Analizowanie ryzyka PL1PL2PL3 PL6 Scalanie planu PL7 Hierarchiczna struktura produktów Opisy produktów Szeregowanie Diagram przepływu produktów Szacowanie PL4PL5 Lista czynności Zależności między czynnościami Oszacowanie czynności Harmonogram Rejestr ryzyka

J.Nawrocki, Project Planning.. PRINCE 2 Lifecycle Starting Up a Project Initiating a Project Stage 1Stage 2Stage 3Stage 4Closing a Project

J.Nawrocki, Project Planning.. 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

J.Nawrocki, Project Planning.. The PRINCE Process Model Directing a Project DP Managing Stage Boundaries SB Starting up a Project SU Controlling a Stage CS Planning PL Managing Product Delivery Initiating a Project IP Closing a Project CP

J.Nawrocki, Project Planning.. Directing a Project Authorising Initiation Authorising a Project Authorising a Stage or Excep. Plan Giving ad hoc Direction Confirming Project Closure Managing Stage Boundaries SB Starting up a Project SU Controlling a Stage CS Planning PL Managing Product Delivery Initiating a Project IP Closing a Project CP

J.Nawrocki, Project Planning.. 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?