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

Slides:



Advertisements
Similar presentations
Introduction to the course Jerzy Nawrocki Requirements Eng. & Project Manag.
Advertisements

Systems Development Environment
Project Management with XPrince (2) Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki „Trabrennen”
A little Software Engineering: Agile Software Development C Sc 335 Rick Mercer.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
Software Life Cycles ECE 417/617: Elements of Software Engineering
EXtreme Programming Quick Introduction Daniel Arraes Pereira Eduardo Lourenço Apolinário Ricardo de Oliveira Cavalcanti.
Extreme Programming Mark Steverson. What Is Extreme Programming? ● Extreme Programming (XP) is a lightweight, agile methodology developed by Kent Beck.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Introduction to Agile Methodologies and Concepts Roy Osherove Principal, Team Agile Blog : ISerializable.com.
Chapter 1 The Systems Development Environment
Chapter 1 The Systems Development Environment
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
Solar Tech Chuck Hess, CEO Jamie Tofte, CFO Christina Cruz, CTO.
Human Factor in Project Management Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki Prince Jozef.
Communication in Project Management: Does it have to be so difficult?
Rational Suite and CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Quality Connection 2002, Helsinki Poznan University of Technology Poznan,
Chapter 1 The Systems Development Environment
Chapter 5 Software Process Models. Problems with “Traditional” Processes 1.Focused on and oriented towards “large projects” and lengthy development time.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Describing Methodologies PART II Rapid Application Development* Systems Analysis and Design II.
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers Unit 11 Slide 1 Chapter 1 The Systems Development Environment.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 4 Slide 1 Chapter 1 The Systems Development Environment.
COMP3001 Technology Management & Professional Issues: Project Management Agile and Iterative Planning Lecture 7 Graham Collins, UCL
Agile Methodologies: Comparative Study and Future Direction 林佳蓁 資工 4B.
Requirements Verification & Validation Requirements Engineering & Project Management.
Introduction to XPrince Requirements Engineering & Project Management Lecture 1.
Use-Cases Elicitation and FAST Copyright, 2003 © Jerzy R. Nawrocki Requirements Engineering.
Project Planning & Initiation Requirements Engineering & Project Management Lecture.
PRINCE 2 for Managers Copyright, 2003 © Jerzy R. Nawrocki
Copyright © Jerzy R. Nawrocki The Requirements Document and IEEE 830 Requirements Engineering.
CIS 210 Systems Analysis and Development Week 1 Part I The Systems Development Environment,
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Solar Tech Chuck Hess, CEO Jamie Tofte, CFO Christina Cruz, CTO.
RUP and Elaboration Phase Copyright, 2003 © Jerzy R. Nawrocki Requirements Engineering.
© 2005 by Prentice Hall Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Project Management with XPrince Requirements Eng. & Project Management Lecture 11 Jerzy Nawrocki „Trabrennen” in.
Introduction to Requirements Eng. Copyright, 2001 © Jerzy R. Nawrocki Requirements.
1 Software Engineering and Security DJPS April 12, 2005 Professor Richard Sinn CMPE 297: Software Security Technologies.
The Systems Development Environment Systems Analysis and Design II.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
Change Management Requirements Engineering & Project Management Lecture 10.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY 1 eXtreme Programming – one of the Agile Software Development Methodologies.
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Web Applications and Services.
APMG-International Webinar Integrating Agile into PRINCE2® Thursday 19 December 2013 / 13:00 GMT Presented by Melanie Franklin,
RATIONAL UNIFIED PROCESS PROCESS FRAMEWORK OVERVIEW.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Peopleware Requirements Engineering & Project Management Lecture 7.
Approaches to Systems Development
Process 4 Hours.
Requirements Engineering Lecture 4
Appendix B Agile Methodologies
Chapter 1 The Systems Development Environment
(c) Jerzy Nawrocki Jerzy Nawrocki
Introduction to PRINCE 2
Chapter 1 The Systems Development Environment
Approaches to Systems Development
Requirements Engineering Lecture 2
Appendix B Agile Methodologies
Topic 1: Introduction to the Module and an Overview of Agile
Joint Application Development (JAD)
Presentation transcript:

Project Management with XPrince Requirements Eng. & Project Management Lecture 10 Jerzy Nawrocki „Trabrennen” in Austria

J.Nawrocki, XPrince (1) Software Crises LOOPLOOP 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

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 : 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 K Working software

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

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.

J.Nawrocki, XPrince (1) XP Frederick P. Brooks IBM OS/360 Manager ( ) 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, 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 ”

J.Nawrocki, XPrince (1) XPrince e X treme Pr ogramming in c ontrolled e nvironments XPrince origins XP PRINCE 2Rational 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 ExecutiveSenior Supplier

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

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

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.

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łu XPrince Team Project Board Senior user ExecutiveSenior Supplier Manager = Coach Project Assurance Developers Architect = Coach Analyst = 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 Starting Up a Project Initiating a Project Stage 1Stage 2Stage 3Stage 4Closing a Project

J.Nawrocki, XPrince (1) XP Lifecycle

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

J.Nawrocki, XPrince (1) RUP Phases

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

J.Nawrocki, XPrince (1) XPrince Lifecycle

J.Nawrocki, XPrince (1) XPrince Lifecycle 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

J.Nawrocki, XPrince (1) Team Growth 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

J.Nawrocki, XPrince (1) XPrince Lifecycle 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

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

J.Nawrocki, XPrince (1) Project Mandate Customer name: …………………………………… Customer representative: …………………………. ……………………………………………. 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 + PM Project Approach SU5 Plan for Project Initiat. SU6 PM

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

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

J.Nawrocki, XPrince (1) Project Management Team Executive : Jerzy Nawrocki (61) Senior supplier : Bartosz Walter (61) Senior 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 + PM Project Brief SU4 Project Brief Cust + PM Project Approach SU5 Plan for Project Initiat. SU6 PM

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

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.

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

J.Nawrocki, XPrince (1) Questions?