Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management.

Slides:



Advertisements
Similar presentations
Extreme Programming Copyright, 1999 © Jerzy R. Nawrocki Personal Software Process Lecture.
Advertisements

Extreme Programming Alexander Kanavin Lappeenranta University of Technology.
Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements Engineering.
System Analysis & Design Methods V Extreme Programming XP/dX.
Procedures for CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall B.1.
NAUG NAUG Knowledge Evening – th February 2007.
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
Extreme Hour Role-Playing The XP Process. What Is Extreme Programming? n User Stories:Function, Qualities, Priority, Scope. n Schedule:By negotiation.
RequisitePro (1) Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
Quality Assurance Copyright, 2002 © Jerzy R. Nawrocki Quality Management Auxiliary.
Agile Requirements Methods CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute October 26, 2004.
Introduction to XP “When the tests all run, you’re done”
Extreme Programming Collaboration in Software Development Process.
Copyright  Larry Dribin, Ph.D. SE470_ProjMgmt_v1.ppt SE470 - ProjMgmt - 1 Excellence in Software Engineering Repeatable Level Defined Level Manage.
EXtreme Programming Quick Introduction Daniel Arraes Pereira Eduardo Lourenço Apolinário Ricardo de Oliveira Cavalcanti.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 15 Finalizing.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
Management 421 Computer Science 350. Overview Project Roles Software Development Process Extreme Programming Management/Developer Interaction in Extreme.
Introduction to ISO 9001:2000 Copyright, 2002 © Jerzy R. Nawrocki Quality Management.
Creator: ACSession No: 19 Slide No: 1Reviewer: - CSE300Advanced Software EngineeringMarch 2007 ‘Agile Methods’ (part 2) CSE300 Advanced Software Engineering.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Roles Managers Technical Team Leaders Programmers Customers Database Administrators Instructors.
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,
Requirements specification Copyright, 2001 © Jerzy R. Nawrocki Quality Management.
Current Trends in Systems Develpment
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
Extreme programming overview Agenda  Extreme programming goals  Extreme programming values  Extreme programming practices  The Extreme programming.
Unified Process versus Extreme Programming. Outline Compare and contrast UP and XP  Processes / Disciplines  Management  Artefacts Risk management.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
1 e X treme P rogramming D. Dranidis September 2000 CITY College.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
1 Software Process Models-ii Presented By; Mehwish Shafiq.
Project Planning Copyright, 2002 © Jerzy R. Nawrocki Requirements Engineering.
Planning Game in Artifacts Tracker (AT) Project Michal Pilawski.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
XP – Extreme Programming
Quality of Usage Scenarios Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Extreme Programming David Li CTO, DigitalSesame. Problem in Developing Software The Basic Problem - Risk –Schedule slips –Project canceled –System goes.
1 김 수 동 Dept. of Computer Science Soongsil University Tel Fax
Introduction to Requirements Engineering Copyright, 2000 © Jerzy R. Nawrocki Requirements.
XP Overview Short Life cycle Risky / Dynamic Requirements Increase developer productivity.
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
Extreme programming (XP) Variant of agile Takes commonsense practices to extreme levels © 2012 by Václav Rajlich1.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix B Agile Methodologies B.1.
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.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY 1 eXtreme Programming – one of the Agile Software Development Methodologies.
Planning Extreme programming
Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Comparison of CMM Level 2 and eXtreme Programming Copyright, 2002 © Bartosz Walter Web Applications and Services.
Introduction to SoDA Copyright, 2001 © Jerzy R. Nawrocki Quality Management Lecture.
Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.
1 Introduction to eXtreme Programming Remko Popma Azzurri Ltd.
Extreme programming (XP) Advanced Software Engineering Dr Nuha El-Khalili.
Software Development. The Software Life Cycle Encompasses all activities from initial analysis until obsolescence Analysis of problem or request Analysis.
Coming up: What is Agile? XP Development Dan Fleck 2010 Dan Fleck 2010.
Toward Maturity Model for eXtreme Programming Copyright, 2001 © J. Nawrocki, B. Walter, A.. Wojciechowski
Software Development Life Cycle. The Software Life Cycle  Encompasses all activities from initial analysis until end of work  Formal process for software.
Requirements Engineering Lecture 13
Requirements Engineering Lecture 4
Appendix B Agile Methodologies
Planning User stories are written.
What do you need to know about XP?
Appendix B Agile Methodologies
Extreme Programming (and Pair Programming)
Presentation transcript:

Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Quality Management Lecture 5 Quality Management Lecture 5

