extremeprogramming (XP) is an agilesoftware development methodology defined through a set of practices and values. Although the value of XP is well-established through various real-life case studies, it lacks practi...
详细信息
ISBN:
(纸本)9783642130533
extremeprogramming (XP) is an agilesoftware development methodology defined through a set of practices and values. Although the value of XP is well-established through various real-life case studies, it lacks practices for project management. In order to enable XP for larger projects, we provide the rolling forecast practice to support product planning, and an optimization model to assist in release planning. We briefly evaluate the new practices with a real-life case study.
this manuscript describes a technique to perform comparisons on agile methods, based on a set of relevant features and attributes. this set includes attributes related to four SWEBOK Knowledge Areas (KAs) and to the A...
详细信息
ISBN:
(纸本)9783642130533
this manuscript describes a technique to perform comparisons on agile methods, based on a set of relevant features and attributes. this set includes attributes related to four SWEBOK Knowledge Areas (KAs) and to the agile Manifesto principles. Withthis set of attributes, by analyzing the practices proposed by each method, we are able to assess (1) the coverage degree for the considered KAs and (2) the agility degree.
though agile methodologies have gained widespread acceptance in the past decade, there are still a number of potential adopters who are yet to join the critical mass. Some of these adopters need assurance of whether a...
详细信息
ISBN:
(纸本)9783642130533
though agile methodologies have gained widespread acceptance in the past decade, there are still a number of potential adopters who are yet to join the critical mass. Some of these adopters need assurance of whether agilesoftware methodologies will continue to be the dominant software process technology of the 2010s and beyond. this study applies the softwareengineering Process Technologies Adoption Grid proposed by Fichman & Kemerer [3] to evaluate the adoption trajectory of agilesoftware development (ASD) methodologies. the study concludes that ASD methodologies will continue to be the dominant software process technology of the 2010's, and adopted by more business organizations.
Experimentation is one way to gain insight into how processes perform for a team, but industry teams rarely do experiments, fearing that such educational excursions will incur extra costs and cause schedule over-runs....
详细信息
ISBN:
(纸本)9783642130533
Experimentation is one way to gain insight into how processes perform for a team, but industry teams rarely do experiments, fearing that such educational excursions will incur extra costs and cause schedule over-runs. When facing a stalemate concerning the use of pair programming one industry-like, academic team constructing a commercial-grade web application, performed a lightweight experiment comparing pair programming and programming alone using Fagan inspection. through the experiment, the team learned that pair programming was not only faster than programming alone, but also required less effort and produced code of more predictable quality. Conducting the experiment required only eight hours of effort over six weeks (a mere 0.5% of the total effort during that time frame) and afforded crucial information for choosing the best practices for the team. As demonstrated by this experience, lightweight experimentation is cost effective and does not threaten project schedules.
Experience from numerous agile teams in the transition to agile methods in the Ericsson Operation and Maintenance has shown that teamwork and collaboration are crucial to achieving success. this finding motivated a re...
详细信息
ISBN:
(纸本)9783642130533
Experience from numerous agile teams in the transition to agile methods in the Ericsson Operation and Maintenance has shown that teamwork and collaboration are crucial to achieving success. this finding motivated a review of how sports coaches work to build effective teams. the review highlighted certain characteristics that sports coaches deem fundamental to success. this report details these finding and how we use these characteristics to helping teams improve.
Customer collaboration is vital to agile projects. through a Grounded theory study of New Zealand and Indian agile teams we discovered that lack of customer involvement was causing problems in gathering and clarifying...
详细信息
ISBN:
(纸本)9783642130533
Customer collaboration is vital to agile projects. through a Grounded theory study of New Zealand and Indian agile teams we discovered that lack of customer involvement was causing problems in gathering and clarifying requirements, loss of productivity, and business loss. "agile Undercover" allows development teams to practice agile despite insufficient or ineffective customer involvement. We present the causes and consequences of lack of customer involvement on agile projects and describe the agile Undercover strategies used to overcome them.
Collaboration-intensive agile practices are dependent on the development team understanding the customer's perspective and requirements. through a Grounded theory study of agile teams in New Zealand and India, we ...
详细信息
ISBN:
(纸本)9783642130533
Collaboration-intensive agile practices are dependent on the development team understanding the customer's perspective and requirements. through a Grounded theory study of agile teams in New Zealand and India, we discovered that a gap between the teams' technical language and the customers' business language poses a threat to effective team-customer collaboration. We describe this language gap and the 'Translator' role that emerges to bridge it.
In distributed agile teams, people often use email as a knowledge sharing tool to clarify the project requirements (aka user stories). Knowledge about the project included in these emails is easily lost when recipient...
详细信息
ISBN:
(纸本)9783642130533
In distributed agile teams, people often use email as a knowledge sharing tool to clarify the project requirements (aka user stories). Knowledge about the project included in these emails is easily lost when recipients leave the project or delete emails for various reasons. However, the knowledge contained in the emails may be needed for useful purposes such as re-engineeringsoftware, changing vendor and so on. But, it is difficult to relate texts such as emails to certain topics because the relation is not explicit. In this paper, we present and evaluate a technique for automatically relating emails with user stories based on their text and context similarity. agile project management tools can use this technique to automatically build a knowledge base that is otherwise costly to produce and maintain.
Since late 2007 the software development teams at Codeweavers UK have been incrementally improving their ability to deliver motor finance and insurance web services. this two-year journey has taken the company from ch...
详细信息
ISBN:
(纸本)9783642130533
Since late 2007 the software development teams at Codeweavers UK have been incrementally improving their ability to deliver motor finance and insurance web services. this two-year journey has taken the company from chaos to kanban-style single-piece flow, including Scrum briefly along the way. this paper charts that journey, showing the benefits gained from a simple "inspect and adapt" cycle in which the teams tackled their biggest problem at each stage.
software product lines - families of similar but not identical software products - need to address the issue of feature variability. that is, a single feature might require various implementations for different custom...
详细信息
ISBN:
(纸本)9783642130533
software product lines - families of similar but not identical software products - need to address the issue of feature variability. that is, a single feature might require various implementations for different customers. Also, features might need optional extensions that are needed by some but not all products. software product line engineering manages variability by conducting a thorough domain analysis upfront during the planning phases. However, upfront, heavyweight planning approaches are not well-aligned withthe values of minimalistic practices like XP where bottom-up, incremental development is common. In this paper, we introduce a bottom-up, test-driven approach to introduce variability to systems by reactively refactoring existing code. We support our approach with an eclipse plug-in to automate the refactoring process. We evaluate our approach by a case study to determine the feasibility and practicality of the approach.
暂无评论