Answer questions based on article:
2. What types of changes accompany the extreme programming methodology?
3. Why could a methodology such as extreme programming be good for a military project? What might be its disadvantages?
4. Does research mentioned at end of case study influence your view of XP?
he agile communicati suffered One team mem are development method called extreme joining the XP project and thot nesistonce from a Modinonal programming XP) has its enthusiasts and detractors ond the juryis out on whether itisabetter choice hierarchy o the more collaborativexP style of Research with undergraduates suggests that paired program mers about as well as the best of te pot bu one for doubt about whether "two heads are better than compared to approaches such as Scrum Mindful of how important agility is for military software, the US Strategic Co a pilot XP project. programming fosis however the students enoyed the progiomming ares many principles in common with Scrum and other agile XP methods, including the early and continuous delivery of fun some confidence. Another study of 40 XP teams suggests that paired isef may not be a key XP's success. The close collaboration between developers and end users, and respon makexp work are really the collective ownership of fhe siveness to changing requirements XP developers are less plan-driven and do much less documentation to define requirements XP also fea- factors that tures "pair programming, in which two developers the same computer. focus on code standards and testing fhe team members For the military projects pilot, the XP teams job was to add new In the U.S. Strategic Commands pilot, believed search functionality to SkiWeb the Command's strategic knowedge tions about fhe project were positive despite the snags, They better and information website used to share information about military that the XP approach led to very good quality software, even more operations and world events across the whole command and intel than the team might have produced using the old approach. As will ligence communities. All team members were contractors, except for and more organiza switch to agile methods such as xp we the government functional manager who served as user collaborator better understand just what it is about these methods that make them successful. The two programmers sat next to one another in a cubicle, and the user collaborator's office was on the same floor Other team members Discussion Questions were either in the same building or nearby, so no one was parficipat 11.25. How did the U.S. Strategic Command adjust to unexpected ing in virtual mode sues as it implemented extreme programming? The project got off to a rocky start when one of the two developers program announced that she d fried pair programming before and wasn't wil- 11-26. types of changes accompany the extreme ming methodology? ng to do it again. The team didn't try to enforce it, but did encourage could a methodology such as extreme programming be 11.27. er to work closely with her programming partner to solve thorny logic good for a project? What might be its disadvantages problems together. Other agile practices were welcomed and adopted 11.28. Does the research mentioned at the end of the case study easily For instance, the practice of delivering frequent small releases nfluence your view of XP? rather than infrequent major ones was already in place. Having the customer on-site is another critical element and the user collaborator Sources: Balijepalyv, Mahapatra. R.et I. (2009). Are two heads better than one for software development? The productivity paradox of pair programming. MIS was right down the hall. work 33(1), 91-118. et A case study: Introducing extr programming The daily meetings were very successful, but problems in Fruhling. McDonald, Proceed 41st assignments and communications arose.XP team members are sup- in aus government system development 11. 2011 posed to be fully assigned to the project to avoid distractions, but this 1109/HICSS 2008.4, accessed June programming projects team members were offen pulled off for other wood Successful extreme Technolog to the methodology or good teamworking? Information & Software 5504), 660-672. or emergencies. Midway through, they found they needed someone h expertise in interface design, but that person was skeptical about
