1. Requirements Engineering Lecture 4
Jerzy Nawrocki
Requirements Engineering
Lecture 4
Implementing XP at PUT
Copyright, 2000 © Jerzy R. Nawrocki
Requirements Eng., Lecture 4

2. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
Plan of the lecture
Software development practices
Roles for people
Calendar
Measurements
The Planning Game
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

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

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

5. Software development practices
Jerzy Nawrocki
Software development practices
Practices absent in XP
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
IEEE/ANSI
standard
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

6. Software development practices
Jerzy Nawrocki
Software development practices
Common practices
Planning Game: business / technical decisions
Exploration phase + concrete experiments
Writing test cases as early as possible
Automated testing (as far as possible)
Business
Development
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

7. Software development practices
Jerzy Nawrocki
Software development practices
Common practices
Incremental planning
Short releases
Software configuration management tools
Coding standards
Open, honest communication
Accepted responsibility
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

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

9. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
Calendar
: 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,
Easter’01:
15.04
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

10. Time spend by team members
Jerzy Nawrocki
Measurements
Time spend by team members
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.
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

11. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
Measurements
XP-oriented measures
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 ???
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

12. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
Measurements
Delays
Experimentation phase
Release1
Release2
Iterations
Meetings
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

13. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
Measurements
Defects
In code
In test cases
In tools, operating systems, and other environment elements
Misunderstandings
Time spend on detecting and fixing a defect
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

14. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
The Planning Game
Goal
Maximise the value of the software produced
in a given time
for a given amount of money.
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

15. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
The Planning Game
Strategy
Minimal investment.
Minimal development time.
Most valuable functionality.
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

16. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
The Planning Game
The pieces
User story
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, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

17. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
The moves
Exploration phase
Estimate a story
(Ideal Eng. Time)
Development
It was
not OK.
Split a story
Business
It was
not OK.
Business
It was
not OK.
Write a story
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

18. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
The moves
Commitment phase
Development
Sort by risk:
predictable
more or less
unpredictable
Set velocity:
IET / calendar
month
Business
Business
Choose scope
Sort by value:
necessary
important
optional
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

19. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
The moves
Steering phase
Iteration (2 weeks)
Recovery (Development)
New story (Business)
Re-estimate (Development)
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

20. J. Nawrocki, Requirements Eng.., Lecture 4
Summary
Practices
Calendar
Measurements
The Planning Game as RE
At last!
J. Nawrocki, Requirements Eng.., Lecture 4

21. J. Nawrocki, Requirements Eng.., Lecture 4
Jerzy Nawrocki
Further readings
K. Beck, Extreme Programming Explained, Addison-Wesley, 2000. 
J. Nawrocki, Requirements Eng.., Lecture 4
Requirements Eng., Lecture 4

22. J. Nawrocki, Requirements Eng.., Lecture 4
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, Requirements Eng.., Lecture 4