Purpose – A cost estimate is considered to have a high impact on software project success. Because of this, different methodologies for creating an accurate estimate have been studied over decades. Many methodologies produce accurate results, when used properly. However, software projects still suffer from inaccurate estimates. The disparity may result from organisational hindrances. This paper focuses on top management support (TMS) for software cost estimation (SCE). The purpose of this paper is to identify current practices and attitudes of top management involvement in SCE, and to analyse the relationship between these two and project success. Design/methodology/approach – A list of 16 TMS practices for SCE has been developed. A survey was conducted to capture the frequency of use and the experienced importance of support practices. Data has been collected from 114 software professionals in Finland. Correlations between the frequency of use, attitudes and project success were analysed. Findings – Top management invests a significant amount of attention in SCE. The extent of use and experienced importance do not correlate strongly with each other or project success. Research limitations/implications – The results may lack generalisability. Researchers are encouraged to validate the results with further studies. Practical implications – Software professionals invite senior managers to participate in SCE. A list of practices for participating is provided. Originality/value – This paper suggests a list of 16 TMS practices for SCE. The paper also reports on the extent of use and experienced importance of practices, and the correlations between these two and project success.
Over the past 20 years, open source has become a widely adopted approach to develop software. Code repositories provide software to power cars, phones, and other things that are considered proprietary. In parallel, proprietary development has evolved from rigid, centralized waterfall approaches to agile, iterative development. In this paper, we share our experiences regarding this co-evolution of open and closed source from the viewpoints of tools, practices, and organizing the development work, concluding that today's bazaars and cathedrals have much more common characteristics than those that separate them.
Now, a few weeks before defending my thesis in front of the public, is a good time to stop and think why did I do it. I'm 45 years old, working long days in a busy company, and have a family and hobbies. It's been busy. However, I've always enjoyed learning new things. Also, I value education, and I admire researchers and practitioners, who discover novelties, contribute and make a difference. With my thesis, I wanted to make sure that I continue learning. I also had a dream of contributing myself. Now, that dream comes true. I wish that my work could help software professionals, even a little, to run more successful projects. That's why I did it.Good things get even better in good company. I've had a dream team backing me and my work during the process, and I've enjoyed every bit of it. Ville, please accept my gratitude for your effort, persistence, practicality, wisdom and advise, among many other things. Without you and your team this wouldn't have been possible. Sami, you taught me everything, and showed that science can be fun. I'll always be grateful to you for being a mentor and companion to me during the journey. I'd also like to thank Jukka Teuhola for planting the seed for all of this during my Master's studies.My sincere thanks also go to prof. Markku Oivo and prof. Jürgen Munch, who acted as pre-examiners to my thesis. Your suggestions were welcome. I'm also thankful to prof. Kari Systä for accepting the demanding role of the opponent, and taking the time to review my work. Of other scholars, I'd like to thank prof. Tommi Mikkonen for minding and supporting, prof. Marko Seppänen for the NPD stuff, and prof. Ivan Porres for methodology ninjutsu. Jukka and Johannes, thanks for the stats, you rock! Joonas, thanks for making it possible to combine the research with my position as Vaadin's COO. Tapio, thanks for your generous offer, which I happily accepted, to pay for the drinks consumed in the after party. I'd also like to thank N4S research programme for providing a superior framework for research, and methodology Table 3.3: Interviewees' roles in the company Role Department Length (min) CEO,
Open source repositories, by their nature, are open for study. This has inspired researchers to study them using various tools, leading to an established body of knowledge regarding how developers execute their work, communicate, and coordinate the effort. One flavor of open source community, which has received less attention, is hybrid open source, where developers and other stakeholders with various backgrounds exist. In this paper, we perform a sentiment analysis to a hybrid open source community, based on comments given when making commits. The goal is to understand if the community members behave differently, depending on their background in the company that owns the community IPR, being an independent contributor, or representing a collaborating organization. Based on the results, we find that there indeed is a clear difference in the sentiments, with in-house developers having a tendency to be more negative than independent developers, who in contrast express positive sentiments in their commit comments.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.