Search

"Agile management methods" is a comprehensive guide to the principles and practices of agile management. The book is structured to provide readers with a thorough understanding of the philosophy and of the agile approach, as well as practical advice for implementing agile practices in a variety of settings. The book begins by introducing the core values and principles of agile management, highlighting the importance of collaboration, flexibility and continuous improvement. It explains how these values and principles can be applied to different types of projects and organizational structures. The second part of the book focuses on three key agile methods: Scrum, Kanban and DevOps. Readers will learn about the key features of each method, as well as how to use them effectively in different contexts. The author provides detailed guidance on how to set up and manage Scrum and Kanban boards, as well as how to implement DevOps practices to improve collaboration and efficiency. The third part of the book covers practical topics of agility, such as user stories, effort estimation, prioritization, and agile metrics. Readers will learn how to write effective user stories, estimate project effort using agile methods, prioritize tasks based on value, and measure progress using agile metrics. The final part of the book explores how agile methods are used in different settings, including enterprises, public sector organizations, educational institutions, etc. The author provides real-world examples of successful agile implementations, as well as tips for overcoming common challenges and obstacles., To βιβλίο με τίτλο «Ευέλικτες μέθοδοι διοίκησης και διαχείρισης έργων» είναι ένας ολοκληρωμένος οδηγός για τις αρχές και τις πρακτικές της ευέλικτης διοίκησης. Το βιβλίο παρουσιάζει στους αναγνώστες του την ευέλικτη φιλοσοφία, τις αξίες και τις αρχές, καθώς και πρακτικές συμβουλές για την εφαρμογή των ευέλικτων μεθόδων σε διάφορα περιβάλλοντα. Το βιβλίο ξεκινά παρουσιάζοντας στο πρώτο μέρος τις βασικές αξίες και αρχές της ευέλικτης διοίκησης, συμπεριλαμβανομένης της σημασίας της συνεργασίας, της ευελιξίας και της συνεχούς βελτίωσης. Εξηγεί πώς αυτές οι αξίες και αρχές μπορούν να εφαρμοστούν σε διαφορετικούς τύπους έργων και οργανωτικών δομών. Το δεύτερο μέρος του βιβλίου επικεντρώνεται σε τρεις βασικές ευέλικτες μεθόδους: τις μεθόδους Scrum, Kanban και DevOps. Οι αναγνώστες θα μάθουν τα βασικά χαρακτηριστικά της κάθε μεθόδου, καθώς και πώς να τα χρησιμοποιούν αποτελεσματικά σε διαφορετικά πλαίσια. Ο συγγραφέας παρέχει λεπτομερείς οδηγίες σχετικά με τον τρόπο εφαρμογής των μεθόδων Scrum και Kanban, καθώς και τον τρόπο εφαρμογής πρακτικών DevOps για τη βελτίωση της συνεργασίας και της αποτελεσματικότητας. Το τρίτο μέρος του βιβλίου καλύπτει πρακτικά θέματα της ευέλικτης προσέγγισης, όπως τις ιστορίες χρηστών, την εκτίμηση της προσπάθειας έργων, την ιεράρχηση των προτεραιοτήτων και ευέλικτες μετρικές. Συνεπώς, οι αναγνώστες θα μάθουν πώς να γράφουν κατάλληλες ιστορίες χρηστών, να εκτιμούν την προσπάθεια του έργου χρησιμοποιώντας ευέλικτες μεθόδους, να ιεραρχούν τις εργασίες με βάση την αξία τους και να μετρούν την πρόοδο των εργασιών χρησιμοποιώντας ευέλικτες μετρικές. Το τελευταίο μέρος του βιβλίου διερευνά πώς οι ευέλικτες μέθοδοι χρησιμοποιούνται σε διαφορετικούς κλάδους, συμπεριλαμβανομένων των επιχειρήσεων, των οργανισμών του δημόσιου τομέα, στην εκπαίδευση κ.ά. Ο συγγραφέας παρουσιάζει πραγματικά παραδείγματα επιτυχημένων ευέλικτων εφαρμογών, καθώς και συμβουλές για την αντιμετώπιση κοινών προκλήσεων και εμποδίων.

Software project scope definition is complicated due to the diversity and magnitude of the information needed. An inadequate scope definition often results in project failure as it continues to emerge as the major cause of delays, changes/rework, and cost and schedule overruns. Literature mentions different tools and methods to verify, quantify, and control software scope definition. However, none of these methods and tools help in defining a complete scope. Since a well-defined scope in the early stages is a core ingredient for project success, therefore, previously we developed a method that includes 45 elements of the software project scope definition. Although these elements are noteworthy for project scope, some may influence others; and should be concentrated on more when defining the scope of the software projects. The objective of this present study is that it builds on our previous research and uses Interpretive Structural Modeling (ISM) to extract the interrelationships among the elements and Decision Making Trial and Evaluation Laboratory (DEMATEL) to determine the intensity of these relationships. Experts from academia and the software development industry were consulted to identify the relationships among the elements. ISM-DEMATEL approach indicates that the project manager’s competence is the main driver. Further, requirements, stakeholders’ expectations, cost estimates, project schedule, resource estimation, project summary, communication, consultation, top management support are among the most influential elements that are critical to focus on. Moreover, the findings of the study provide project managers with a better understanding of the elements and their interconnections thus, helping in achieving a better scope definition.

Failure of IT projects has risen to become an eyesore for most organisations. This is often attributed to the ‘mum effect’- an individual’s reluctance to report the exact position of troubled software projects. With the increasing digitalization of operations by most State Universities in Zimbabwe, the mum effect has the potential to rise to exponential proportions. Guided by the Design Science approach data was gathered from an intensity sample of 15 participants comprising 7 software project team members, 3 ICT project managers, and 5 users of the system drawn from three Zimbabwean state universities. The data collection was done using key informant interviews and focus group discussions. Data were analysed using thematic analysis and NVivo (version 11) software was used to store, organise, and code data transcripts. Factors suppressing Bad News Reporting were grouped into three broad categories which included organisational factors, personal factors, and situational factors. The findings suggest the need to incorporate these multi-level factors in the design and implementation of software projects if they are to be efficacious. This study recommends the establishment of clear channels of communication to manage bad news reporting and creating formal structures that function outside the traditional organisational hierarchy to convey information regarding anomalies. This study contributes to practice by providing appropriate interventions based on empirical evidence based on the centrality of software project team members’ insights, experiences as well as practices.

Context: The definition and prioritization of indicators is now a common reality and an integral part of the evolution of the strategic, technical and business processes of any organization, whether public or private. Purpose: This paper proposes a new model regarding the definition and prioritization of indicators. Herein, we also investigate the definition and prioritization models currently adopted by academia and industry, and analyze the context of the proposed strategies against the traditional view of indicator definition currently adopted. In addition, we conducted a survey with organizations that had well-defined indicator management processes, seeking to identify customer expectations with a new indicator management model proposed by this work. Method: To gather evidence, we defined a methodology that relates the literature review and an exploratory case study with the application of an experiment. Driven by a set of research questions, this methodology comprised four main phases: planning, literature review, experiment execution and documentation of results. The method used is supported by some techniques, such as design thinking, design sprint and the Cynefin framework. Results: The analysis of the results was carried out in two different ways: Through the verification of the achievement of specific objectives and through a questionnaire applied to assess the degrees of perception of all employees who participated in the work. Regarding the specific objectives, it is clear that most of the objectives were achieved. Regarding the applied questionnaire, it is clear that, although the collaborators did not have adequate knowledge regarding the conceptual and practical aspects of some approaches used in the proposed model, there was a general perception that the model, in fact, supported top management for decision making. For professionals, the proposed model has a restricted scope; that is, it does not serve all types of organizations. Conclusion: The model proposed in this work proved to be effective, considering that the indicators were defined, prioritized and optimized, with a focus on the user experience. As future work, we intend to expand the scope of the model’s performance, evaluating business indicators alongside IT indicators.

Dissertation presented as the partial requirement for obtaining a Master's degree in Information Management, specialization in Information Systems and Technologies Management Defect detection in software is the procedure to identify parts of software that may comprise defects. Software companies always seek to improve the performance of software projects in terms of quality and efficiency. They also seek to deliver the soft-ware projects without any defects to the communities and just in time. The early revelation of defects in software projects is also tried to avoid failure of those projects, save costs, team effort, and time. Therefore, these companies need to build an intelligent model capable of detecting software defects accurately and efficiently. This study seeks to achieve two main objectives. The first goal is to build a statistical model to identify the critical defect factors that influence software projects. The second objective is to build a statistical model to reveal defects early in software pro-jects as reasonable accurately. A bibliometric map (VOSviewer) was used to find the relationships between the common terms in those domains. The results of this study are divided into three parts: In the first part The term "software engineering" is connected to "cluster," "regression," and "neural network." Moreover, the terms "random forest" and "feature selection" are connected to "neural network," "recall," and "software engineering," "cluster," "regression," and "fault prediction model" and "software defect prediction" and "defect density." In the second part We have checked and analyzed 29 manuscripts in detail, summarized their major contributions, and identified a few research gaps. In the third part Finally, software companies try to find the critical factors that affect the detection of software defects and find any of the intelligent or statistical methods that help to build a model capable of detecting those defects with high accuracy. Two statistical models (Multiple linear regression (MLR) and logistic regression (LR)) were used to find the critical factors and through them to detect software defects accurately. MLR is executed by using two methods which are critical defect factors (CDF) and premier list of software defect factors (PLSDF). The accuracy of MLR-CDF and MLR-PLSDF is 82.3 and 79.9 respectively. The standard error of MLR-CDF and MLR-PLSDF is 26% and 28% respectively. In addition, LR is executed by using two methods which are CDF and PLSDF. The accuracy of LR-CDF and LR-PLSDF is 86.4 and 83.8 respectively. The standard error of LR-CDF and LR-PLSDF is 22% and 25% respectively. Therefore, LRCDF outperforms on all the proposed models and state-of-the-art methods in terms of accuracy and standard error.

Mahmoud, A. N., & Santos, V. (2021). Statistical Analysis for Revealing Defects in Software Projects: Systematic Literature Review. International Journal of Advanced Computer Science and Applications, 12(11), 237-249. https://doi.org/10.14569/IJACSA.2021.0121128 Defect detection in software is the procedure to identify parts of software that may comprise defects. Software companies always seek to improve the performance of software projects in terms of quality and efficiency. They also seek to deliver the soft-ware projects without any defects to the communities and just in time. The early revelation of defects in software projects is also tried to avoid failure of those projects, save costs, team effort, and time. Therefore, these companies need to build an intelligent model capable of detecting software defects accurately and efficiently. The paper is organized as follows. Section 2 presents the materials and methods, PRISMA, search questions, and search strategy. Section 3 presents the results with an analysis, and discussion, visualizing analysis and analysis per topic. Section 4 presents the methodology. Finally, in Section 5, the conclusion is discussed. The search string was applied to all electronic repositories looking for papers published between 2015 and 2021, which resulted in 627 publications. The results focused on finding three important points by linking the results of manuscript analysis and linking them to the results of the bibliometric analysis. First, the results showed that the number of defects and the number of lines of code are among the most important factors used in revealing software defects. Second, neural networks and regression analysis are among the most important smart and statistical methods used for this purpose. Finally, the accuracy metric and the error rate are among the most important metrics used in comparisons between the efficiency of statistical and intelligent models. publishersversion published

In recent years, one of the most important topics in the field of software development projects is rethinking success in context of increasing complexity and failure of software projects. Literature review shows that there is no clear line between success and failure, especially considering that a project can be both successful in one area and unsuccessful in another. In addition, the increasing complexity, context and broader conceptualization of projects, required both change in project and success definition. The aim of this paper is to perform literature review in field of software project success definition, as well as to propose a multidimensional construct that includes project management success, project success and strategic project success as three dimensions for measuring software's project success.

La propuesta de modelo de Gestión de Proyectos para la Fábrica de Software del Ministerio de Educación Nacional es motivada básicamente como una oportunidad para mejorar, estructura y organizar la gestión de los proyectos de nuevos desarrollos de software, así como su evolución y/o mejora, aumentando las capacidades y habilidades internas mediante la implementación y adopción de prácticas que faciliten la administración de proyectos. La administración de los proyectos mediante la implementación del modelo busca mejorar la eficiencia y la eficacia en la ejecución de los proyectos de forma tal que, generen valor y apoyen el cumplimiento de las metas y objetivos estratégico al Ministerio de Educación, lo anterior se logra con, la entrega de soluciones de software, estables, sostenibles en el tiempo, en los tiempos esperados y aún más importante, que cumplan con los requisitos y necesidades esperados por la entidad. Siendo así, en alineación con las buenas prácticas establecidas en el PMBOK (Project Management Institute, 2013) específicamente en su extensión para Software, se realiza la estructuración del modelo con base en el ciclo de vida de los proyectos, acorde a las particularidades que presenta el Ministerio de Educación al contar con un proveedor para la ejecución de la iniciativa de fábrica. Dicha alineación ha logrado que se pueda establecer los mecanismos que permitan estructurar claramente, el que hacer de la oficina de Tecnología y Sistemas de Información, identificar los recursos y roles necesarios para cumplir con el modelo, asignar claramente el nivel de responsabilidades y su intervención especifica durante el mismo, lo que evita considerablemente reprocesos, retrasos de los cronogramas y sobrecostos en los proyectos. The proposed Project Management model for the Software Factory of the Ministry of National Education is basically motivated as an opportunity to improve, structure and organize the management of new software development projects, as well as their evolution and / or improvement, increasing internal capacities and skills by implementing and adopting practices that facilitate project management. The administration of the projects through the implementation of the model seeks to improve the efficiency and effectiveness in the execution of the projects in such a way that they generate value and support the fulfillment of the goals and strategic objectives of the Ministry of Education, the above is achieved with , the delivery of software solutions, stable, sustainable over time, in the expected times and even more importantly, that meet the requirements and needs expected by the entity. Thus, in alignment with the good practices established in the PMBOK (Project Management Institute, 2013) specifically in its extension for Software, the model is structured based on the life cycle of the projects, according to the particularities that it presents. the Ministry of Education by having a supplier for the execution of the factory initiative. This alignment has made it possible to establish the mechanisms that allow a clear structure, what to do of the Office of Technology and Information Systems, identify the resources and roles necessary to comply with the model, clearly assign the level of responsibilities and their specific intervention. during it, which considerably avoids rework, schedule delays and cost overruns in projects. Magíster en Gerencia de Sistemas de Información y Proyectos Tecnológicos Maestría

