Extreme Programming Modified Extreme Programming Modified : : Embrace Requirements Engineering Embrace Requirements Engineering Practices Practices J. Nawrocki, M. Jasinski, B. Walter, A.Wojciechowski Poznan University of Technology, Poznan, Poland IEEE Joint International Conference on Requirements Engineering 9-13 September 2002, Essen, Germany
IEEE Joint International Conference on Requirements Engineering 9-13 September 2002, Essen, Germany. Extreme Programming Modified : Embrace Requirements Engineering Practices. J . Nawrocki , M. Jasinski, B. Walter, A.Wojciechowski Poznan University of Technology, Poznan, Poland. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
• increments & short releasesincrements & short releases
• test-first codingtest-first coding
• planning gameplanning game etc. etc.
IntroductionIntroduction
WeaknessesWeaknesses of XP of XP: :
• lack of documentationlack of documentation
• one (on-site) customerone (on-site) customer
• too short planning perspectivetoo short planning perspective
How to solve those problemsand preserve agility?
ContentsContents
1. Introduction
2. Reconciling XP with documentation3. Multiple customer representatives
4. Modifying the XP lifecycle
5. Early evaluation results
6. Conclusions
Reconciling XP with documentationReconciling XP with documentation
Travel light.Travel light.
Documen-tationDocumen
-tation
Developer
I’ve changed my mind.Let’s go that way.
Customer
Reconciling XP with documentationReconciling XP with documentation
Travel light.Travel light.What you need is justWhat you need is just code and test cases code and test cases. .
I’ve changed my mind.
Customer
code +tests
No problem.
IEEE
Standard 830
UML
Reconciling XP with documentationReconciling XP with documentation
Oral communication is preferred as „Oral communication is preferred as „the written the written and e-mail communications (..) are error-proneand e-mail communications (..) are error-prone”.”.
Why did I decide to ..
Travel light.Travel light.What you need is justWhat you need is just code and test cases code and test cases. .
Error
But people sometimes forget!
Reconciling XP with documentationReconciling XP with documentation
To be agile does not mean that you have to To be agile does not mean that you have to throw away the (requirements) documentation.throw away the (requirements) documentation.
I’ve changed my mind.
Customer
Documen-tation
No problem.
Reconciling XP with documentationReconciling XP with documentation
To be agile does not mean that you have to To be agile does not mean that you have to throw away the (requirements) documentation.throw away the (requirements) documentation.
Documen-tation
No problem.
Developer
I’ve changed my mind.
Customer
Reconciling XP with documentationReconciling XP with documentation
To be agile does not mean that you have to To be agile does not mean that you have to throw away the requirements documentation.throw away the requirements documentation.
XP roles:• Customer• Developer• Coach• Tracker• Tester
In XP tester „is responsible for helping the customer choose and write functional tests”.
-- Kent Beck
Tester-analyst (product manager)is responsible for writing and managing usage scenarios, requirements, and acceptance tests.