Paper Title:

Maurer, F. Martel, S.
Extreme Programming - Rapid development for Web-based applications,
Internet Computing, IEEE, Jan/Feb 2002
Volume: 6, Issue: 1, pp. 86-90

Three Critical Questions

Group 1:

Member Name: Bokka Satya Saradhi

1)This paper says that face to face communication is much preferable rather than documentation approach but how do they resolves problems such as , when majority of the employees of the software development team leaves the company ?

2)Author says that XP is more popular for web development, no doubt it is true .So what special features made it so popular, compared to the Softwares owned by other gigantic companies?

3)In pair programming technique, who will be given priority for every conflict issue? (Because same problem can be coded in different ways , each one will prefer their owns technique).

Member Name:Vallurupalli Anusha

1) The author says that having one part time customer and good telecommunication can be sufficient to achieve constant communication. Is it feasible that with one part time customer, can the service all round the day can be handled? For large projects involving long hours will one part time customer service fetch effective results?
2) Is it always an issue that working over time hours leads to reduced quality?
3)To what extent is pair programming feasible?

Group 2:

Member Name: Chrianjeevi Ashok Puvvula

1. How can Software quality be achieved based on testing without the actual code being developed?
2. How can a large software be developed using XP with the involvement of fewer people(pair programming) than desired?
3. Do Small releases help in fastening the development process?
4. Do you think the XP's Concept of sustainable development will always be acceptable even in cases of emergency?
5. Is that the onsite customer requirements are the only requirements that are needed to develop the project?

Member Name: Anuradha Pathuri

1. The paper considers an example where in a study has been conducted in a small company and the statistics of the productivity are listed before and after using the Extreme Programming process in that company. But I question the consistency of the numbers based on such a study, since it could be possible that the productivity might have increased overtime because of the experience gained by the programmers and might not be because of the change in the process.
2. Is there a way in which we can increase the development speed of the companies with bigger projects with more number of people involved? Can we make use of the XP process partially in such a scenario? Probably for the Semi- automated projects, where in we need to develop similar kind of web-pages, then we need not have to keep lot of paper keeping and documentation for such automated part.
3. Is the XP process standalone i.e., for example say let us consider a project which is already successful using the conventional software engineering process approach model to go through all the phases of design, coding, testing and implementation. So we assume that there are no requirement changes. Now, if we implement the XP process for that project, would there be any advantage or disadvantage? Can the conventional process be completely replaced by the XP process?

Group 3:

Member Name: Bindu

1. As implementing all 12 practices would take a lot of human effort and increases the cost of the project would applying all the 12 practices be possible in reality?

2. It is not clear as to how many people can be in a team for a XP process to be working fine. Does this serve equally well for a group of more than 15?

3.Will this agile software process XP maintain top quality without having any effect on the development process?

Member Name: Yogendra Siva Ram Boppana

1.The paper even though convinced that XP is a good software process by comparing it with traditional object-oriented approach, by showing the Productivity gain ,but is it better than the other software process which is more successful than Object-Oriented approach ?

2.Having an on-site customer is a very good practice to prioritize the requirements from customer’s point of view. But is it practical to have a on-site customer representative available all the times? If provided, the work for on-site customer representative is only when the planning of the process comes in to picture.

3.XP is an apt software process to develop Web-Based Applications. But it’s restricted to the project groups in which only 5-15 people are working. Can we extend this process by relaxing some of the principles of XP? So that, big projects can also follow the Extreme Programming.

Group 4:

Member Name:Srikanth Voruganti

1) Why is the technique not being used other than business contexts?
2) In the whole topic the time constraint is not specified. Will XP with all its features being employed can reduce the duration of the project? If so how much? If it’s more then why can’t we use this technique for large group of members by dividing them into smaller sub groups?
3) Can this technique be simultaneously run with other methods?

++++Member Name:Srujan Kumar Swarna
1. XP is good for team that contains 5 to 15 developers. Then how to maintain same concept for team that contains more members?

2. "Collective ownership" practice leads to change in code for several times. So according to "Refactoring" practice it leads some problems. So is this correct to distribute ownership on code to all members?

3. Without paper work or documentation work what will be the backup for the project?

Group 5:


Critical Questions:

1. The paper claims that it is suitable for smaller groups. But how many persons can be in a team?

2. The paper stated the statistical measurements of NLOC, methods and classes per effort to prove it gives increased productivity. But, are they performed on the persons with same intelligence?

3. It was mentioned that it best suits for the development of web applications. Doesn't it suit for other than web applications?

4. In this paper it was suggested that the employers to work for 40 work hours per week. How they are going to cope up with deadlines and critical situations of delivery?

Group 6:


1) XP does not have stable requirements. How can a project developed without having stable requirements?

2) In the paper the author had mentioned that customer representative is in the development of the project. Is it safe if a non-technical person (customer representative) linked to a technical team?

3) In the paper the author had replaced the paper based with the face-to-face communication. Through how the other people can understand that project without having the paper work of that project?

Group 7:

Member Name: Rameshwaram Karunapriya

Critical Questions:
1.)It works best for small teams, but will this be applicable for the larger teams?

2.)Will the precise documentation be beneficial for the third person?

3.)Will the pair programming be effective and efficient in all circumstances?

Group 8:

Member Name:Nikhilesh Katakam

Critical questions :

1)The paper claims about customer satisfaction by small releases but how efficient is approach as it would add up a cost overheard for releasing a new version of the software ?
2) The paper claims that pair programming increases the software quality . but ther e was not sufficient evidence about how it would help in Improving the software quality ?
3) The paper says that this approch pays off well for a small group of 5-15 people. But there is not sufficient proof stated in the paper to show that this approach wont work for a large group of 100-150 members ?
4) How safe is it to use collective ownership approach , that would allow any person to modify or change a part of the code which some times would cause problems to other part of code if the person who is modifying did not fully understand the existing problem ?

Group 9:


1. How is ideal engineering time(IET) calculated?

Group 10:

Member Name: Jonnalagadda,Harideep Reddy

1. In the developed process, if user raises many doubts regarding the documentation part and as there are small groups, it naturally takes longer time to resolve. This makes practice of sustainable development questionable. What is XP’s programmers’ reply to this???

2. XP itself mean that it follows simple coding techniques. What is the use of again following the practice of coding standards???

3. Is there any strong based proof regarding XP’s practices are efficient even in reality?????

Member Name:Chennamaneni Manasa

1.As mentioned the pair programming helps to improve the software quality so to improve the quality in best way can we have more members more than two?
2.How the team is organized and work together when paper based is replaced with face-to-face communication?
3.How many people can work in a team for planning the game when considering both customer views and tecnical aspects?

Zheng Jia

1. What are the available handy tools other than IDE integrated tools(eg. separate testing tools, design tools, re-factoring tools, prototyping tools) for the XP programming?

2. Is it possible for the integration of existing software engineering practice and tools into XP, to maintain its simpleness while compensate its drawbacks(eg, lack of documentation which could results in difficulty in tracing problems or requirements.)

3. Frameworks or toolkits, which could speedup the coding process while contributing the XP practice, and their relationships with XP principles. For example, framework which could facilitate unit testing.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License