Está investigación pretende analizar la relación entre las prácticas ágiles de Scrum asociados al éxito de los proyectos de Software por la compañía Thomas MTI, la cual está dedicada a prestar servicios para la administración y custodia de la información desde hace 65 años y actualmente se encuentra ubicada en la ciudad de Bogotá. Es necesario extraer conceptos relevantes de los resultados obtenidos con el fin generalizar los resultados de los estudios cualitativos de referencia expuestos por diferentes autores en la literatura (Boehm & Turner, 2005); (Dyba & Dingsøyr, 2008); (Kettunen, 2009); (Hoda et al., 2010) y (Azanha et al., 2017), por tanto, se realizó una investigación con un enfoque cuantitativo, alcance correlacional y diseño no experimental transversal. Por población objetivo se tomarán aquellas personas que participaron en proyectos que apliquen o utilicen prácticas ágiles de la metodología Scrum en la compañía Thomas MTI. This research aims to analyze the relationship between agile Scrum practices associated with the success of Software projects by the Thomas MTI company, which has been dedicated to providing services for the administration and custody of information for 65 years and is currently located in the city of Bogota. It is necessary to extract relevant concepts from the results obtained in order to generalize the results of the qualitative reference studies presented by different authors in the literature (Boehm & Turner, 2005); (Dyba & Dingsøyr, 2008); (Kettunen, 2009); (Hoda et al., 2010) and (Azanha et al., 2017), therefore, an investigation was carried out with a quantitative approach, correlational scope and non-experimental cross-sectional design. By target population, those people who participated in projects that apply or use agile practices of the Scrum methodology in the Thomas MTI company will be taken. Magíster en Gerencia de Proyectos Maestría

The study presented in this paper was developed in an academic environment. All subjects involved in this research are enrolled in the Information Systems Master’s Degree of the University of Minho. The main objective of this study is to demonstrate the need for the continuity of studies about the risks presented in software development projects. For this purpose, we analyzed more than four hundred risks and about one hundred problems faced and documented by the working groups. With the collected data we defined a list of twenty risks and conducted a comparative study of these risks with others already formalized in previous industrial studies. The comparison data was analyzed and interpreted, and important conclusions were made. FCT – Fundação para a Ciência e Tecnologia within the R&D Units Project Scope: UIDB/00319/2020 info:eu-repo/semantics/publishedVersion

There is a lack in research on the perspectives of different managerial roles on data about software projects in software analytics tools, such as the perspectives of chief financial officers (CFOs), chief executive officers (CEOs) and compliance officers. Today, software analytics tools are mainly developed to address the needs of technical stakeholders such as developers, but research shows that there exist potentials of expanding this technical users’ scope of focus to also include higher level stakeholders, such as managers. The goal of this study is to explore what managers working in software development organizations consider to be useful data to have about software projects in software analytics tools, as well as examining how they want data about software projects to be presented to them in such tools. This study was done in four steps. First, a literature review was conducted. Second, a questionnaire was conducted with four CFOs, one CEO and one compliance officer working in six different Swedish software development organizations. Third, semi-structured interviews were conducted with three CFOs, one CEO and one compliance officer working in five different Swedish software development organizations. Fourth, a visual prototype simulating a software analytics tool was constructed based on the data gathered from the interviews. The result of this study shows that abstraction, limitation, and visualization of data about software projects, as well as presentation of useful data in software analytics tools that support the work tasks of managers, is helpful in addressing the perspectives and views of the target group.

Software development encompasses many collaborative tasks in which usually several persons are involved. Close collaboration and the synchronization of different members of the development team require effective communication. One established communication channel are meetings which are, however, often not as effective as expected. Several approaches already focused on the analysis of meetings to determine the reasons for inefficiency and dissatisfying meeting outcomes. In addition to meetings, text-based communication channels such as chats and e-mails are frequently used in development teams. Communication via these channels requires a similar appropriate behavior as in meetings to achieve a satisfying and expedient collaboration. However, these channels have not yet been extensively examined in research. In this paper, we present an approach for analyzing interpersonal behavior in text-based communication concerning the conversational tone, the familiarity of sender and receiver, the sender's emotionality, and the appropriateness of the used language. We evaluate our approach in an industrial case study based on 1947 messages sent in a group chat in Zulip over 5.5 months. Using our approach, it was possible to automatically classify written sentences as positive, neutral, or negative with an average accuracy of 62.97% compared to human ratings. Despite this coarse-grained classification, it is possible to gain an overall picture of the adequacy of the textual communication and tendencies in the group mood., Published in the proceedings of the 8th International Conference on Human-Centered Software Engineering

Software projects are still failing at an alarming rate and do not provide value to the organisation at large. This has been the case for the last decade. Software projects use predominantly Waterfall as a methodology. This raises the question whether new ways of working can be introduced to improve the success rate. One such new way is Agile as an approach to developing software. A survey was done to determine whether Agile projects are more successful than Waterfall projects, thus contrasting the old and the new ways of working. Some 617 software projects were evaluated to determine the success rate based on the methodology used. Success was measured on a continuum of five levels and not just the triple constraint. The results imply that Agile projects are more successful than Waterfall projects to some extent, but that there are still concerns that need to be addressed.

User satisfaction is an important feature of software quality. However, it was rarely studied in software engineering literature. By enhancing earlier research this paper focuses on predicting user satisfaction with machine learning techniques using software development data from an extended ISBSG dataset. This study involved building, evaluating and comparing a total of 15,600 prediction schemes. Each scheme consists of a different combination of its components: manual feature preselection, handling missing values, outlier elimination, value normalization, automated feature selection, and a classifier. The research procedure involved a 10-fold cross-validation and separate testing, both repeated 10 times, to train and to evaluate each prediction scheme. Achieved level of accuracy for best performing schemes expressed by Matthews correlation coefficient was about 0.5 in the cross-validation and about 0.5–0.6 in the testing stage. The study identified the most accurate settings for components of prediction schemes.

This paper presents several considerations about teaching Project Management for Digital Health (PMDH) for the students of Digital Health Master Program, in Politehnica University Timisoara. The introductory part briefly describes the specific of digital health projects: the very sensitive public perception of this domain, wide variation of requirements, heterogeneous applications, clients with a very poor time reserve for discussions with the developers, need to integrate software from different developers, the target environment not permissive, need of interoperability, difficulties in financing a.s.o. Due to these, is obvious that is difficult to convince future engineers to embrace a career in the field. Then, the analysed discipline (PMDH) is briefly described. This contains “classical” chapters related to general Project Management issues (About projects, Communication, Motivation, Planning, Risk Analysis, Decision Analysis), others related to the specific of Software Development (The development Effort estimation, The Project Leader) but the most difficult part is to describe examples that illustrate the way the Project Management is adapted to the specific of digital health projects mentioned above. An extra chapter describes a Strategic approach for Medical Healthcare institutions, related to Digital Health. The content of the lecture is practically supported by a complex project that requires from the students to recall all the technical skills from other disciplines and an extra need of managerial skills, because all the projects are team works (7 up to 10 students), they imply diverse technologies (IoT, mobile, cloud, Web, Analytics), the team must deal with a global assessment and split the available points. The project is shared between 3 different disciplines. Thus, the inter-disciplinary skills are also addressed and developed. A lot of specific activities and documents are requested: the aim of the project (considering the need of the project, and an associated economic point of view, related to the return of investment), specifications, development, testing documentation, management files (estimation of the development effort, planning, effort, risk assessment, workload a.s.o.). Based on the didactical experience related to the tuition of this discipline, several useful conclusions are issued: results are presented, comments are made in correlation with the tuition objectives, meant to increase the motivation for this very specific domain of software development. The tuition process must consider the specific of now-a-days students: the Academics must challenge the students with debates, gaining their respect, give them “show”, increase their responsibility, request them an activity as in software companies. All these contribute to obtain a better preparation for a successful career in the field.

Decisions about whether or not to approve a project plan for execution are critical. A decision to continue with a bad plan may lead to a failed project, whereas requesting unnecessary additional planning for an already high-quality plan may be counterproductive. However, these decisions can be influenced by psychological biases, such as the endowment effect, optimism bias and ambiguity effect, which are enhanced when uncertainty is substantial and information incomplete. As a result, a non-biased model for evaluating the quality of project planning is important to improve planning approval decisions and resource allocation. This paper introduces a novel artifact (QPLAN) that evaluates and improves planning quality, and a case study to demonstrate its effectiveness within a business environment.

Yazılım, temelinde 1 ve 0 değerlerinin anlamlı bir dizi oluşturmasından oluşan, bilgisayar, makine, sistem, cihaz ya da ürün yönetimi gibi işlemlerde ve pek çok alanda kullanılan komut dizinidir. Yazılım insan hayatında günden güne daha fazla yer tutmakta ve alışılageldik pek çok işimizi herhangi bir kodlama dilinde hazırlanmış yazılımlardan gelen komutlar ile çalıştırılarak ortaya konulmuş hizmet ve ürünlerle gerçekleştirme oranımız artmaktadır. İnsanlığın sahip olduğu yeni alışkanlıkların yazılım tabanlı olgular ile şekillenmesi tüm insanların yaşadığı sayısal dönüşümün de en önemli işaretidir. Günümüzde insanlık sağlık, iletişim, finans, medya, ulaşım, turizm, gayrimenkul, pazarlama, spor, savunma, üretim, tarım, coğrafya, meteoroloji, oyun ve ilişkilendirebileceği her alanda yazılımı her geçen gün daha da büyüyen bir oranla kullanmaktadır.Proje, özel bir amaç uğruna belirli bir zaman diliminde ve aktif olduğu süreçte adım adım olgunlaşan, hedeflerinin ve çıktı beklentilerinin başlangıcında ölçümlenip tespit edildiği geçici ortak çabalar toplamıdır. Proje insanlığın yaratılışıyla ile birlikte en temel gereksinimleri olan hayatta kalma, beslenme, barınmadan itibaren kendini gösteren ve başarılı ya da başarısız olarak sonuçlanması pek çok değişkene bağlı olan bir süreç olarak hayatımızda yer almaktadır. İnsanlık öncelikle projeyi tanımlamış daha sonra da bu tanımı yönetebilecek kurallar dizinini oluşturarak proje yönetiminin de temellerini oluşturmuştur.Bilinen tüm yazılım üretim faaliyetleri bireysel ya da ekip çalışması olarak bir proje şeklinde ilerlemektedir. Yazılım konusunda bilginin ve deneyimli profesyonellerin ve yürütülen projelerin sayısı zaman içinde sürekli artmaktadır. Bu artışlar ile beraber bütçelerin de büyümesi, hem kullanılan proje yönetim yönteminin projenin zaman, maliyet ve kalite yönünde etkisi olup olmadığı hem de var olan proje yönetim metotlarından hangisi ile en etkin sonuçların alındığı sorularını da beraberinde getirmiştir.Yukarıda bahsedilen iki ana soruya yanıt bulunması amacıyla anket yöntemi kullanılmıştır. Bu ölçümlemeyi yapabilmek adına yazılım üreten ya da yazılım alanında iş yapan 210 profesyonelden anket yoluyla cevapları alınmış, hem Çevik hem de Şelale yöntemlerinde tecrübe sahibi olan 161 kişi tarafından cevaplandırılan anket sonuçları üzerine yapılan değerlendirme ile varılan sonuçlar bu tezin hazırlanmasında kullanılmıştır. Yapılan değerlendirme sonucunda proje yönetimi metodu ile projenin zaman, maliyet ve kalite ölçütleri arasında ilişki olduğu ortaya çıkmıştır.Anahtar kelimeler: Proje, Proje Yönetimi, Proje Performansı, Yazılım, Yazılım Projeleri, Çevik, Şelale, Maliyet, Kalite, Zaman Software is a command sequence that consists of a meaningful array of values 1 and 0 and is used in many areas such as computer, machine, system, and device or product management. Software is taking place more and more in human life day by day, and many of the usual work in any coding language prepared by running commands from the software and the services and products put forward by increasing the rate of realization. Shaping the new habits of humanity with software based phenomena is the most important sign of the digital transformation experienced by all human beings. Today, humanity uses software in every field that it can associate with health, communication, finance, media, transportation, tourism, real estate, marketing, sports, defense, production, agriculture, geography, meteorology, games and more.A project is a collection of temporary joint efforts that are step by step matured in a given time interval and active for a specific purpose, measured and determined at the beginning of the objectives and output expectations. With the creation of mankind, the project takes place in our lives as a process that depends on many variables, the most basic requirements of which are survival, nutrition, shelter and success or failure. Humanity first defined the project and then formed the index of rules that could manage this definition and formed the basis of project management.All known software production activities are progressing as individual or a team project. The information in software field and number of experienced professionals increase continuously. As a result of these progresses, the number of projects is increasing and magnitude of budgets is enhanced. As a result of these developments, the question about whether there is a relationship between the project management methodology used and project performance metrics (cost, time, quality) and the question about which one of waterfall and agile project management methodologies is more effective in ensuring success with regards to these three metrics (project cost, time, quality) have been raised.A survey methodology was used to find answers to the two main questions above. The survey has been answered by 210 software professionals or professionals whose current jobs are related with software. The responses from 161 out of 210 respondents who have experience in both agile and waterfall methods were used in the data analysis phase of the thesis. Results showed that there are statistically significant differences between agile and waterfall project techniques in terms of cost, time and quality metrics.Keywords: Project, Project Management, Project Performance, Software, Software Projects, Agile, Waterfall, Cost, Quality, Time 75