J. Nawrocki, Quality Manag., Lecture 5 Plan of the lecture Software development practices Roles for people Calendar Measurements The Planning Game

J. Nawrocki, Quality Manag., Lecture 5 Software development practices Pair programming (single programmers + reviews) Design for today, not for tomorrow (look-ahead design) Continuous integration (controlled integration) Practices specific to XP Error

J. Nawrocki, Quality Manag., Lecture 5 Software development practices Oral communication (written communication) Artefacts: only code + test cases (SRS, plans, design) On-side customer (remote customer) Practices specific to XP

J. Nawrocki, Quality Manag., Lecture 5 Software development practices No SRS (user stories) No architecture design (metaphor) No UML diagrams or other stored pictures No formal reviews No long-term planning No traceability information Practices absent in XP IEEE/ANSI standard

J. Nawrocki, Quality Manag., Lecture 5 Software development practices Planning Game: business / technical decisions Exploration phase + concrete experiments Writing test cases as early as possible Automated testing (as far as possible) Common practices BusinessDevelopment

J. Nawrocki, Quality Manag., Lecture 5 Software development practices Incremental planning Short releases Software configuration management tools Coding standards Open, honest communication Accepted responsibility Common practices

J. Nawrocki, Quality Manag., Lecture 5 Roles for people Programmers (3rd year) Coach (4th year) Tracker (4th year) Customer Testers (5th year) Teamwork

J. Nawrocki, Quality Manag., Lecture 5 CalendarCalendar : Rehearsals : Project presentations till 25.11: Team building till 20.12: Exploration/experiments (Exploration report) till 13.02: Winter break till 11.04: Release 1 (8 weeks, 160 h/programmer) till 17.04: Easter break till 13.06: Release 2 (8 weeks, 160 h/programmer) Easter’01: 15.04

J. Nawrocki, Quality Manag., Lecture 5 MeasurementsMeasurements Time the customer spend with the team (in each week) Time spend on pair programming (in each week) Other team work (per week) Time spend working alone (in each week) Time spend on exploration, release 1, release2. Time spend by team members

J. Nawrocki, Quality Manag., Lecture 5 MeasurementsMeasurements Number of refactorings Number of integrations Total number of created / modified / removed test cases Total number of created / modified / removed lines of code Rework time ??? XP-oriented measures

J. Nawrocki, Quality Manag., Lecture 5 MeasurementsMeasurements Experimentation phase Release1 Release2 Iterations Meetings Delays

J. Nawrocki, Quality Manag., Lecture 5 MeasurementsMeasurements In code In test cases In tools, operating systems, and other environment elements Misunderstandings Time spend on detecting and fixing a defect Defects

J. Nawrocki, Quality Manag., Lecture 5 The Planning Game Maximise the value of the software produced in a given time for a given amount of money. Goal

J. Nawrocki, Quality Manag., Lecture 5 The Planning Game ‘To invest as little as possible to put most valuable functionality into production as quickly as possible.’ Strategy

J. Nawrocki, Quality Manag., Lecture 5 The Planning Game The pieces Date: Type of activity: New: X Fix:__ Enhance:__ Story number: 23 STORY DESCRIPTION: When the COLA rate changes in the middle of the BIW Pay Period, we will want to pay the 1st week of the period at the old COLA rate, and the 2nd week of the Pay Period at the NEW COLA rate. Should occur automatically based on the system design. NOTES:

J. Nawrocki, Quality Manag., Lecture 5 The Planning Game Exploration (write / estimate / split a story) Commitment (sort by value, sort by risk, set velocity, choose scope) Steer (1-3 weeks iteration, recovery, new story, re-estimation) The moves

J. Nawrocki, Quality Manag., Lecture 5 SummarySummary Practices Calendar Measurements The Planning Game

J. Nawrocki, Quality Manag., Lecture 5 Further readings K. Beck, Extreme Programming Explained, Addison-Wesley, 

J. Nawrocki, Quality Manag., Lecture 5 HomeworkHomework Assess maturity of RE processes in your last-year SDS project Write an HTML document (Requirements Management Policy) describing the list of guidelines you are willing to follow this year

J. Nawrocki, Quality Manag., Lecture 5 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?