Wyniki wyszukiwania - Biblioteka Nauki

Nowa wersja platformy, zawierająca wyłącznie zasoby pełnotekstowe, jest już dostępna.
Przejdź na https://bibliotekanauki.pl

Ograniczanie wyników

Znaleziono wyników: 4

Liczba wyników na stronie

Wyniki wyszukiwania

Wyszukiwano:
w słowach kluczowych: agile software development

Sortuj według:

Ogranicz wyniki do:

Highly Automated Agile Testing Process: An Industrial Case Study

100%

Berłowski J. , Chruściel P. , Kasprzyk M. , Konaniec I. , Jureczko M.

2016

tom Vol. 10, nr 1

69--87

This paper presents a description of an agile testing process in a medium size software project that is developed using Scrum. The research methods used is the case study were as follows: surveys, quantifiable project data sources and qualitative project members opinions were used for data collection. Challenges related to the testing process regarding a complex project environment and unscheduled releases were identified. Based on the obtained results, we concluded that the described approach addresses well the aforementioned issues. Therefore, recommendations were made with regard to the employed principles of agility, specifically: continuous integration, responding to change, test automation and test driven development. Furthermore, an efficient testing environment that combines a number of test frameworks (e.g. JUnit, Selenium, Jersey Test) with custom-developed simulators is presented.

Risks characteristic to Agile project management methodologies and responses to them

100%

Walczak W. , Kuchta D.

tom Vol. 23, No. 4

75--95

Agile methods for project management are often treated as methods for mitigating risk. However, there is disagreement as to whether explicit methods of risk management should be used in projects which are executed according to Agile methodology or is the implicit risk management built into Agile methodologies sufficient. To contribute to the discussion, an attempt has been made to identify risks that are either caused by the introduction of an Agile methodology to a project or become more significant when such methodology is in use. If such risks exist, this would be evidence that explicit risk management is required, even in the case of Agile methodologies. The results of this research may be useful for any organization that is in the process of selecting a methodology for project management and is considering Agile methodologies.

Fixations in Agile Software Development Teams

100%

Borowa K. , Kamoda S. , Ogrodnik P. , Zalewski A.

Foundations of Computing and Decision Sciences

2023

tom Vol. 48, No. 1

3--18

Cognitive biases influence every human being, including the individuals that take part in the software development process. Fixation is a cognitive bias that occurs when one focuses too much on certain items, events, obstacles or activities. In this study, we examine whether agile team members fixate on any particular agile practices. Through a set of semi-structured interviews, we investigated the source of these fixations, their consequences, and then propose possible countermeasures. We found that practitioners tend to fixate on practices that give them a sense of being in control over the project (such as meetings or Scrum events), while neglecting the Agile Principles of self-organising teams and working at a sustainable pace. This resulted in a series of problems, such as futile attempts to control team members, oversharing information with the client, meetings becoming a form of interrogation, and others.

Assessment of PTC windchill in teaching the software development using the agile methodology

63%

Bołdak C.

Journal of Applied Computer Science

2014

tom Vol. 22, nr 1

7--27

In this work a description of using PTC Windchill Project Link in education of students of Computer Science during a practical course of the group software development is given. The students learn how to cooperate in construction of a software project according to SCRUM – one of the most commonly used agile software development methodologies. PTC Windchill is used to organize their work and to collect the process artifacts. After one semester experience, strong and weak points of this system are pointed out.