Submitted by Nadir Basilio (nadirsb@uninove.br) on 2020-11-09T20:48:45Z No. of bitstreams: 1 Wagner Solivan Ferreira.pdf: 1337269 bytes, checksum: 067ece6bff673d6afdd8dd6e7525776b (MD5) Made available in DSpace on 2020-11-09T20:48:45Z (GMT). No. of bitstreams: 1 Wagner Solivan Ferreira.pdf: 1337269 bytes, checksum: 067ece6bff673d6afdd8dd6e7525776b (MD5) Previous issue date: 2019-12-13 Organizations of Information Technologies (IT) projects are faced with the challenge of developing projects of activity duration estimates, due to the presence of diverse and complex scenarios that raise the levels of uncertainty and insecurity. The lack of parameters, how to get project information already completed (positive or negative) and share knowledge among the project team, hinders the work of project professionals for the development schedule and budget. Studies show that the absorption of the knowledge acquired during the life cycle of the project and the shared experience among the professionals involved can be stored and shared through methods and models, which are appointed by the theoretical framework as a leveraging factor for the projects, consequently, for organizations. Thus, this study aims to "offer knowledge capture model for software projects based on lessons learned. To this end, qualitative research of descriptive character by applying a single case study in a leading IT company in the solutions market to support customer experience management will be adopted, active in Latin America and Spain and situated among the 25 multinationals in its class. The company was selected for having high volume of software development projects, this volume, on average 33% of projects have change activity estimates, often resulting in cost variances and / or time limits for the company. To achieve robustness in the result that is intended to determine, They were carried out semi-structured interviews with professionals working as managers and project managers who experience the use of the estimated duration of the software project activities. The collection of various sources of evidence (primary and secondary), and internal tools (SharePoint), documentation (Excel, Word and e-mails), and the interviews were used for triangulation of data. The results of this study demonstrated the negligence on the part of the organization in not giving due importance on information that is generated during the lifecycle of a project. This scenario occurs because of the existence of cultural problems, the high volume of projects and the constant re-prioritization of the company's activities. As organizações de projetos de Tecnologias da Informação (TI) se deparam com o desafio de elaborar estimativas de duração de atividades de projetos, devido a presença de cenários diversos e complexos que as elevam a patamares de incertezas e inseguranças. A falta de parâmetros, como obter informações de projetos já concluídos (positivos ou negativos) e compartilhar conhecimento entre a equipe de projeto, dificulta o trabalho dos profissionais de projetos para o desenvolvimento de cronograma e orçamento. Estudos mostram que a absorção desses conhecimentos adquiridos durante o ciclo de vida do projeto e a experiência compartilhada entre os profissionais envolvidos podem ser armazenados e compartilhados por meio de métodos e modelos, que são apontados pelo referencial teórico como um fator alavancador para os projetos e, consequentemente, para as organizações. Sendo assim, este estudo tem como objetivo “propor o modelo de captura de conhecimento em projetos de software com base em lições aprendidas. Para tal, será adotada a pesquisa qualitativa de caráter descritivo mediante a aplicação de um estudo de caso único em uma empresa de TI líder do mercado de soluções para apoio à gestão de experiência do cliente, atuante na América Latina e na Espanha e situada entre as 25 melhores multinacionais do seu segmento. A empresa foi selecionada por possuir alto volume de projetos de desenvolvimento de software, deste volume, em média 33% dos projetos possuem alterações de estimativas de atividades, muitas vezes resultando em desvios de custos e/ou prazos para a empresa. Para se obter robustez no resultado que se pretende apurar, foram realizadas entrevistas semiestruturadas com profissionais que atuam como gerentes e gestores de projetos que vivenciam o uso da estimativa de duração das atividades de projetos de software. A coleta de várias fontes de evidências (primárias e secundárias), como ferramentas internas (SharePoint), documentações (Excel, Word e e-mails), além das entrevistas foram utilizadas para a triangulação dos dados. O resultado desse estudo demostrou a negligência por parte da organização em não dar a devida importância nas informações que são geradas durante o ciclo de vida de um projeto. Esse cenário ocorre devido a existência de problemas culturais, ao alto volume de projetos e a re-priorização constante de atividades da empresa. Diante disso o modelo proposto permitirá a empresa criar processos para capturar as lições aprendidas gerada durante o ciclo de vida do projeto, assim, apoiando os gerentes e gestores de projetos no processo de elaboração das estimativas de atividades com mais precisão.

Software development project activities are grouped into functional roles, each of which is performed by a type of software engineer who carries out different activities. Therefore, for each of these roles, various technicals and personalities skills are required. Failure to meet these requirements when selecting team members and allocating roles will put the software development project at serious risk of failure as the selected people may not perform well. However, the process of selecting people and assigning them to roles is a complex process for the project manager to do based on his or her experience, because even with a relatively small number of people and roles, a large number of combinations can be identified. Thus, analyzing each option is not feasible and good options may not be considered. In order to support this decision process, exploring Search Based Software Engineering (SBSE) techniques, this paper proposes a multi-objective approach for selection and allocation of technically qualified and psychologically suitable people for each functional role of the software development project. To evaluate the proposal, besides comparing with the existing literature related to the theme of the proposed approach, the paper presents results from three distinct metaheuristics capable of dealing with the multiple objectives to be optimized. These algorithms are applied to real data collected in a case study that reveal the efficiency and potential applicability of the proposed approach. Nenhuma As atividades dos projetos de desenvolvimento de software são agrupadas em diferentes papéis funcionais, cada qual executado por um tipo de engenheiro de software, que realiza diferentes atividades. Sendo assim, para cada um destes papéis são necessárias diversas habilidades técnicas e de personalidades específicas. Caso estes requisitos não sejam observados durante a seleção de membros para a equipe e alocação nos papéis, colocará o projeto de desenvolvimento de software em sério risco de fracasso, pois as pessoas selecionadas poderão não desempenhar bem as suas atribuições. Porém, o processo de seleção das pessoas e a alocação destas a papéis para a formação da equipe é um processo complexo para ser realizado pelo gerente de projetos com base apenas em sua experiência, pois, mesmo com um número relativamente pequeno de pessoas e papéis, uma grande quantidade de combinações pode ser identificada. Assim, analisar cada opção é inviável e boas opções podem não ser consideradas. A fim de fornecer suporte na tomada de decisão, explorando técnicas de Engenharia de Software Baseada em Buscas, do inglês Search Based Software Engineering (SBSE), este trabalho propõe uma abordagem multiobjetiva para seleção e alocação de pessoas tecnicamente qualificadas e psicologicamente adequadas para cada papel funcional do projeto de desenvolvimento de software. Para avaliação da proposta, além da comparação com a literatura existente relacionada com o tema da abordagem proposta, o trabalho apresenta resultados de três metaheurísticas distintas capazes de lidar com os múltiplos objetivos a serem otimizados. Estes algoritmos são aplicados a dados reais coletados em um estudo de caso que revelam a eficiência e aplicabilidade potencial da abordagem proposta.

One of important aspects of software projects is estimating the cost and time required to develop projects. Nowadays, this issue has become one of the key concerns of project managers. Accurate estimation of essential effort to produce and develop software is heavily effective on success or failure of software projects and it is highly regarded as a vital factor. Failure to achieve convincing accuracy and little flexibility of current models in this field have attracted the attention of researchers in the last few years. Despite improvements to estimate effort, no agreement was obtained to select estimation model as the best one. One of effort estimation methods which is highly regarded is COCOMO. It is an extremely appropriate method to estimate effort. Although COCOMO was invented many years ago, it enjoys the effort estimation capability in software projects. Researchers have always attempted to improve the effort estimation capability in COCOMO through improving its structure. However, COCOMO results are not always satisfactory. The present study introduces a hybrid model for increasing the accuracy of COCOMO estimation. Combining bee colony algorithm with COCOMO estimation method, the proposed method obtained more efficient coefficient relative to the basic mode of COCOMO. Selecting the best coefficients maximizes the efficiency of the proposed method. The simulation results revealed the superiority of the proposed model based on MMRE and PRED(0.15).

Requirements engineering is pivotal and central to every successful software development project. There are several reasons why software projects fail; however, poorly elicited, documented, validated and managed requirements contribute grossly to software projects failure. Software project failures are normally very costly and risky and these could even a times be life threatening also. Projects that overlook requirements engineering processes often suffer or are most likely to suffer from failures, challenges and other consequent risks. The cost of project failures and overruns when estimated is quite great and grave. In addition, software project failures or overruns portend a challenge in today’s competitive market environment. It affects negatively the image, goodwill, profitability, and revenue drive of companies and decreases the marketability of their products, as well as, the perceived satisfaction of their customers and clients (which also leads to poor loyalty). In this paper, requirements engineering was discussed. Its role in software projects success was elaborated. The place of software requirements process in relation to software project failure was explored and examined. Furthermore, project success, challenge and failure factors were also discussed with emphasis placed on requirements factors as they play a major role in software projects’ successes, challenges and failures. The paper relied on secondary statistics to explore and examine factors responsible for the successes, challenges and failures of software projects in large, medium and small scaled software companies.

Günümüzde bilişim alanında yürütülen projelerin çoğunluğu tamamlanamamakta veya zaman, bütçe ve performans kriterlerini karşılayamamaktadır. Projelerin etkin olarak yönetimi maksadıyla, yaygın olarak istifade edilen çok sayıda rehber, bilgi tabanı, standart ve metot bulunmaktadır. Ancak, bilişim projelerinin kendine has özelliklerinden dolayı bilişim alanına yönelik özel bir metoda ihtiyaç duyulmaktadır. Bu çalışma, bilişim projelerine yönelik çevik ve geleneksel yaklaşımları birlikte ele alan hibrit bir proje yönetim metodu önermektedir. Geliştirilen metot; prensip, bilgi alanı, süreçler ana bileşenleri ile roller ve sorumluluklar, dokümanlar, yetkinlikler ve kritik başarı faktörleri tamamlayıcı bileşenlerinden oluşmaktadır. Metodun geliştirilmesinde tasarım bilimi araştırmasından istifade edilmiştir. Problemin ortaya konulmasını müteakip literatür taraması neticesinde PRINCE2 Proje Yönetim Metodu en uygun başlangıç çözüm olarak belirlenmiştir. Dünyada Kabul görmüş ve yaygın olarak kullanılan ve uzun yıllardır yapılan çalışmaların ürünü olan proje yönetim bilgi tabanı, rehber, standart ve metotları ile bilişim alanında yaygın olarak kullanılan diğer en iyi uygulamalar ve bilişim projeleri kritik başarı faktörlerinden faydalanılarak, tasarım bilimi araştırmasında kullanılan geliştirme modelleri ile metot adım adım geliştirilmiştir.Metodun doğrulanması için tecrübeli proje yöneticileri ve proje yönetimi alanında çalışan akademisyenler ile yapılan yarı yapısal yüz yüze görüşmelerden istifade edilmiştir. Nitel analiz neticesinde elde edilen bulgular ile hem metot doğrulanmış hem de analiz sonuçlarından istifade edilerek bilişim proje yönetim metoduna son hali verilmiştir. Anahtar Kelimeler: Bilişim Projeleri, Proje Yönetim Metodu, Hibrit Metodolojiler, Tasarım Bilimi Araştırması, PMBOK, PRINCE2, Çevik Proje Yönetimi, Kritik Başarı Faktörleri, Nitel Araştırma, Yarı Yapılandırılmış Yüz Yüze Görüşmeler The majority of the IT projects today either completely fail or fail to comply with time, budget or performance criteria. There are several standards, Bodies of Knowledge (BOK) and methods in the project management area developed by different organizations to manage projects more effectively. However, there is a requirement for domain-specific Project Management Method in IT area due to distinct characteristics of IT Projects. This study proposes a hybrid project management method including both traditional and agile approaches to managing IT projects effectively.The method is composed of the principles, knowledge areas and processes main building blocks as well as roles and responsibilities, critical success factors, documents and competencies complementary building blocks. To develop the IT project management method, Design Science Research has been utilized. Following the definition of the problem, PRINCE2 Project Management Method is identified as the best possible initial solution. Then, the method has been developed step by step by using Design Science Research Development Models, utilizing Worldwide well-known and recognized current standards, bodies of knowledge and methods in the project management area, as well as other best practices in information systems domain and IT projects critical success factors.To validate the method, semi-structured face to face interviews are conducted with experienced project managers and academicians working on IT project management area. The method has been finalized by the findings obtained as a result of qualitative analysis.Keywords: IT Projects, Project Management Method, Hybrid Methodologies, Design Science Research, PMBOK, PRINCE2, Agile Project Management, Critical Success Factors, Qualitative Research, Semi-Structured Interviews 137

