Thesis (M.Sc)--Athabasca University, 2005. / Includes bibliographical references (leaves 69-70).

none

Dissertation (Ph.D.)--Auburn University, 2007. / Abstract. Includes bibliographic references.

Thesis (M.Eng.) - Carleton University, 2006. / Includes bibliographical references (p. 157-163). Also available in electronic format on the Internet.

Introduction: As information technology has been developing so rapidly, it affects all business processes. Project management is also greatly affected, as organizations world-wide constantly strive for competitive advantage, major tools were produced and manage-ment control of project progress throughout their lifecycle is becoming increasingly recog-nized for its importance. Problem: The study of software project management tools has aroused a great deal of in-terest in modern research circles as well as inspired extensive research in the area of mana-gerial science. However, there still seems to be confusion, disagreement and limited re-search regarding these concepts of job performance. Purpose: The purpose of this thesis is to examine, how project management tools can af-fect the efficiency in a software development project. Efficiency will be measured by time, from project start to finish, human and financial resources. Method: An electronic qualitative and partly quantitative questionnaires were sent to three sampled companies. In each company one Web programmer, one project manager and one executive level employee had filled out the questionnaires. The acquired data was then ana-lysed in relation to the frame of reference. Frame of Reference: Theoretical framework is build on a literature within software pro-ject management field, Iron/Golden Triangle, Productivity Paradox, Technology Accep-tance Model, and Software Project Management. Conclusion: To conclude the results of the study, after analyzing the data gathered from various companies implementing JIRA has in all cases resulted in increased product quality, more efficient and faster communication, as well as lower product development costs. This means that implementing JIRA can be beneficial for time, money and quality of software development.

Thesis (M.S.)--West Virginia University, 2003. / Title from document title page. Document formatted into pages; contains x, 66 p. : ill. (some col.). Vita. Includes abstract. Includes bibliographical references (p. 43-44).

Thesis (M.S.)--West Virginia University, 2003. / Title from document title page. Document formatted into pages; contains ix, 161 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 49).

Procurando obter ganhos sustentáveis de produtividade e qualidade no desenvolvimento de software, diversos modelos, formas de organização do trabalho e abordagens inovadoras foram desenvolvidos para auxiliar os gerentes de projeto. O presente trabalho propõe um modelo de gerenciamento de projetos, baseado nas metodologias ágeis de desenvolvimento de software (Extreme Programming e o Scrum), e nos princípios e valores do pensamento enxuto, originado na manufatura automobilística japonesa. Após a proposição do modelo, ele é aplicado em um estudo de caso, avaliando os resultados obtidos na combinação entre as metodologias ágeis e nos princípios e valores da produção enxuta. Em seguida, este modelo é analisado qualitativamente com o intuito de determinar suas vantagens de utilização e seu escopo de aplicação. Para tanto, recorreu-se a uma avaliação do modelo proposto e o tradicional modelo cascata, ainda amplamente adotado no setor de software, e mapeando como este modelo contorna os problemas apontados na literatura, advindos da utilização do modelo cascata. / Looking for sustainable gains in productivity and quality in the development of software, several models, forms of work organization and innovative approaches were developed to support software development managers. The present work proposes a model of project management, based on agile software development methodologies (Extreme Programming and Scrum) and on lean principles and values borrowed from the Japanese automobile manufacturing. After describing the proposed model, it is applied in a case study, describing the results of combining the agile software development methodologies with the lean production principles and values. After this, the model is qualitatively analyzed to determine its advantages and its scope of application. For this, the proposed model is evaluated with the traditional waterfall model - until now widely adopted in the software industry - and mapping how it addresses problems, cited in the literature, derived from the use of the waterfall model.

Procurando obter ganhos sustentáveis de produtividade e qualidade no desenvolvimento de software, diversos modelos, formas de organização do trabalho e abordagens inovadoras foram desenvolvidos para auxiliar os gerentes de projeto. O presente trabalho propõe um modelo de gerenciamento de projetos, baseado nas metodologias ágeis de desenvolvimento de software (Extreme Programming e o Scrum), e nos princípios e valores do pensamento enxuto, originado na manufatura automobilística japonesa. Após a proposição do modelo, ele é aplicado em um estudo de caso, avaliando os resultados obtidos na combinação entre as metodologias ágeis e nos princípios e valores da produção enxuta. Em seguida, este modelo é analisado qualitativamente com o intuito de determinar suas vantagens de utilização e seu escopo de aplicação. Para tanto, recorreu-se a uma avaliação do modelo proposto e o tradicional modelo cascata, ainda amplamente adotado no setor de software, e mapeando como este modelo contorna os problemas apontados na literatura, advindos da utilização do modelo cascata. / Looking for sustainable gains in productivity and quality in the development of software, several models, forms of work organization and innovative approaches were developed to support software development managers. The present work proposes a model of project management, based on agile software development methodologies (Extreme Programming and Scrum) and on lean principles and values borrowed from the Japanese automobile manufacturing. After describing the proposed model, it is applied in a case study, describing the results of combining the agile software development methodologies with the lean production principles and values. After this, the model is qualitatively analyzed to determine its advantages and its scope of application. For this, the proposed model is evaluated with the traditional waterfall model - until now widely adopted in the software industry - and mapping how it addresses problems, cited in the literature, derived from the use of the waterfall model.

<p>Software projects are known for their failure rate, where many are being delivered late, over budget or being canceled while in development. The reason to it is changing requirements and intangibility of the software. Being so abstract it is difficult to imaging all the aspects of the software at the requirements stage. Also technology is playing a major role since processing power, storage space, and data transfer speeds are improving from year to year.</p><p>Agile methodologies are addressing projects with unclear requirements making process of implementing new specifications along the project much easier and less costly. However the success rate of the software projects did not improve much since the introduction of Agile methodologies. This thesis is looking at what type of projects fit different methodologies and what are factors which practitioners should take into account when selecting methodology for a particular project,</p><p>The thesis opens up with introduction which sets the research question and provides a brief background to the research topic. In subsequent chapter literature review is conducted to find out what does literature and other researchers have said on the same topic. Third chapter discusses underlying research philosophy and discusses the data collection tools. Next chapter discusses the findings of the research. Interviews has been conducted with project management professionals from Sweden, US, UK and Canada. It was identified through the analysis of patters that Agile methodologies are not well suited for projects involving databases, embedded development and computationally complex projects. Through the analysis of the questionnaire several project characteristics were identified which suit Agile methodologies better than traditional ones: unclear requirements, high risk of failure etc… In the last chapter the thesis concludes the findings and its theoretical and practical implications.</p>