the daily stand-up meeting is a widely used practice. However, what is more uncertain is how valuable the practice is to team members. We invited professional developers of a programming forum to a survey and obtained...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
the daily stand-up meeting is a widely used practice. However, what is more uncertain is how valuable the practice is to team members. We invited professional developers of a programming forum to a survey and obtained 221 responses. Results show that the daily stand-up meeting was used by 87% of those who employ agile methods. We found that even though the respondents on average were neutral towards the practice, the majority were either positive or negative. Junior developers were most positive and senior developers and members of large teams most negative. We argue that the value of the practice should be evaluated according to the team needs. Further, more work is needed to understand why senior developers do not perceive the meetings as valuable and how to apply the practice successfully in large teams.
Technical Debt is a metaphor that has, in recent years, helped developers to think about and to monitor software quality. the metaphor refers to flaws in software (usually caused by shortcuts to save time) that may af...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
Technical Debt is a metaphor that has, in recent years, helped developers to think about and to monitor software quality. the metaphor refers to flaws in software (usually caused by shortcuts to save time) that may affect future maintenance and evolution. We conducted an empirical study in an academic environment, with nine teams of graduate and undergraduate students during two offerings of a laboratory course on extremeprogramming (XP Lab). the teams had a comprehensive lecture about several alternative ways to identify and manage Technical Debt. We monitored the teams, performed interviews, did close observations and collected feedback. the results show that the awareness of Technical Debt influences team behavior. Team members report thinking and discussing more about software quality after becoming aware of Technical Debt in their projects.
agilesoftware Development (ASD) is becoming more popular in all fields of industry. For an agile transformation, organizations need to continuously improve their established approaches to Requirements engineering (RE...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
agilesoftware Development (ASD) is becoming more popular in all fields of industry. For an agile transformation, organizations need to continuously improve their established approaches to Requirements engineering (RE) as well as their approaches to software development. this is accompanied by some challenges in terms of agile RE. the main objective of this paper is to identify the most important challenges in agile RE industry has to face today. therefore, we conducted an iterative expert judgement process with 26 experts in the field of ASD, comprising three complementary rounds. In sum, we identified 20 challenges in three rounds. Six of these challenges are defined as key challenges. Based on the results, we provide options for dealing withthose key challenges by means of agile techniques and tools. the results show that the identified challenges are often not limited to ASD, but they rather refer to software development in general. therefore, we can conclude that organizations still struggle withagile transition and understanding agile values, in particular, in terms of stakeholder and user involvement.
Security testing can broadly be described as (1) the testing of security requirements that concerns confidentiality, integrity, availability, authentication, authorization, nonrepudiation and (2) the testing of the so...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
Security testing can broadly be described as (1) the testing of security requirements that concerns confidentiality, integrity, availability, authentication, authorization, nonrepudiation and (2) the testing of the software to validate how much it can withstand an attack. agile testing involves immediately integrating changes into the main system, continuously testing all changes and updating test cases to be able to run a regression test at any time to verify that changes have not broken existing functionality. software companies have a challenge to systematically apply security testing in their processes nowadays. there is a lack of guidelines in practice as well as empirical studies in real-world projects on agile security testing;industry in general needs a more systematic approach to security. the findings of this research are not surprising, but at the same time are alarming. the lack of knowledge on security by agile teams in general, the large dependency on incidental pen-testers, and the ignorance in static testing for security are indicators that security testing is highly under addressed and that more efforts should be addressed to security testing in agile teams.
Context: Eliciting requirements from customers is a complex task. In agileprocesses, the customer talks directly withthe development team and often reports requirements in an unstructured way. the requirements elici...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
Context: Eliciting requirements from customers is a complex task. In agileprocesses, the customer talks directly withthe development team and often reports requirements in an unstructured way. the requirements elicitation process is up to the developers, who split it into user stories by means of different techniques. Objective: We aim to compare the requirements decomposition process of an unstructured process and three agileprocesses, namely XP, Scrum, and Scrum with Kanban. Method: We conducted a multiple case study with a replication design, based on the project idea of an entrepreneur, a designer with no experience in software development. Four teams developed the project independently, using four different development processes. the requirements were elicited by the teams from the entrepreneur, who acted as product owner and was available to talk withthe four groups during the project. Results: the teams decomposed the requirements using different techniques, based on the selected development process. Conclusion: Scrum with Kanban and XP resulted in the most effective processes from different points of view. Unexpectedly, decomposition techniques commonly adopted in traditional processes are still used in agileprocesses, which may reduce project agility and performance. therefore, we believe that decomposition techniques need to be addressed to a greater extent, both from the practitioners' and the research points of view.
While the effects of mindfulness are increasingly explored across different fields, little is known about the application of these practices in agile project teams. In this paper we report on a rigorous controlled tri...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
While the effects of mindfulness are increasingly explored across different fields, little is known about the application of these practices in agile project teams. In this paper we report on a rigorous controlled trial executed to understand the impact of the three minute breathing exercise on the perceived effectiveness of stand-up meetings. We compare (1) an active group using a three minute breathing exercise, to (2) a placebo, and (3) a control group in 3 organizations and 8 teams with over 152 measurements. Our findings indicate an immediate positive impact on perceived effectiveness, decision-making and improved listening in the active groups compared to the placebo and natural history groups. We provide a preliminary agenda for future research based on our findings and previous evidence from other fields.
software startups operate under various uncertainties and the demand on their ability to deal with change is high. agile methods are considered a suitable and viable development approach for them. However, the competi...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
software startups operate under various uncertainties and the demand on their ability to deal with change is high. agile methods are considered a suitable and viable development approach for them. However, the competing needs for speed and quality may render certain agile practices less suitable than others in the startup context. the adoption of agile practices can be further complicated in software startups that adopt the Lean Startup approach. To make the best of agile practices, it is necessary to first understand whether and how they are used in software startups. this study targets at a better understanding of the use of agile practices in software startups, with a particular focus on lean startups. Based on a large survey of 1526 software startups, we examined the use of five agile practices, including quality related (regular refactoring and test first), speed related (frequent release and agile planning) and communication practice (daily standup meeting). the findings show that speed related agile practices are used to a greater extent in comparison to quality practices. Daily standup meeting is least used. software startups who adopt the Lean Startup approach do not sacrifice quality for speed more than other startups do.
A retrospective is a standard agile meeting practice designed for agilesoftware teams to reflect and tune their process. Despite its integral importance, we know little about what aspects are focused upon during retr...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
A retrospective is a standard agile meeting practice designed for agilesoftware teams to reflect and tune their process. Despite its integral importance, we know little about what aspects are focused upon during retrospectives and how reflection occurs in this practice. We conducted Case Study research involving data collected from interviews of sixteen software practitioners from four agile teams and observations of their retrospective meetings. We found that the important aspects focused on during the retrospective meeting include identifying and discussing obstacles, discussing feelings, analyzing previous action points, identifying background reasons, identifying future action points and generating a plan. Reflection occurs when the agile teams embody these aspects within three levels of reflection: reporting and responding, relating and reasoning, and reconstructing. Critically, we show that agile teams may not achieve all levels of reflection simply by performing retrospective meetings. One of the key contributions of our work is to present a reflection framework for agile retrospective meetings that explains and embeds three levels of reflection within the five steps of a standard agile retrospective. agile teams can use this framework to achieve better focus and higher levels of reflection in their retrospective meetings.
Avionic systems for communication, navigation, and flight control, and many other functions are complex and crucial components of any modern aircraft. Present day avionic systems are increasingly based on computers an...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
Avionic systems for communication, navigation, and flight control, and many other functions are complex and crucial components of any modern aircraft. Present day avionic systems are increasingly based on computers and a growing percentage of system complexity can be attributed to software. An error in the software of a safety-critical avionic system could lead to a catastrophic event, such as multiple deaths and loss of the aircraft. To demonstrate compliance with airworthiness requirements, certification agencies accept the use of RTCA document DO-178 for the software development. Avionics software development is typically complex and is traditionally reliant on a strict plan-driven development process, characterized by early fixture of detailed requirements and late production of working software. In this process, requirement changes and solving software errors can lead to much rework, and create a risk of budget and schedule overruns. this raises the question whether avionics software development could benefit from the application of agile approaches. Based on the results of three activities: (1) a literature study on industrial experience withthe use of agile methods in a DO-178 context, (2) an expert assessment of the DO-178 objectives, and (3) a survey conducted among European avionics industry, an outline is presented of an agile development process, where Scrum is extended to achieve the DO-178 objectives. the application of agile methods is expected to support frequent delivery of working software and ability to respond to changes, resulting in reduced risk of budget and schedule overruns.
Knowledge is a core resource for agile organisations that is transformed into products and services during the development process. Sharing of knowledge is essential across any organisation, and it has been claimed th...
详细信息
ISBN:
(数字)9783319576336
ISBN:
(纸本)9783319576336;9783319576329
Knowledge is a core resource for agile organisations that is transformed into products and services during the development process. Sharing of knowledge is essential across any organisation, and it has been claimed that the software industry requires more knowledge management than any other sector. agile methodologies concentrate on team level collaboration, and some techniques for inter-team knowledge sharing have also proved to be successful. But these techniques focus on within-team and between-team knowledge sharing rather than knowledge sharing across the organisation. this paper presents the results of a survey with81 responses on organisational knowledge sharing in a multinational agile company. the survey focuses on three aspects of knowledge sharing: within agile teams, beyond the team with company colleagues, and with customers. It concentrates on knowledge sharing practices, ease of knowledge sharing and motivation for knowledge sharing. Summary statistics, regression, and test of equity are used as analysis techniques. Results show that knowledge sharing with team members is significantly easier than with customers or company colleagues beyond their team. In addition, using agile practices improves ease of knowledge sharing within teams but not with customers or colleagues. Extrinsic motivators need to be in place to encourage knowledge sharing across the organisation, especially where such knowledge sharing is not an automatic consequence of completing the work.
暂无评论