İşletmelerde ortaya çıkan bilgi teknolojileri projelerinin sayısı ve proje yönetimi için yeni metodolojilerin geliştirilmesine paralel olarak, doğru proje yönetim metodolojilerini seçmek ve projeyi etkileyen kritik başarı faktörlerini dikkate şirketler için kritik hale gelmiştir. Projeleri başarıyla sonuçlandırmak için, proje başarısını etkileyen faktörlerin proje uzmanları tarafından bilinmesi gerekir. Bu nedenle, kritik başarı faktörleri kavramı farklı araştırmacılar tarafından incelenmektedir. Bu çalışmanın temel amacı, geleneksel ve çevik proje yönetimi yaklaşımlarıyla yönetilen bilgi teknolojileri projeleri için kritik başarı faktörlerini analiz etmek ve kritik başarı faktörlerinin geleneksel ve çevik proje yönetimi yaklaşımları arasındaki benzerlik ve farklılıkları tespit etmektir. Farklı araştırmacılar tarafından daha önce analiz edilen kritik başarı faktörleri literatürde araştırılmış ve literatürde yer alan maddelere dayanarak teorik model ve hipotezler oluşturulmuştur. Başarı faktörlerine ek olarak, 178 farklı proje için proje ve firma demografisi toplanmıştır. Analiz için çoklu regresyon, ANOVA ve t-testleri kullanılmıştır. Sonuç olarak, dört faktör bilgi teknolojileri projeleri için kritik bir başarı faktörü olarak ortaya çıkmıştır; projenin kritikliği, proje ekibi, proje yönetimi süreci ve proje geliştirme süreci. Geleneksel proje yönetimi için proje ekibi ve proje geliştirme süreci kritik başarı faktörleri olarak belirlenmiştir. Çevik proje yönetimi içinse; proje kritikliği ve proje yönetimi süreci kritik başarı faktörleri olarak tespit edilmiştir. Çalışmanın sonunda akademisyenler, araştırmacılar ve proje uzmanları için bulguların ve kısıtlamaların detayları açıklanmıştır. In parallel to the emerging number of information technology projects in the companies and the development of new methodologies for the project management, choosing the right methods and knowing the influencers of project become critical for the companies. In order to finalize the projects successfully, factors effecting the project success need to be known by project professionals. Therefore, critical success factors concept is studied by different researchers. The main objective of this study is to analyze the critical success factors for information technology projects that are managed either with traditional and agile project management approaches and identify the similarities and differences of critical success factors between them. Critical success factors analyzed before by different researchers are searched in the literature and theoretical model and hypotheses are formulated based on the items found in the literature. In addition to success factors, project and company demographics are collected for 178 different projects. For analysis, multiple regression, ANOVA and t-tests are used. As a result, four factors are identified as critical success factor for information technology projects; project criticality, project team, project management process and project development process. Project team and project development process are identified as critical success factors for traditional project management. Project criticality and project management process are identified as critical success factors for agile project management. Details of findings and limitations are explained at the end of the study for academicians, researchers and project professionals. 115

Günümüzde teknolojik gelişmelerle birlikte, müşterilerin ihtiyaç ve beklentilerinde hızlı bir değişim yaşanmaktadır. Bu değişimlere ve gelişmelere ayak uyduramayan işletmeler zamanla rakipleri ile rekabet edemez duruma gelmekte ve faaliyetlerini sonlandırmaktadır. Bu durum yazılım geliştirme yapan işletmeler için de geçerlidir. Yazılım geliştirme yapan işletmelerin yoğun rekabet ortamında hayatta kalabilmeleri için bilişim sektöründeki gelişmelere ayak uydurmaları ve değişen müşteri ihtiyaçlarına hızlı yanıt verebilmeleri gerekmektedir. Yazılım sektöründe projeler bir yıl veya bir yılı aşkın bir sürede geliştirilebilmektedir. Söz konusu projeler geleneksel yöntemlerle geliştirildiğinde, proje süresince müşteri ihtiyaç ve çevre koşullarında olabilecek değişimlerden dolayı proje sonunda ortaya çıkan ürünlerin, müşteri ihtiyacını karşılayacak güncellikte olmaması ile sonuçlanabilmektedir.Müşterilerin, yazılım geliştirme yapan işletmelerden beklentileri; değişen ihtiyaçlara hızlı uyum sağlamaları ve proje teslimatlarını daha kısa sürede gerçekleştirmeleridir. Bu sebepten, değişen müşteri ihtiyaçlarına daha hızlı yanıt vermek ve müşteri memnuniyetini sağlamak amacıyla çevik yazılım yöntemleri, yazılım sektöründeki işletmelerce uygulanmaya başlanmış olup, gün geçtikçe daha fazla işletme tarafından tercih edilir hale gelmiştir.Çevik yazılımda en çok kullanılan yöntemlerden biri olan Scrum, Türkiye'de ve dünyada birçok işletme tarafından geniş bir uygulama alanına sahiptir. Buna rağmen, Scrum'ın her zaman başarılı bir şekilde uygulanamadığı ve organizasyonların Scrum'a geçiş sürecinde bir takım problemler yaşadığı durumlarla sıklıkla karşılaşılmaktadır. Bunun sonucu olarak, Scrum yönteminin organizasyona getireceği fayda ve geleneksel yöntemlere göre üstünlüğü sık sık tartışılmaktadır.Bu tez çalışmasında, Türkiye'de yazılım projelerinde çevik yöntemlerin kullanımı ve söz konusu yöntemlerden biri olan Scrum uygulamalarının ne derecede gerçekleştirildiği araştırılmıştır. Bu doğrultuda, Türkiye'de çeşitli sektörlerde faaliyet gösteren işletmelerin yazılım geliştirme departmanlarında farklı pozisyonlarda çalışanların, çalıştıkları işletmelerdeki çevik yöntem kullanımları incelenmiştir. Bununla birlikte, söz konusu çalışanların Scrum ve çalıştıkları işletmelerde Scrum'ın uygulanma derecesi hakkındaki düşünceleri irdelenmiştir İşletmelerin çevik dönüşümdeki başarısı çevik dönüşüm ve Scrum konularında uzman olan çevik koçların görüşleri doğrultusunda literatürde önemli görülen çeşitli faktörlerle birlikte değerlendirilmiştir. Bu araştırmada, çevik dönüşüm sürecine organizasyonun tamamının dahil edilmesi ve gerektiğinde değişimin organizasyon kültürüne yayılması, dönüşüm için organizasyon içerisinde gerekli bilginin, değişim ortamının ve üst yönetimin desteğinin sağlanmasının, çevik dönüşüm sürecinin başarılı olarak gerçekleştirilmesinde önemli olarak görüldüğü sonucuna ulaşılmıştır. Nowadays, there is a rapid change in customer needs and expectations with the latest technological developments. Companies that cannot keep up with these changes and developments have problems to compete with their rivals in time. This fact also seen for companies engaged in software development. Software development companies need to keep up with developments in the technolgy and respond quickly to changing customer needs in order to survive in an intense competitive environment. However, in the software sector, projects be developed over a period of one year or more. When companies develop these projects with traditional metholodogies, customer needs and environmental conditions frequently change. In this case, the project may result in updated products at the end of the project and these products do not have the ability to meet the customer needs.Customers expect from companies adapt to the changing needs and deliver project deliveries in a shorter time. For this reason, agile software methologies have been prefeered by many companies in the software sector in order to respond faster to changing customer needs and to ensure customer satisfaction.Scrum is one of the most widely used method of agile software and it has a wide range of applications by many businesses in Turkey and the world. Nevertheless, unsuccessfully Scrum implementation and companies face some problems in the transition to Scrum are often encountered. As a result, it is the advantage of the Scrum and its superiority over traditional methods stated frequently.In this study, the use of agile methologies and the success of Scrum transformation in software projects in Turkey is researched. In this regard, the use of agile methologies and Scrum usage was examined in different sectors. In additoion, the opinions of the employees in question about Scrum and the degree of implementation of Scrum in the companies they work in were examined. Moreover, the success of organizational agile transformation is evaluated with various factors that are considered important in the literature in accordance with expert opinions.As a result of this study, it has been concluded that the agile transformation process has been realized more successfully in organizations that include the entire organization in the process of agile transformation, spread the change to the whole organization, change the culture of the organization and provide the support of the management. 83

Agile project management emphasizes flexibility and adapting to change. Embracing change often means that specified requirements get changed, removed or replaced under the course of a software project. Another consequence of the nature of agile projects is that everything that does not directly contribute to the working software gets dropped from the product lifecycle. Traceability – the ability to trace requirements back to their origins and forward to design artifacts, code, and testcases – is one such thing that may be overlooked. At the same time, traceability may be crucial to making sure that the delivered product meets the product goals. This thesis investigates the concept of decision traceability – the ability to trace decisions that relate to the evolution of a software product, as well as the fulfillment of product goals. The purpose of this thesis is to understand the importance of decision traceability in relation to product goals and changing requirements in agile software projects. For this purpose, two research questions were developed. (1) What are the challenges of achieving decision traceability in agile projects? And (2) What are important aspects of achieving decision traceability in agile projects? An interpretive qualitative case study was conducted at an IT-consultancy firm. In the case study, two of the organization’s in-house projects were observed, and six informants were interviewed. In answer to the research questions, seven challenges and six important aspects of achieving decision traceability were identified. A conclusion that can be made from the findings is that other aspects than just well-defined processes– such as team engagement, value perception, and communication – may be essential to achieving decision traceability in agile software projects.

Software engineering researchers have, over the years, proposed different critical success factors (CSFs) which are believed to be critically correlated with the success of software projects. To conduct an empirical investigation into the correlation of CSFs with success of software projects, we adapt and extend in this work an existing contingency fit model of CSFs. To archive the above objective, we designed an online survey and gathered CSF-related data for 101 software projects in the Turkish software industry. Among our findings is that the top three CSFs having the most significant associations with project success were: (1) team experience with the software development methodologies, (2) team’s expertise with the task, and (3) project monitoring and controlling. A comprehensive correlation analysis between the CSFs and project success indicates positive associations between the majority of the factors and variables, however, in most of the cases at non-significant levels. By adding to the body of evidence in this field, the results of the study will be useful for a wide audience. Software managers can use the results to prioritize the improvement opportunities in their organizations w.r.t. the discussed CSFs. Software engineers might use the results to improve their skills in different dimensions, and researchers might use the results to prioritize and conduct follow-up in-depth studies on those factors.

Orta ve büyük ölçekli yazılım geliştirme projeleri genellikle bir çok takım üyesi tarafından birlikte geliştirilirler. Takım üyelerinin koordine edilmesi, grup için uygun geliştirme yöntemleri kullanılması ve grubun yazılım geliştirme sürecinin kontrolü zor problemlerdir. Yazılım geliştirme metotları yoğunlukla bu zor problemlerin çözümü için kullanılmaktadırlar. Var olan yazılım geliştirme metotları her ne kadar endüstrinin ihtiyaçlarını karşılasalar dahi, akademisyenler tarafından üniversitelerde yürütülen araştırma tabanlı yazılım geliştirme proje ihtiyaçlarını sağlamaya yönelik değillerdir. Bu çalışmada; araştırma tabanlı yazılım projeleri için yeni bir metotun gerekli olduğunu ortaya koymak adına, bu alanda çalışan kişilerin ihtiyaçları ve üstün yöntemleri nitel bir çalışma ile toplanıp, toplanan veriler ışığında da, araştırma tabanlı yazılım projeleri için yeni bir yazılım geliştirme metotu sunulmuştur. Önerilen metot alan uzmanlarının sağladığı uzman görüşleri ile değerlendirilip araştırma tabanlı yazılım projeleri için uygun bulunmuştur. Çalışma sırasında toplanmış olan alan problemleri ve üstün yöntemler, araştırma tabanlı yazılım projelerinde yer almak isteyen proje yöneticileri, takım üyeleri, üniversiteler ve destekleyici kurumlara öneriler olarak bir çerçevede sunulmuştur. Bu öneriler kullanılarak ilerde gerçekleştirilecek olan benzeri projelerin verimlilikleri artırılabilir. Software development in mid-sized or large-scale projects is usually carried by a group of individuals, whose coordination, choosing suitable development practices for the group and keeping track of the software development process are all challenging tasks. Software development methodologies are heavily utilized for these purposes. Although previously proposed methodologies manage to meet the needs of the industry, they are not tailored to do so for academicians developing research-based software projects at universities. Therefore, in this thesis, our first aim is to show the necessity of a new software development methodology for research-based projects carried by the universities. Then, through current literature, interviews and questionnaires, the needs and the best practices of research-based projects are collected using grounded theory qualitative method. Finally, after completing the analysis of the findings, a new software development methodology is proposed tailored to the needs of the researchers that are working on research-based software projects. The proposed methodology is evaluated by the experts and it is found useful for the research-based software projects. Collected issues and best-practices are proposed as a guideline for the project managers, team members, funding agencies, universities, and the end-users of research-based software projects. These guidelines can be utilized to increase the productiveness of such projects. 138

