Object oriented design with applications
Object oriented design with applications
The capability maturity model: guidelines for improving the software process
The capability maturity model: guidelines for improving the software process
The case for collaborative programming
Communications of the ACM
Introduction to the team software process
Introduction to the team software process
Extreme programming explained: embrace change
Extreme programming explained: embrace change
On the criteria to be used in decomposing systems into modules
Communications of the ACM
A Discipline for Software Engineering
A Discipline for Software Engineering
Planning Extreme Programming
Extreme Programming Installed
Strengthening the Case for Pair Programming
IEEE Software
Extreme Programming from a CMM Perspective
IEEE Software
Recovery, Redemption, and Extreme Programming
IEEE Software
Using Extreme Programming in a Maintenance Environment
IEEE Software
Structured Analysis and System Specification
Structured Analysis and System Specification
Structured Programming With and Without go to Statements
IEEE Transactions on Software Engineering
Design and code inspections to reduce errors in program development
IBM Systems Journal
Combining Extreme Programming with ISO 9000
EurAsia-ICT '02 Proceedings of the First EurAsian Conference on Information and Communication Technology
New directions on agile methods: a comparative analysis
Proceedings of the 25th International Conference on Software Engineering
The Architecture of the Apex Platform, salesforce.com's Platform for Building On-Demand Applications
ICSE COMPANION '07 Companion to the proceedings of the 29th International Conference on Software Engineering
| Hi-index | 0.00 |
Lightweight software development methodologies promise an easy way to deliver products of high quality without excessive cost. On the contrary, classical heavyweight processes are well-defined and proven, but require a lot of effort. Two approaches: eXtreme Programming (XP) and CMM Level 2 have been used in joined industry-academic software projects run at the Poznan University of Technology. Running concurrently those two software approaches allowed us to compare them on the basis of experimental data. After the projects were completed, major risk factors connected with both approaches have been collected and some improvements have been proposed.