1. Implementing XP at PUT Copyright, 2000 © Jerzy R. Nawrocki Jerzy.Nawrocki@put.poznan.pl www.cs.put.poznan.pl/jnawrocki/mse/quality/ Quality Management Lecture 5 Quality Management Lecture 5

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

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

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

5. 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 830-1993

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

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

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

9. J. Nawrocki, Quality Manag., Lecture 5 CalendarCalendar 14-15.11: Rehearsals 21-22.11: 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

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

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

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

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

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

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

16. J. Nawrocki, Quality Manag., Lecture 5 The Planning Game The pieces Date: 6.11.01 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:

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

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

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

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

21. 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?