Proje yönetimi, küresel çaptaki boyutu ile dikkat çekmektedir. Dünya Bankası istatistiklerine göre küresel ölçüde gayri safi yurtiçi hasılanın %24'ü kadar bütçe proje yönetimi aktivitelerine harcanmaktadır. Ayrıca, 2020 itibariyle küresel ölçüde 16 milyon civarı yeni proje yönetimi iş alanının yaratılması beklenmektedir. Sonuç olarak proje yönetimi küresel olarak değer yaratma anlamında iş dünyasına önemli bir katkı sağlamaktadır. Projelerin maliyet, zaman ve kalite gibi temel bileşenleri bulunmaktadır. Bu bileşenleri göz önünde tutarak proje hedeflerine ulaşmak için projelerin disipliner bir yaklaşım ile yönetilmesi gerekir. Bu noktada proje yönetiminin önemli ve yönlendirici bir rolü bulunmaktadır. Uygulamada, firmaların kendi dinamiklerine göre geliştirdikleri proje yönetimi metodolojilerinin yanında, amacı proje yönetimi aktivitelerini dünya genelinde geliştirmek olan ve kar amacı gütmeyen organizasyonlar tarafından oluşturulmuş metodolojiler de bulunmaktadır. Bunlardan bazılarının arasında PMAJ, PRINCE2, IPMA, APM bulunmaktadır. Ama küresel ölçekte en çok kabul gören proje yönetimi metodolojisi Project Management Institute (PMI) tarafından geliştirilmiştir. PMI, kendi proje yönetim metodolojisi süreçlerini on farklı bilgi alanı altında toplamıştır. PMI, tüm proje tipleri için bir temel sunmaktadır. Buna bağlı olarak her proje ve sektör bu metodolojiyi kendi süreç ve aktivitelerine uyarlamaktadır. Proje bazlı çalışan sektörlerden bir tanesi de bankacılıktır. Bankacılık sektörü neredeyse tamamen teknoloji tabanlıdır. Bu sebeple, yazılım geliştirme projeleri toplam içinde önemli bir paya sahiptir. Yazılım projeleri genellikle şelale tekniği ile yapılırken son yıllarda çevik yöntemler de gündeme gelmiştir. Bu tekniklerin yanı sıra, proje yönetimi araç ve metodolojileri de kullanılmaktadır. Bir projede başarı hikayesine ulaşmak için, proje yönetimi uygulamaları artık bir zorunluluk haline gelmiştir. Bu tez çalışmasında, Türkiye'nin büyük ölçekli bankalarından birinin örnek bir yazılım geliştirme projesi PMI'ın proje yönetimi metodolojisi göz önünde tutularak eleştirilmektedir. Bunu yaparken bir grup proje paydaşı ile yapılan mülakat ile proje ve PMI'ın proje süreçleri görüşülmüştür. Paydaşların yorum ve görüşlerine göre her sürecin PMI'ın yaklaşımına göre uyumlu olarak yönetilip yönetilmediği değerlendirilmiştir. Banka PMI'ın standartlarını uygulamamaktadır. Uygulanan metodoloji iyi bir şekilde tanımlı ve dokümante edilmemiştir. Özetle, proje ekibi her ne kadar projeyi PMI'ın standartlarına göre yönetmiyor olsa da birçok uygulama genellikle PMI ile örtüşmektedir. Sonuç olarak, paydaşlar PMI'ın standartlarının bankanın yazılım projelerine uygulanması durumunda, bu işleyişin bankadaki projelere maliyet, zaman ve verimlilik anlamında olumlu katkı sağlayacağı konusunda hemfikir olmuştur. Project management takes the attentions with its size globally. Depending on the World Bank's figure, almost 24% of the GDP is spent to the project management activities. And nearly 16 million new project management jobs are expected to be created globally by the 2020. As a result of these, project management provides a significant contribution to business life in value creation globally.Projects has some components such as cost, time and quality. To meet the project objectives by considering these components, they have to be managed in a disciplinary approach. At this point project management has a significant and directive role. In practice, beside the firm based developed methodologies; there are many number of project management methodologies developed by generally non-profit organizations, have aims to improve the project management activities all around the world. Some of them are PMAJ, PRINCE2, IPMA, APM, and etc. However, the globally most accepted project management methodology is developed by the Project Management Institute (PMI). It defines the project management processes under ten different knowledge areas. It provides a baseline to each type of projects. So each project/industry can apply this methodology to its own processes and activities. One of the project based industry is banking. The banking industry almost wholly based on the technology. That's why, software development projects keep a great portion in totally. In software development projects while waterfall techniques are generally used, in recent years, agile techniques became popular. Besides these techniques, the project management tools and methodologies are used. To reach a success story, project management application become an obligation. In this thesis, Turkey's one of the big size bank's software development project was criticized by considering the PMI's project management methodology. While doing this, a group of stakeholder were interviewed about project and processes defined in PMI's methodology. By considering their comments and opinions, each process was evaluated whether they are consistent with the PMI's approach or not. The bank did not adopt the PMI's standards as the project management methodology. They apply their own methodology which is not defined or documented very well. In summarize, although the project team did not manage the project in the light of the PMI's standard, their applications generally overlap with PMI's methodology. In conclusion, the stakeholders agree on if the PMI's standards are applied in bank's software projects, they believe it would have a positive contribution in terms of cost, time and effectiveness. 134

Irrespective of different research-based approaches toward risk management, developing a precise model towards risk management is found to be a computationally challenging task owing to critical and vague definition of the origination of the problems. This research work introduces a model called as PROM i.e. Predictive Optimization of Risk Management with the perspective of software engineering. The significant contribution of PORM is to offer a reliable computation of risk analysis by considering generalized practical scenario of software development practices in Information Technology (IT) industry. The proposed PORM system is also designed and equipped with better risk factor assessment with an aid of machine learning approach without having more involvement of iteration. The study outcome shows that PORM system offers computationally cost effective analysis of risk factor as assessed with respect to different quality standards of object oriented system involved in every software projects.

This article investigated the moderating effect of the perceived compatibility of agile methodologies in determining the actual success of a methodology. The researchers conceptualised the agile methodology perceived success by using cost, scope, time and quality to complete the project. The researchers further hypothesised that perceived compatibility has moderating effects towards agile methodology perceived success and its use. The theoretical framework was evaluated by means of data collected from IT professionals (n = 230). The objective of the study was to determine how agile methodology use and perceived compatibility influence agile methodology perceived success in South Africa. A survey was conducted among IT professionals and the results analysed using statistical methods. The results showed perceived compatibility to have a moderating effect towards agile methodology use, time and cost. Nevertheless, there was a lack of moderating effect of perceived compatibility with regard to agile methodology use and perceived quality, and agile methodology use and perceived scope. The results of this study formulate a comprehensive model that could provide a set of guidelines for agile methodology use to the agile methodology communities and other IT professionals in South Africa. Categories: • Applied computing ~ Software development • Applied computing ~ Project management

O sucesso de um projeto de desenvolvimento de software não se mede somente pelo resultado final, mas também pelo cumprimento de variáveis que compõem o ciclo de vida do projeto. A escolha de boas práticas, a utilização ou não de metodologias de desenvolvimento de software e a gestão de fatores críticos de sucesso são pontos a que não nos podemos alhear e que permitem obter os resultados que pretendemos. Com esta investigação apurou-se quais os fatores críticos de sucesso com maior influência no resultado final de um projeto, bem como a relação existente entre a adoção de determinadas metodologias e o resultado de um projeto. Para tal, optámos por uma abordagem metodológica qualitativa realizando um inquérito vocacionado para membros de equipas de projetos de desenvolvimento de software. Os resultados obtidos permitiram comparar a situação da gestão de projetos de desenvolvimento de software em Portugal com a realidade que se passa noutros países, que, muitas vezes, apenas é conhecida através de estudos como, por exemplo, o realizado pelo 'The Standish Group'. Da informação recolhida, foi possível verificar que os fatores críticos que maior influência têm no resultado de um projeto são “Infraestrutura e ferramentas de apoio”, “Comprometimento e motivação da equipa do projeto” e “Qualificações da equipa”. Existe um longo caminho a percorrer na gestão de projetos em Portugal, mas aqui fica uma breve análise, em jeito de contributo, dos principais fatores a ter em conta, para que se possam implementar estratégias que resultem, cada vez mais, no sucesso dos projetos. The success of a software development project depends not only on the outcome, but on the many variables composing its life cycle. Good practice choices, using (or not) software development methodologies and managing critical success factors must not be ignored to achieve the intended results. This research establishes which factors have major influence in final result relates analyzing the relationships between adopted methodologies and project’s outcome. We have therefore chosen a qualitative methodological approach by holding a survey destined to software development project team members. The results obtained allowed to compare the current situation of the management of software development projects in Portugal with the reality in other countries which is often only known through studies such as the one made by 'The Standish Group'. From the information collected, it can be concluded that the critical success factors with major influence in the project’s outcome are “Infrastructure and supporting tools”, “Commitment and motivation of project teams” and “Team qualifications”. There is still a long way ahead regarding project management in Portugal, but here is a brief study, as a contribution, of the main factors which must be taken into account to implement strategies which will increasingly result in a success projects.

Submitted by Emanuel Varela Cardoso (emanuel.varela@ufcg.edu.br) on 2018-09-10T20:31:40Z No. of bitstreams: 1 MIRKO BARBOSA PERKUSICH – DISSERTAÇÃO (PPGCC) 2018.pdf: 3631770 bytes, checksum: 855cc4a180be90ee4d3788f2b18b6141 (MD5) Made available in DSpace on 2018-09-10T20:31:40Z (GMT). No. of bitstreams: 1 MIRKO BARBOSA PERKUSICH – DISSERTAÇÃO (PPGCC) 2018.pdf: 3631770 bytes, checksum: 855cc4a180be90ee4d3788f2b18b6141 (MD5) Previous issue date: 2018-03-05 O aumento na utilização de métodos ágeis tem sido motivado pela necessidade de respostas rápidas a demandas de um mercado volátil na área de software. Em contraste com os tradicionais processos dirigidos a planos, métodos ágeis são focados nas pessoas, orientados à comunicação, flexíveis, rápidos, leves, responsivos e dirigidos à aprendizagem e melhoria contínua. Como consequência, fatores subjetivos tais como colaboração, comunicação e auto-organização são chaves para avaliar a maturidade do desenvolvimento de software ágil. O Scrum, focado no gerenciamento de projetos, é o método ágil mais popular. Ao ser adotado por uma equipe, a aplicação do Scrum deve ser melhorada continuamente sendo complementado com práticas e processos de desenvolvimento e gerenciamento ágeis. Apesar da Reunião de Retrospectiva, evento do Scrum, ser um período reservado ao final de cada sprint para a equipe refletir sobre a melhoria do método de desenvolvimento, não há procedimentos claros e específicos para a realização da mesma. Na literatura, há diversas propostas de soluções, embora nenhuma consolidada, para tal. Desta forma, o problema em questão é: como instrumentar o Scrum para auxiliar na melhoria contínua do método de desenvolvimento com foco na avaliação do processo de engenharia de requisitos, equipe de desenvolvimento e incrementos do produto? Nesta tese, propõe-se um processo sistemático baseado em redes bayesianas para auxiliar na avaliação da aplicação do Scrum em projetos de software, instrumentando o método para auxiliar na sua melhoria contínua com foco na avaliação do processo de engenharia de requisitos, equipe de desenvolvimento e incrementos do produto. A rede bayesiana foi construída por meio de um processo de Engenharia de Conhecimento de Redes Bayesianas. Uma base de dados, elicitada de dezoito projetos reais de uma empresa, foi coletada por meio de um questionário. Essa base de dados foi utilizada para avaliar a acurácia da predição da Rede Bayesiana. Como resultado, a previsão foi correta para quatorze projetos (acurácia de 78%). Dessa forma, conclui-se que o modelo é capaz de realizar previsões com acurácia satisfatória e, dessa forma, é útil para auxiliar nas tomadas de decisões de projetos Scrum. The use of Agile Software Development (ASD) is increasing to satisfy the need to respond to fast moving market demand and gain market share. In contrast with traditional plan-driven processes, ASD are people and communication-oriented, flexible, fast, lightweight, responsive, driven for learning and continuous improvement. As consequence, subjective factors such as collaboration, communication and self-management are key to evaluate the maturity of agile adoption. Scrum, which is focused on project management, is the most popular agile method. Whenever adopted, the usage of Scrum must be continuously improved by complementing it with development and management practices and processes. Even though the Retrospective Meeting, a Scrum event, is a period at the end of each sprint for the team to assess the development method, there are no clear and specific procedures to conduct it. In literature, there are several, but no consolidated, proposed solutions to assist on ASD adoption and assessment. Therefore, the research problem is: how to instrument Scrum to assist on the continuous improvement of the development method focusing on the requirements engineering process, development team and product increment? In this thesis, we propose a Bayesian networks-based process to assist on the assessment of Scrum-based projects, instrumenting the software development method to assist on its continuous improvement focusing on the requirements engineering process, development team and product increments. We have built the Bayesian network using a Knowledge Engineering Bayesian Network (KEBN) process that calculates the customer satisfaction given factors of the software development method. To evaluate its prediction accuracy, we have collected data from 18 industry projects from one organization through a questionnaire. As a result, the prediction was correct for fourteen projects (78% accuracy). Therefore, we conclude that the model is capable of accurately predicting the customer satisfaction and is useful to assist on decision-support on Scrum projects.

