Informacja

Drogi użytkowniku, aplikacja do prawidłowego działania wymaga obsługi JavaScript. Proszę włącz obsługę JavaScript w Twojej przeglądarce.

English (EN)·Polski (PL)·Yкраїнський (UK)
Przejdź do strony domowej biblioteki Centralna Biblioteka Wojskowa Link otwiera się w nowym oknie Logo biblioteki Prolib Integro - strona głównaCentralna Biblioteka Wojskowa

Wyszukujesz frazę "project management software" wg kryterium: Temat

  Lista filtrów
Wyrównaj
    Wyświetlanie 1-4 z 4
    Tytuł:
    The Role of Organisational Phenomena in Software Cost Estimation: A Case Study of Supporting and Hindering Factors
    Autorzy:
    Rahikkala, J.
    Hyrynsalmi, S.
    Leppänen, V.
    Porres, I
    Powiązania:
    https://bibliotekanauki.pl/articles/384055.pdf
    Data publikacji:
    2018
    Wydawca:
    Politechnika Wrocławska. Oficyna Wydawnicza Politechniki Wrocławskiej
    Tematy:
    software cost estimation
    project management
    project success
    top management
    organisational factors
    software improvement
    software process maturity
    case study
    Opis:
    Despite the fact that many researchers and practitioners agree that organisational issues are equally important as technical issues from the software cost estimation (SCE) success point of view, most of the research focus has been put on the development of methods, whereas organisational factors have received surprisingly little academic scrutiny. This study aims to identify organisational factors that either support or hinder meaningful SCE, identifying their impact on estimation success. Top management’s role is specifically addressed. The study takes a qualitative and explorative case study based approach. In total, 18 semi-structured interviews aided the study of three projects in three organisations. Hence, the transferability of the results is limited. The results suggest that the role of the top management is important in creating prerequisites for meaningful estimation, but their day-to-day participation is not required for successful estimation. Top management may also induce undesired distortion in estimation. Estimation maturity and estimation success seem to have an interrelationship with software process maturity, but there seem to be no significant individual organisational factors, which alone would make estimation successful. Our results validate several distortions and biases reported in the previous studies, and show the SCE research focus has remained on methodologies and technical issues.
    Źródło:
    e-Informatica Software Engineering Journal; 2018, 12, 1; 167-198
    1897-7979
    Pojawia się w:
    e-Informatica Software Engineering Journal
    Dostawca treści:
    Biblioteka Nauki
    Artykuł
    Tytuł:
    Risks characteristic to Agile project management methodologies and responses to them
    Autorzy:
    Walczak, W.
    Kuchta, D.
    Powiązania:
    https://bibliotekanauki.pl/articles/406318.pdf
    Data publikacji:
    2013
    Wydawca:
    Politechnika Wrocławska. Oficyna Wydawnicza Politechniki Wrocławskiej
    Tematy:
    risk
    risk management
    agile software development
    agile project management
    Opis:
    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.
    Źródło:
    Operations Research and Decisions; 2013, 23, 4; 75-95
    2081-8858
    2391-6060
    Pojawia się w:
    Operations Research and Decisions
    Dostawca treści:
    Biblioteka Nauki
    Artykuł
    Tytuł:
    Milestone-Oriented Usage of Key Performance Indicators – An Industrial Case Study
    Autorzy:
    Staron, M.
    Niesel, K.
    Bauman, N.
    Powiązania:
    https://bibliotekanauki.pl/articles/953064.pdf
    Data publikacji:
    2018
    Wydawca:
    Politechnika Wrocławska. Oficyna Wydawnicza Politechniki Wrocławskiej
    Tematy:
    software metrics
    key performance indicator
    project management
    case study
    Opis:
    Background: Key Performance Indicators are a common way of quantitative monitoring of project progress in modern companies. Although they are widely used in practice, there is little evidence on how they are set, and how many of them are used in large product development projects. Goal: The goal of this paper is to explore how KPIs are used in practice in a large company. In particular, it is explored whether KPIs are used continuously or only during short, predefined periods of time. It is also explored whether software-related KPIs are reported differently from non-software-related KPIs. Method: A case study of 12 projects at the Volvo Car Group in Sweden was conducted. The data from the project progress reporting on tools was collected and triangulated with data from interviews conducted with experts from the company. Results: KPIs are reported mostly before the milestones and the manual assessment of their status is equally important as the automated data provision in the KPI reporting system. The trend of reporting software-related KPIs is very similar to the non-software-related KPIs. Conclusions: Despite the documented good practices of using KPIs for project monitoring, it is difficult to develop a clear status-picture solely using quantitative data from progress reporting tools. It was also shown that the trends in reporting the software-related KPIs are similar to the trends in reporting the non-software related KPIs.
    Źródło:
    e-Informatica Software Engineering Journal; 2018, 12, 1; 217-236
    1897-7979
    Pojawia się w:
    e-Informatica Software Engineering Journal
    Dostawca treści:
    Biblioteka Nauki
    Artykuł
    Tytuł:
    Technical Debt Aware Estimations in Software Engineering: a Systematic Mapping Study
    Autorzy:
    Klimczyk, Paweł
    Madeyski, Lech
    Powiązania:
    https://bibliotekanauki.pl/articles/384112.pdf
    Data publikacji:
    2020
    Wydawca:
    Politechnika Wrocławska. Oficyna Wydawnicza Politechniki Wrocławskiej
    Tematy:
    software estimation
    technical debt
    project management
    decision making
    change impact
    Opis:
    Context: The Technical Debt metaphor has grown in popularity. More software is being created and has to be maintained. Agile methodologies, in particular Scrum, are widely used by development teams around the world. Estimation is an often practised step in sprint planning. The subject matter of this paper is the impact technical debt has on estimations. Objective: The goal of this research is to identify estimation problems and their solutions due to previously introduced technical debt in software projects. Method: The Systematic mapping study (SMS) method was applied in the research. Papers were selected from the popular digital databases (IEEE, ACM, Scopus, etc.) using defined search criteria. Afterwards, a snowballing procedure was performed and the final publication set was filtered using inclusion/exclusion criteria. Results: 42 studies were selected and evaluated. Five categories of problems and seven proposed solutions to the problems have been extracted from the papers. Problems include items related to business perspective (delivery pressure or lack of technical debt understanding by business decision-makers) and technical perspective (difficulties in forecasting architectural technical debt impact or limits of source code analysis). Solutions were categorized in: more sophisticated decision-making tools for business managers, better tools for estimation support and technical debt management tools on an architectural-level, portfolio approach to technical debt, code audit and technical debt reduction routine conducted every sprint. Conclusion: The results of this mapping study can help taking the appropriate approach in technical debt mitigation in organizations. However, the outcome of the conducted research shows that the problem of measuring technical debt impact on estimations has not yet been solved. We propose several directions for further investigation. In particular, we would focus on more sophisticated decision-making tools.
    Źródło:
    e-Informatica Software Engineering Journal; 2020, 14, 1; 61-76
    1897-7979
    Pojawia się w:
    e-Informatica Software Engineering Journal
    Dostawca treści:
    Biblioteka Nauki
    Artykuł
      Wyświetlanie 1-4 z 4

      Ta witryna wykorzystuje pliki cookies do przechowywania informacji na Twoim komputerze. Pliki cookies stosujemy w celu świadczenia usług na najwyższym poziomie, w tym w sposób dostosowany do indywidualnych potrzeb. Korzystanie z witryny bez zmiany ustawień dotyczących cookies oznacza, że będą one zamieszczane w Twoim komputerze. W każdym momencie możesz dokonać zmiany ustawień dotyczących cookies