Originally posted by Cindy Cheung:
1. What is the system devleopment life cycle of XP (I just know the 4 values and 12 practices of XP)
2. Does it has any similar phase as SDLC?
4. What are the advantages and disadvantages of XP from a management perspective?
5. Does XP provide an improvement in systems development leading to better business outcomes?
6. How XP affect the quality of information system developed using this approach?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
The idea is to split the project into very short iterations, typically 1-3 weeks each, in which you perform every activity you would on a "SDLC project". The iteration starts with the team sitting down with the customer to plan what the team is going to build during the iteration, i.e. come up with user stories. Then, the team starts to implement the user stories by discussing with the customer about the details of the story under work and creating an acceptance test for the said story. When the iteration ends, the team reflects on the progress and tweaks the process if necessary. Then it all starts again.1. What is the system devleopment life cycle of XP (I just know the 4 values and 12 practices of XP)
See my answer above. The best way to think about it would be "there are no phases in XP", in my opinion, although certain activities are performed before the XP cycle starts (creating a business case of some sort, marketing research, etc.).2. Does it has any similar phase as SDLC?
The practices and high discipline present in an XP development team makes for high quality -- code reviews are constant (pair programming), testing is automated, the source code repository is held in a good state at all times (continuous integration and automated tests), all "risky" code is covered by unit tests (test-driven development, although this isn't really one of the original 12 XP practices) etc.3. What impacts cause manager would select XP as the systems development methodology? (any impacts on time, cost, culture etc)
The biggest disadvantage is probably that most enterprises have developed their management practices based on cost accounting and the false assumption that software development is a manufacturing process (while it's really a design process) and can be estimated as such.4. What are the advantages and disadvantages of XP from a management perspective?
Yes, because the focus is on throughput and elimination of waste, it is possible to manage software development projects based on their actual ROI. It's possible to cancel a project and actually have it deliver something that generates value to the business.5. Does XP provide an improvement in systems development leading to better business outcomes?
6. How XP affect the quality of information system developed using this approach?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]