La correcta predicción de costes es crucial para el éxito de un proyecto de ingeniería del software, dado que una estimación incorrecta puede derivar en el fracaso del mismo. Existen multitud de modelos propuestos para abordar esta parte de la gestión del proyecto, algunos orientados específicamente para proyectos de componente Web. Este trabajo trata de analizar si esta gestión específica de proyectos Web está justificada, examinando el comportamiento diferencial de los costes entre proyectos de desarrollo software Web y no Web. El análisis se centra en dos aspectos del cálculo de costes: las deseconomías de escala que se dan en este tipo de proyectos, y el impacto que conllevan algunas características de estos proyectos que son frecuentemente utilizados como cost drivers. Tras una revisión de las características principales de los desarrollos de proyectos Web, se enuncian dos hipótesis: (a) en estos proyectos las deseconomías de escala son mayores y (b) el efecto del incremento de coste que provocan los cost drivers de coste es menor para los proyectos Web. Se contrastaron estas hipótesis utilizando una base de datos con datos de proyectos reales. Los resultados sugieren que ambas hipótesis se cumplen, lo que justificaría el desarrollo y uso de modelos específicos para este tipo de proyectos.

Difficult implementation of software development projects in the automotive industry have to face the velocity strategies for the use of the latest technologies that would provide the success of this type of projects, namely the frequency of change requirements during the life cycle. Current complexity determines the implementation of development strategies that would provide optimal projects structuring from the software field. In the first part the paper presents a comparative analysis of classical life cycle of IT projects with different life cycles of AGILE projects type from the automotive industry. In the second part it is configured in a teaching manner a conceptual model, which integrates Critical Chain method, based on the philosophy Theory of Constraints (TOC) developed by Goldratt, with life cycles analyzed, to avoid delays in the project and more to cope with disturbances caused by changing requirements in the each phase of the project life cycle.

What makes elegant, valid, useful and convincing evidence? Find the answer to this question has been the work field for decades by various researchers. In the literature there is a number of papers on Empirical Software Engineering and discussed in countless discussions, workshops, conferences and special issues of journals. This article presents a reflection on the evidence; is reviewed progress in Software Engineering and attempts to answer questions such as: What is the good that has been done so far? Where will the related research? The findings show that: 1) find about convincing evidence is harder than you may think, 2) Software Engineering researchers have to work together as a community and share their achievements, and 3) it must be acknowledged that convincing evidence is a specific component context, because that is convincing for someone may not be for others. Consequently, we must be prepared to reinterpret and rescan each time you disclose something about.

Teknoloji geliştirme ve sayısallaştırma gerçek dünyayı farklı şekilde etkilemektedir. Otomatikleştirilmiş sistemler günlük hayattaki tüm işlemlere entegre olmuştur. Sürekli entegrasyon ve sürekli teslim otomatik sistemlerin kalbidir. Bu tezin amacı, yeni nesil teknolojilerle geliştirilen çevik yazılım geliştirme yaşam döngüsü üzerindeki sürekli entegrasyon ve sürekli teslim yöntemlerinin bugün ve gelecekteki etkilerini araştırmak ve tanımlamaktır.Birinci bölümde çevik yazılım geliştirme, sürekli entegrasyon ve sürekli teslim metodolojileri tarihsel gelişmeleri ile birlikte sunulmaktadır. Bu teknolojiler, dünya çapında rekabetçi oyun değiştirici efektler olarak vurgulanır, ancak diğer yazılım geliştirme yöntemlerinden farklıdır. Koşulların evrimi karşılaştırmalarla açıklığa kavuşmuştur.Daha sonraki bölümde sürekli entegrasyon ile geliştirilen otomasyon terimi tanımlanmıştır ve sürekli teslim ihtiyacının yapısı özetlenmiştir. Entegrasyonu içeren, uygulanabilir sürekli teslim modeline iyi tanımlanmış özelliklerle genel bir bakış sunulmuştur. Buna ek olarak, sayısallaştırma konusundaki büyük argümana cevap veren dijital kurumsal çözümleri, faydaları ve sürekli teslimin önemi ortaya koyulmaktadır.Öte yandan, detaylandırılmış bölümler, başarısızlığı önlemenin olası yollarıyla sürekli teslim modeli için olası tehditleri tartışmaktadır.Sonuç olarak tez, sürekli entegrasyon ve sürekli teslim metodolojileri ve teknolojilerinin işletmeleri olumlu yönde etkilediğini ve yazılım geliştirme projelerinin karını artırdığını iddia etmektedir. Detaylı bölümler, çevik yazılım geliştirme yaşam döngüsü üzerinde sürekli entegrasyon ve sürekli teslim metodolojilerinin önemini ispatlıyor.Anahtar kelimeler: sürekli teslim, sürekli entegrasyon, proje yönetimi, iş çözümleri, çevik metodolojiler, yazılım geliştirme yaşam döngüsü Technology development and digitalization affect the real world differently. Automated systems integrated every transaction in daily life. Continuous integration and continuous delivery are the heart of the automated systems. The aim of this thesis is to investigate and identify the present and future effects of continuous integration and continuous delivery methodologies on agile software development life-cycle which are improved by new generation technologies.In the first part, the term of agile software development, continuous integration and continuous delivery methodologies are presented with their historical evolutions. These technologies highlight the world-wide competitive game changer effects, but differ from other software development methodologies. The evolution of the terms clarified with comparisons.The thesis then identifies the automation term which is developed by continuous integration, and further outlines the structure of the need for continuous delivery. Detailed sections of the thesis provide an overview of applicable continuous delivery model which includes integration, progresses with well-defined properties. In addition, detailed sections reveal the digital enterprise solutions, benefits and importance of continuous delivery which answer the big argument of digitalization.On the other hand, detailed sections argue possible threats for continuous delivery model with possible ways to prevent failure.In conclusion, the thesis argues that continuous integration and continuous delivery methodologies and their technologies affect the enterprises in a positive way and increase the profit of software development projects. Detailed sections prove the importance of the continuous integration and continuous delivery methodologies on agile software development life-cycle.Keywords: continuous delivery, continuous integration, project management, business solutions, agile methodologies, software development life-cycle. 93

Risk analysis is a stage in the process of managing software projects, which largely affects the success of the project. It represents a complex and demanding process of planning, identification, analysis, response planning risks, monitoring, control, and reporting. Every software project, regardless of size, structure and project team is exposed to various types of risks. Risks can occur in the environment, but we have to accept the fact that they can not be completely eliminated. It is necessary to focus a lot of activities on risk reduction. The two most important features for improving the risk analysis process are: engaging professional resources, procurement and use of adequate software tools for risk analysis and management. This paper presents the results of comparative analysis of the 4 types of different risk management tools. We also proposed some specific measures for the selection and choice of the most appropriate of them in accordance with the requirements and needs of the user. Obtained results can help, not highly experienced software project managers, to select good risk management tool for leading their small and medium size software projects

Günlük hayatta ve iş yaşamında, birden fazla seçenek arasında kalınan tüm durumlarda bir karar verme süreci işletilmektedir. Karar vermenin gerektiği durumlarda doğru karar vermek işin başarısını doğrudan etkilemektedir.Proje seçimi problemi, çok sayıda faktörün incelenmesini gerektiren karmaşık bir Çok Kriterli Karar Verme problemidir. Projeler arasında seçim yapılırken birden fazla kriter değerlendirilerek doğru projenin seçilmesi gerekmektedir. Bu seçim durumlarında Çok Kriterli Karar Verme yöntemleri kullanılarak seçimin alternatif seçenekler arasından en uygun olanının seçilmesi sağlanmaktadır. Bu metotların kullanılması, yöneticiye karar verme sırasında yardımcı olarak doğru sonucun elde edilmesini sağlamaktır.Bu tez çalışmasında, birden fazla proje arasından seçim yapılması gereken durumlarda firmalar için en uygun proje seçimi kriterleri belirlenmiş ve Çok Kriterli Karar Verme yöntemlerinden Bulanık AHP yöntemi kullanılarak projeler arası seçme ve sıralama işlemlerinin yapılması sağlanmıştır.Bu tez çalışmasının birinci bölümünde, karar analizi ve proje yönetiminde genel konular anlatılmıştır. Burada proje yönetimi süreçlerine değinilmiş, karar verme adımları ve karar grupları kısaca anlatılarak proje seçimi için önemi açıklanmıştır. İkinci bölümde Çok Kriterli Karar Verme yöntemlerinin tanımı yapılmış, en çok kullanılan Çok Kriterli Karar Verme yöntemleri açıklanarak anlatılmıştır. Üçüncü bölümde Çok Kriterli Karar Verme yöntemlerini kullanarak seçme problemleri üzerine çalışmalar yapan kaynaklar incelenmiş, proje seçimi için gerekli kriterler analiz edilerek uygulama bölümünde kullanılacak olan projelerin seçimi için gerekli kriterlerin belirlenmesi sağlanmıştır. Proje seçimi için kriterler belirlenmiş ve hiyerarşik olarak gösterilmiştir.Son bölümde, bilişim sektöründe çalışan uzman kişilerle görüşülerek ve ilgili literatür taranarak belirlenen kriterler ve alt kriterlerin ağırlıklandırılması gerçekleştirilmiş, ardından üç farklı proje arasından seçim yapılması için bir anket çalışması yapılmıştır. Uzman görüşlerinden faydalanılarak proje seçim kriterleri analiz edilmiştir. In daily and business life, a decision-making process is run in all cases where there is more than one choice. In cases where decision-making is necessary, making the correct decision directly affects the success of the work.Project selection problem is a complex Multi Criteria Decision Making problem, which requires the examination of a large number of factors. When choosing between projects, the correct project must be selected by evaluating more than one criterion. In these selection cases, it is ensured that the most suitable alternative of the choice is selected by using Multi Criteria Decision Making methods. The use of these methods is help the manager to obtain the right result by assisting in the decision making process.In this thesis study, the most appropriate project selection criteria are determined for the firms in case of selection from more than one project and Fuzzy AHP method which is one of Multi Criteria Decision Making methods is used to select and sort the projects.In the first part of this thesis study, general cases are explained in decision analysis and project management. Project management processes are mentioned, decision making steps and decision groups are briefly explained and the importance of project selection is explained. In the second part, Multi Criteria Decision Making methods are defined and the most commonly used Multi Criteria Decision Making methods are explained.In the third part, studies which utilize Multi Criteria Decision Making methods for selection problems are examined and the criteria for project selection are analysed and the criterion to be used for the application part is determined. Project selection criteria have been identified and shown hierarchically.In the last part, a survey study is carried out to make a choice among three different projects by considering the criteria which are determined by gathering the ideas of experts and analysing the existing literature. The issues that are considered in the projects selection are analysed, and the results obtained by using Fuzzy AHP method are evaluated. Project selection criteria are analysed by using expert opinions. 136

Son yıllarda, gelişen teknolojik faaliyetlerin bir sonucu olarak yazılım ürünlerinin çeşitliliğinde önemli ölçüde bir artış gözlenmektedir. Gün geçtikçe artmakta olan bu ürün çeşitliliği beraberinde piyasada rekabet ortamının çoğalmasına ve firmaların tüketici piyasasında belirli bir hedef kitleyi elde edebilme arzusuna neden olmaktadır. Geliştirilen bu ürünlerin piyasada değer kazanmasını belirleyen en önemli etkenlerden birisini kullanıcı memnuniyeti oluşturmaktadır. Kullanıcı memnuniyeti kavramı sadece endüstriyel ürün tasarımında yer almamakla birlikte gün geçtikçe kullanıcıların günlük ihtiyaçlarının büyük bir çoğunluğunu internet ortamında gerçekleştirmelerine bağlı olarak web veya mobil platformlarda geliştirilen ürünlerin de kalitesini belirleyen önemli bir kavram niteliği taşımaktadır. İnternet ortamının bizlere sunmuş olduğu birçok hizmet neticesinde kullanıcılar birbirinden farklı yapılara, işlevlere ve tasarımlara sahip yazılım ürünleri ile karşılaşmaktadır. Günümüzde aynı işlevleri yerine getiren birçok uygulama olmasına rağmen kullanıcıların hissiyat ve beklentileri zamanla ortaya çıkan ürünlere ve teknolojilere bağlı olarak değişkenlik gösterdiği için bu ürünlerin kullanıcılar tarafından tercih edilmesi aynı oranda mümkün olmayabilmektedir. Bazı yazılım ürünleri her ne kadar kullanım bağlamı çerçevesinde benzerlik gösterse de tasarımsal açıdan genellikle farklı yapılarda olabilmektedir. Özellikle web ve mobil platformlarda geliştirilen yazılım ürünlerinin çeşitliliği kullanıcı deneyimleri doğrultusunda kullanılabilirlik kavramının önem kazanmasına sebep olmuş ve aynı zamanda ürün tasarımlarının ne kadar işlevsel ve tatminkar olduğunun belirlenmesine imkan sağlamıştır. Bu tez çalışmasında Detaysoft firmasına ait geliştirilmekte olan BNet uygulaması üzerinde şirket içerisindeki personel grupları dikkate alınarak uygulama içerisinde görevlerin gerçekleştirilebilme dereceleri ve süreleri değerlendirilerek tasarım sürecinin ve ürünün daha kullanıcı odaklı bir hale getirilmesi amaçlanmıştır. Kullanıcılara daha önceden belirlenmiş olan bir takım görevler sunularak her bir görevin başarı ve hata oranları ile birlikte tamamlanma süreleri dikkate alınarak uygulama arayüzünde karşılaşılan kullanılabilirlik problemlerinin belirlenmesisağlanmıştır. Ağaç testi yapılarak uygulama içerisinde yer alan farklı işlevlerin hiyerarşik olarak doğru menülerin altında bulunup bulunmadığına, ilk tıklama testi ile kullanıcılara verilen görevler neticesinde arayüz üzerinde test kullanıcılarının ekran üzerinde odaklandıkları ve tıkladıkları ilk bölgeye ait bilgilere ve uygulanan sistem kullanılabilirlik anketi ile de ürünün kullanıcılarına nasıl bir deneyim yaşattığına dair bilgilerin elde edilmesi ile uygulamanın sahip olduğu arayüzlerin kullanımının kolay ve kullanıcı odaklı olması sağlanmıştır., In recent years, a large increase in software product variety has been observed as a result of developing technological activities. This growing variety of products is leading to the increase of competitive environment in the market and the power to obtain a certain target audience. User satisfaction is one of the most important factors determining the value of these developed products in the consumer market. The concept of user satisfaction is not only involved in industrial product design but it is also an important concept that determines the quality of products developed on the web or mobile platforms depending on the fact that daily necessities of users are realized on the internet. As a result of many services that the internet environment has presented to us, users are faced with software products with different structures, functions and designs. Although there are many applications that fulfill the same functions today, it is not possible for users to prefer these products to the users because the feelings and expectations of the users vary depending on the products and technologies that develop over time. Although some software products show similarity in terms of usage purpose, they are usually different in terms of design. The diversity of software products, especially developed on web and mobile platforms, has led to the concept of usability in the direction of user experience, and at the same time has enabled the determination of how functional and satisfactory the product designs are. In this thesis project, it was aimed to make the design process and the product more user-oriented by evaluating the information architecture, the degree and the duration of the execution of the tasks by considering the staff groups in the company on the BNet application developed by Detaysoft. A number of tasks are presented to the user, summarized on a task-by-task basis in order to determine the success and failure rates of each task, the completion times, and the usability problems. The results of card grouping studies show that the users of the information architecture are informed that the different functions included in the application are hierarchically right under the menus by tree testing and that the different prototypes designed with A / B tests are left on the users, As a result of the tasks, the test users on the interfaceare focused on the screen and the first point of click information is obtained and the interface designs are easy to use and user-oriented.

Software project manager's goal is getting an optimal allocation of time, cost and quality of each task/activity in the software project such that total time and cost of the project is minimized while project quality is maximized. Accordingly, mathematical and meta-heuristic algorithms have been developed in order to solve such riddle. This research paper introduces a new proposed meta-heuristic algorithm annotated as problem data based optimization (PDBO), which enjoys the fastness and achieves an optimal/near optimal solution for solving the discrete time- cost-quality trade-off problem (DTCQTP) in software projects. PDBO decides the preferred modes of performing tasks where task quality is expressed quantitatively in terms of its defects. Examples are given at the end to show the trade-off analysis between project's cost, time and quality.

Offshore project success is very much important to both customer and the vendor. Based on very less success rate of overall software projects globally, critical success factors (CSFs) for offshore software projects is gaining much importance. In the current study based on literature review, a total of 75 success factors for offshore software projects are identified. Further based on their appearance in literature 20 critical success factors from 10 CSF categories are identified. Finally top six most critical success factors for offshore software projects such as trust, efficient communication, cultural understanding, relationship between client and vendor, contract type and efficient knowledge transfer are identified. The CSFs categories are prioritized in the order of importance. The important CSF categories for offshore projects found are organizational factors (both client and vendor), project factors, cultural factors and environmental factors. Uspešnost “offshore” projektov je zelo pomembna tako za kupca kot za prodajalca. Glede na mnogo nižji delež uspešnosti “offshore” programskih projektov v primerjavi z drugimi projekti s področja razvoja programske opreme, je kritičnim dejavnikom uspeha za “offshore” programske projekte namenjeno veliko pozornosti. Naša raziskava je na podlagi pregleda literature identificirala petinsedemdeset dejavnikov uspeha za te projekte. Nadalje je bilo glede na pogostost pojavljanja v literaturi opredeljenih dvajset kritičnih dejavnikov uspeha iz desetih kategorij dejavnikov. Raziskava je izpostavila kot šest najpomembnejših kritičnih dejavnikov uspeha zaupanje, učinkovito komunikacijo, kulturno razumevanje, odnos med kupcem in prodajalcem, tip pogodbe in učinkovit prenos znanja. Kot pomembne kategorije kritičnih dejavnikov uspeha za “offshore” projekte (KDU) je raziskava ugotovila organizacijske dejavnike (tako kupca kot prodajalca), projektne dejavnike, kulturne dejavnike in okoljske dejavnike.

Expectation confirmation research in general, and in information systems (IS) in particular, has produced conflicting results. In this paper, we discuss six different models of expectation confirmation: assimilation, contrast, generalized negativity, assimilation-contrast, experiences only, and expectations only. Relying on key constructs from the technology acceptance model (TAM), we test each of these six models that suggests different roles for expectations and experiences of the key predictor-here, perceived usefulness- and their impacts on key outcomes-here, behavioral intention, use, and satisfaction. Data were collected in a field study from 1,113 participants at two points in time. Using polynomial modeling and response surface analysis, we provide the analytical representations for each of the six models and empirically test them to demonstrate that the assimilation-contrast is the best existing model in terms of its ability to explain the relationships between expectations and experiences of perceived usefulness and important dependent variables-namely, behavioral intention, use, and satisfaction-in individual-level research on IS implementations. Accepted version Source info: Brown, S.A., Venkatesh, V., and Goyal, S. 'Expectation Confirmation in Information Systems Research: A Test of Six Competing Models,' MIS Quarterly (38:3), 2014, 729-756. https://doi.org/10.25300/MISQ/2014/38.3.05

Yazılım projeleri, günümüzde hayatın her alanında yer almaktadır. Bu durum, söz konusu projelerin hacminin ve karmaşıklığının artmasına sebep olmaktadır. Böylece, projelerde kritik hatalar meydana gelmekte ve geliştirilen yazılımların kullanıldığı alanlarda olumsuz sonuçlar doğmaktadır. Bu hataları önlemek veya minimuma indirmek için `Yazılım Risk Yönetimi` faaliyetlerinin eksiksiz bir şekilde uygulanması gerekmektedir. Bu çalışmada, yazılım projeleri için yapay zekâya dayalı risk yönetimi sağlayan web tabanlı bir model önerilmiştir. Önerilen model, proje iş paketleri ve çıktıların risk düzeylerine göre yazılım projesinin bütçe, takvim, personel sayısı, projenin hedefi ve proje başarısı gibi değerlerinde oluşabilecek sapmaları tahmin edebilmektedir. Çalışmada, risk faktörlerinin belirlenmesi için yazılım mühendisliği alanındaki akademisyen, uzman ve proje yöneticileriyle öngörüşmeler yapılmıştır. Teknokent'lerde bulunan 774 farklı yazılım firmasından toplamda 467 adet gerçek yazılım proje verisi toplanmıştır. Toplanan veriler, genel proje verileri ve proje süreci içerisinde karşılaşılan risk faktörlerini içermekte olup modelin girişlerini oluşturmaktadır. Modelin çıktıları ise, projenin süresinde, bütçesinde, personel sayısında, hedeflerde ve başarısındaki sapmalardır. Modelin eğitimi için ileri beslemeli çok katmanlı ağ mimarisi kullanılmıştır. Model; 45 giriş, tek gizli katman (15 nörona sahip) ve 5 çıkışa sahiptir (45-15-5). Analiz sonuçları, önerilen modelin performansının yüksek olduğunu (Eğitim Regresyon Oranı 0,9978, Test Regresyon Oranı 0,9935 ve Hata Oranı 0,001) ve yazılım projeleri için risk yönetim faaliyetlerinde yapay sinir ağları kullanımının etkili olduğunu açıkça ortaya koymuştur. Ayrıca, geliştirilen risk yönetim sistemi irdelendiğinde, uygulamanın kullanılabilirliğinin yüksek, cevap verme süresi (ms)'nin (işlem performansının) hızlı olduğu ortaya çıkmıştır. Geliştirilen yaklaşımla, yazılım risk faktörlerinin meydana gelmeden önlenmesi sağlanmaktadır. Software projects are in every aspect of life nowadays. This leads to an increase in the size and complexity of these projects. Thus, critical errors occur in projects and negative results occur in areas where developed software is used. Therefore, `Software Risk Management` activities must be fully implemented to prevent or minimize this errors. In this study, a web-based model was proposed that provides artificial intelligence based risk management for software projects. Suggested model can predict the deviations of the software project such as budget, calendar, number of personnel, project target and project success based on the risk levels of the project work packages and outputs. In the study, preliminary interviews were held with the academicians, experts and project managers in the field of software engineering to determine the risk factors. A total of 467 actual software project data have been collected from 774 different software companies located in Technoparks. The collected data includes the general project data and the risk factors encountered in the project process and constitutes the inputs of the model. Outputs of the model are deviations on the duration, budget, number of staff, targets and success of the project. Forward-feed multi-layer network architecture is used for training of the model. Model have 45 inputs, a single hidden layer (with 15 neurons) and 5 outputs (45-15-5). The results of the analysis clearly show that the performance of the suggested model is high (Training Regression Rate is 0.9978, Test Regression Rate is 0.9935 and Error Rate is 0.001) and that the use of artificial neural networks in risk management activities for software projects is effective. In addition, when the developed risk management system are examined, it has been found that the usability of the application is high and the response time (ms) (transaction performance) is fast. With the developed approach, it is ensured that software risk factors are avoided. 194

Günümüzde bir projeyi başarılı kılmak yazılım geliştirmekten daha önemlidir. Müşteri gereksinimlerine karşılık vermeyen her yazılım doğru zamanda ve maliyeti aşmadan bitmiş olsa da başarılı olduğu söylenemez. Bu durumun yaşanmaması için farklı yazılım geliştirme yöntemleri bulunuyor. Çevik yöntem bunlardan biridir. Çevik yöntem temelde sabit bir planı izlemek yerine değişikliklere açık müşteriyle yakın iletişime öncelik verir. Müşteri ve geliştirme takımı etkileşimi büyük öneme sahiptir. Geliştirme sürecinde müşterinin görsel olarak yazılımın nasıl çalışacağını ve süreci anlaması, bunlara göre geri bildirimlerde bulunması zorunludur.Bu tez çalışmasında müşterinin yazılım hakkındaki bilgi ve geri dönüşünü en yüksek seviyeye çıkarabilmek için bir araç geliştirilmiştir. Müşteri yazılım ekranını görebilmekte ve herhangi bir görsel öğeyi yorumlayabilmektedir. Analist, yazılımcı, proje yöneticisi gibi farklı kullanıcılar araç içerisinde farklı yetkilere sahiptir. Bazı kullanıcılar yorum ekleyebilirken diğerleri sadece mevcut yorumları görüntüleyebilmektedir. İkinci bölümde, Çevik yöntemle ilgili literatür taramasını yer verilmiştir. Farklı yaklaşımlar incelenmiştir. Bunların eksik yönleri bulunmuş, geliştirdiğimiz araçla karşılaştırılmıştır. Üçüncü bölümde, geliştirilen Çevik aracın mimari ve akış detayları ile başarısını ölçmek için yapılan anket ve mülakat sorularına yer verilmiştir. Dördüncü bölümde, geliştirme detayları ve değerlendirme sonuçları açıklanmıştır. Son olarak, beşinci bölümde, sonuçlar yorumlanmış ve tez sonlandırılmıştır. Bu tezin amacı, müşteriye kendi ifadeleri ile projedeki her bireye düşüncelerini iletebileceği bir ortam sunmaktır. Böylece dokümantasyon azaldığı gibi somut bilgiler üzerinden proje sonuçlandırılacaktır. Geri bildirimin fazlalaşıp iletişimin hızlanmasıyla projenin başarı şansı yükselecektir. Değerlendirme sonuçlarından da gördüğümüz gibi gereksinimler ve proje arasındaki uyumsuzluklardan kaynaklanan maliyet ve zaman değişiklikleri en aza indirgenecektir. In today's world, successful completion of a project is more important than software development. A software that does not answer customer requirements cannot be considered successful even if it is completed in timely manner and within budget. To avoid such cases, various software development methods are present. Agile method is one of these. In essence, Agile method puts emphasize on close communication with customer who is open to changes rather than following a static plan. Interaction between the customer and the development team is of great importance. In development process, it is necessary that customer understands the process and how the software will work visually, as well as customer gives feedback based on that knowledge.In this thesis work, a tool is developed to maximize the knowledge and feedback of the customer about the software. Customer can observe the software screens and can comment on any visual element. Different user types such as analyst, software developer, or project manager have different permissions in the tool. Some users can add their comments while others can only view existing comments.In the second section, a literature review on Agile method is presented. Different approaches examined. Their shortcomings are provided and they are compared to the proposed tool. In the third section, architecture and flow details of the proposed tool as well as survey questions about its performance are given. In the fourth section, implementation details and evaluation results are explained. Finally, in the fifth section, these results are discussed and the thesis is concluded.Aim of this thesis is to provide a platform to the customer where they can convey their comments to each participant of the projects. Thus, documentation would be decreased whereas project would be completed based on concrete information. Success rate of projects would increase thanks to increased feedback and quick communication. As evaluation results demonstrate, cost and time changes due to incompatibility between requirements and project would be minimized. 60

Companies working on safety-critical projects must adhere to strict rules imposed by the domain, especially when human safety is involved. These projects need to be compliant to standard norms and regulations. Thus, all the process steps must be clearly documented in order to be verifiable for compliance in a later stage by an auditor. Nevertheless, documentation often comes in the form of manually written textual documents in different formats. Moreover, the project members use diverse proprietary tools. This makes it difficult for auditors to understand how the actual project was conducted. My research addresses the project mining problem by exploiting logs from project-generated artifacts, which come from software repositories used by the project team.

Proje yönetimi bir çok alanda uygulanmakta olan bir disiplin olup, en temel işlevi; proje ile ilgili kısıtların, temel çizgilerin ve hedeflerin belirlenmesi, bu temel çizgi ve hedeflerin izlenmesi, kontrolü ve sapmaların belirlenerek, gerekli eylem planlarının belirlenip uygulanmasının sağlanmasıdır. 2000'lere doğru başlayan dijitalleşme trendi ile hızla bilişim projeleri birbirlerini takip etmiştir. Dijitalleşme başlığı altında Yazılım projeleri de bu başlık altında önemli bir yer tutmaktadır.Disiplinler arası çalışma becerisi gerektiren proje yönetiminin, hedeflerine ulaşmada faydalanacağı kriterlerinin belirlenmesi, ölçülmesi ve değerlendirilmesi, performans kavramını öne çıkarmıştır. Yazılım projelerinin doğası gereği varolan özellikleri sebebiyle standart proje performans değerlendirme yöntemlerinin birebir uygulanması ihtiyaçlara tam olarak cevap verememektedir. Bu nedenle mevcut performans değerlendirme yöntemlerinin yazılım projelerine özel olarak ele alınması gereği ortaya çıkmaktadır. Bu amaçla projelerde en sık kullanılan; Dengeli Skor Kartı, Kazanılmış Değer Yönetimi ve Anahtar Performans Göstergeleri esaslı performans değerlendirme ve yönetim tekniklerinin yazılım projeleri için ne şekilde uygulandığı ele alınmıştır. Gerek yazılım projelerinin karakteristiği gereği ortaya çıkan ihtiyaçlar, gerekse proje yönetimi süreçlerinin başarısı için performans yönetimi disiplininin önemi; proje yönetiminde performans yönetimi konusu bütüncül bir yaklaşım ile ele alınması gerektirmektedir. Bu nedenle çalışmada, bütünleşik bir performans değerlendirme ve yönetim yaklaşımı olarak, proje yönetim süreçlerine paralel, 4 aşamalı bir süreç önerilmiştir.•Tanımlama : Gerek proje adımları ve kilometre taşları için gerekse proje sonucu için hedeflerin belirlenmesi aşamasıdır.•Planlama: Tanımlı hedefler için başarı kriterlerinin tanımlanması, formüle edilip, hedef değerinin ve ağırlığının belirlenmesi, hangi aşamada, kim tarafından, nasıl ölçüleceğinin ortaya konmasıdır.•Süreç Performans Yönetimi : Bu adımda proje süreci boyunca performansın değerlendirilmesi ve yönetimi hedeflenmektedir. Bu nedenle performans göstergeleri için proje yönetimine ilişkin bilgi alanları bazında bir sınıflandırma yapılmış, bilgi alanları bazında performans gösterge haritası çıkarılmıştır.•Sonuç Performans Ölçümü: Yazılım projeleri özelinde projenin sonucu itibariyle hedefe ulaşma durumunun ölçülmesi için gerekli performans kriterleri belirlenmiş ve buna göre proje çıktıları bu adımda değerlendirilmektedir. Project management is a dicipline that can be applied on different fields, that has the main function of defining project constraints, baselines, objectives, monitoring and controling the project progress according to these baselines, objectives and finding the variances and defining the needed action plans as aresult of measuring performance and determining the need to request changes. Especially starting in 2000's, many IT projects started with the digitalization trend and especially software projects took an important place in the digitalization With multidisciplinary properties of the Project Management, defining the creteria to reach the objectives, measurement and evaluation of the project progress, make the `performance` concept more important. Because of the nature of Software Projects, the standart use of performance measurement processes can not answer all the needs of software projects. For this reason there is a need for customization of performance measurment and evaluation methods for software projects. Balanced Scorecard Method, Earned Value Method, Key Performance Indicators were analysed as Project Performance Management methods and how these can be used in software projects. Because of the needs related with the characteristics of software projects and the importance of the performance management in project success, it is neccessary to develop an integrated approach for performance management. For this reason an integrated performance measurement and management process is suggested paralel to the project management process as 4 steps;•Defining: The step in that we define the objectives both for project pahes and milestones and for products as output of projects.•Planning: In this step, we define the success criteria of all defined objectives, formulize the targets with weight of them and defining at which steps, how these will be measured, by whom.•Process Performance Management : In this step, we evaluate and manage the performance of the projecet management process. For this reason we use the 10 knowledge areas of the project management to classify the performance indicators and to prepare a performance indicator map.•Output Performance Measurement : In this step, we measure and evaluate the outputs of software projects with the defined performance criteria to reach the objectives of software projects. 239

Günümüzde yazılım, günlük eğlencemizden en karmaşık iş süreçlerine kadar hayatımızın her alanında yerini almış ve etkileri hissedilen bir olgudur. Şirketler, iş süreçlerinin yönetimi için etkin yazılım sistemlerine ihtiyaç duyarlar ve bu sistemleri bilgi sistem departmanları vasıtasıyla üretir ya da yazılım şirketlerinden tedarik ederler. Her iki durumda da yazılımın üretilmesi bir dizi mühendislik ve proje yönetim sürecini gerektirir. Bu süreçlerin metodoloji seçiminde, üretilecek yazılımın büyüklüğü, karmaşıklığı ve kullanım maksadı gibi karakteristik özellikleri, yazılımı üretecek organizasyon ve proje ekibinin yapısı ve kullanılabilecek kaynaklar önem arz eder. Bu çalışmada, yazılım proje başarısına etki ettiği değerlendirilen faktörler temel alınarak bir inceleme ve karşılaştırma ortaya konulmuş; yazılım proje yönetimi metodolojisi seçimi konusunda önerilerde bulunulmuştur. Bu karşılaştırmalarda, 12 durumda çevik yöntemlerin; 9 durumda şelale modelinin avantajlı olduğu değerlendirilmiştir. Elde edilen sonucun, deneysel tecrübe ile karşılaştırılması maksadıyla yazılım sektöründen 97 çalışanın katılımıyla bir anket uygulanmıştır. Anket sonucunda, 1 kriterde şelale modeli tercih edilirken, 48 kriterde çevik yöntemler tercih edilmiştir. Elde edilen cevapların ağırlıkları kullanılarak metodolojiler açısından genel bir karşılama oranı hesaplanmıştır. Metodoloji seçimini etkilediği değerlendirilen kriterlerin karşılama oranları çevik yöntemler için %67,4; şelale modeli için % 51,91 olarak elde edilmiştir. In our time, software is a fact, the influence of which is strongly felt and has attained its place in our lives from daily entertainment to the most complex business processes. Corporations need efficient software systems in order to manage their business processes and they either produce these systems through the agency of their information systems departments or procure from software companies. In both situations, the production of software requires a series of engineering and project management processes. In selection of methodology for these processes, the characteristics of software such as size, complexity and purpose of use, the structure of the project team and organization which are to produce the software and available sources are important. In this study, an analysis and a comparison of waterfall model and agile methodologies based on factors which are evaluated to affect the success of software projects are presented and propsals about selecting a methodology for software project management are submitted. In these comparisons, waterfall model is found to be advantageous in 9 situation and agile methodologies in 12 situations. In order to compare the reults obtained. a survey is organized with the participation of 97 employees in software industry. In survey results, waterfall model is favoured in 1 criteria while agile methodologies in the rest 48. A general coverage ratio is calculated using the weights of the criteria. The coverage ratios of criteria which are evaluated to affect the success of software projects are % 51,91 for waterfall model and %67,4 for agile methodologies. 117

El proceso de requisitos es una etapa fundamental en todo proyecto de desarrollo de software pues, junto con la gestión de requisitos, garantizan que el producto desarrollado satisfaga efectivamente las necesidades que realmente tiene el cliente. Para lograrlo, la Ingeniería de Requisitos plantea la ejecución disciplinada de una serie de actividades entre las que adquiere gran relevancia, por su papel en la consecución de la calidad, la especificación o definición de los requisitos. Sin embargo, este es un proceso riguroso, complejo y que requiere de conocimiento muy específico que pocas universidades en el país ofrecen, razón por la cual, en la región se dificulta encontrar profesionales con dominio en esta temática. Entonces, ¿Cómo logran las MiPymes de la industria local del software realizar una adecuada especificación de requisitos?, el presente trabajo pretende hacer un acercamiento a la manera en que las empresas de la ciudad de Pereira manejan el tema de los requisitos, análisis que hace parte de la tesis doctoral titulada "modelo de aseguramiento de calidad para los requerimientos en proyectos de software desarrollados en las MiPymes de la ciudad de Pereira", como aporte a un sector que busca aumentar sus niveles de madurez y calidad. The development of requirements is a fundamental step in any software development project because, along with requirements management, ensures that the product developed effectively meets the needs that the customer really has. To achieve this, the Requirements Engineering raises the disciplined execution of a series of activities, among which is highly significant for its role in achieving quality, specification or definition of the requirements. However, this is a complex and rigorous process, and requires very specific knowledge that few universities in the country offer, so that, it is difficult to find qualified professionals for this specific domain in the region. So, ¿how can the local software industry (MSME) offer an appropriate specification requirements?, this article aims to make an approach to the way companies located in the city of Pereira face the topic about requirements; the analysis makes part of an ongoing research project that aims to "develop a procedure to specify and validate software requirements based on previous studies in the region", as a contribution to a sector that seeks to increase its levels of maturity and quality. O processo de requisitos é uma etapa fundamental em todo projeto de desenvolvimento de software, pois, junto com a gestão de requisitos, garantem que o produto desenvolvido satisfaça efetivamente as necessidades que o cliente realmente tenha. Para alcança-lo a Engenharia de Requisitos elabora e propõe a execução disciplinada de uma serie de atividades entra as que adquire grande relevância, por seu papel na consecução de qualidade, a especificação ou definição dos requisitos. Entretanto este é um processo rigoroso, complexo e que requer conhecimento muito especifico que poucas universidades no país oferecem, razão pela qual, na região se dificulta encontrar profissionais com domínio nesta temática. Então, Como logram as MiPymes da indústria local de software realizar uma adequada especificação de requisitos? O presente trabalho pretende fazer uma aproximação à maneira em que as empresas da cidade de Pereira manejam o tema de requisitos, análise que faz parte da tese doutoral titulada "modelo de garantia de qualidade para os requerimentos em projetos e software desenvolvido nas MiPymes da cidade de Pereira", como aporte a um setor que busca aumentar seus níveis de maturidade e qualidade.

In software engineering education, the goal is often to provide students with authentic assignments using actual tools of the trade. Students are often allowed to select their preferred tools without specifying what to use for e.g. communication within the team, scheduling, bug tracking, etc. However, there is an abundance of tools to choose from with more appearing rapidly, which can make it difficult for students or staff to select appropriate tools for each task. In this paper, we study the suitability of several commonly used communication and collaboration tools on different tasks that students encounter in team assignments. We surveyed students' experiences with different tools in a university-level web software development course.