Прогнозування трудомісткості розробки програмних систем за допомогою нечіткої гібридної моделі

Для прогнозування трудомісткості розробки програмних систем запропоновано використаннянечіткої гібридної моделі, у якій антецеденти правил задаються нечіткими термами, аконсеквенти – лінійними залежностями “входи – вихід” з нечіткими коефіцієнтами. Заекспериментальними даними проведено ідентифікацію залежності трудомісткості розробкипрограмних модулів від стажу програміста, новизни та складності завдання. Установлено, щозапропонована нечітка гібридна модель забезпечує вищу точність порівняно з іншими п’ятьмаконкурентними моделями

Web development productivity improvement through object-oriented application framework

Most of the commercial and industrial web applications are complex, difficult to implement, risky to maintain and requires deep understanding of the requirements for customization. As today's software market is more competitive, productivity has become a major concern in software development industry. The aim of this research is to design and develop an application framework for accelerating web development productivity through object-oriented technology. It allows customization, design reuse and automatic code generation to support productivity improvement as a breakthrough solution for the given problem. This research employed systematic literature review (SLR) to identify the source of complexity and productivity factors. Agile development methodology was used to design the framework and it was validated by empirical data from two commercial projects. Results showed that object-oriented application framework (OOAF) has significant factors that affect productivity and dramatically improve higher productivity over traditional approach. It has fulfilled the current needs by reducing complexities, development efforts and accelerates web development productivity. This research contributes in the area of software engineering, specifically in the field of software productivity improvement and software customization. These will lead to faster development time for software industries

Measures related to social and human factors that influence productivity in software development teams

Software companies need to measure their productivity. Measures are useful indicators to evaluate processes, projects, products, and people who are part of software development teams. The results of these measurements are used to make decisions, manage projects, and improve software development and project management processes. This research is based on selecting a set of measures related to social and human factors (SHF) that influence productivity in software development teams and therefore in project management. This research was performed in three steps. In the first step, there was performed a tertiary literature review aimed to identify measures related to productivity. Then, the identified measures were submitted for its evaluation to project management experts and finally, the measures selected by the experts were mapped to the SHF. A set of 13 measures was identified and defined as a key input for designing improvement strategies. The measures have been compared to SHF to evaluate the development team\u27s performance from a more human context and to establish indicators in productivity improvement strategies of software projects. Although the number of productivity measures related to SHF is limited, it was possible to identify the measures used in both traditional and agile contexts

Proceedings of the 1st international workshop on software process education, training and professionalism (SPETP 2015)

These Proceedings contain the papers accepted for publication and presentation at the first 1st International Workshop on Software Process Education, Training and Professionalism (SPETP 2015) held in conjunction with the 15th International Conference on Software Process Improvement and Capability dEtermination (SPICE 2015), Gothenburg, Sweden, during June 15-17, 2015. During the 14th International Conference on Software Process Improvement and Capability dEtermination (SPICE 2014) held in Vilnius, Lithuania, at a post conference dinner, a group of key individuals from education and industry started to discuss the challenges faced for software process education, training and professionalism, especially with the background of the new modes of learning and teaching in higher education. Further discussions held post conference with key players in the relevant professional and personal certification fields led to a consensus that it is time for the industry to rise to the new challenges and set out in a manifesto a common vision for educators and trainers together with a set of recommendations to address the challenges faced. It was therefore agreed co-located the 1st International Workshop on Software Process Education, Training and Professionalism with the 15th International Conference on Software Process Improvement and Capability dEtermination. This workshop focused on the new challenges for and best practices in software process education, training and professionalism. The foundation for learning of software process should be part of a university or college education however software process is often treated as ‘add one’ module to the core curriculum. In a professional context, whilst there have been a number of initiatives focused on the certification related to the software process professional these have had little success for numerous reasons. Cooperation in education between industry, academia and professional bodies is paramount, together with the recognition of how the education world is changing and how education is resourced, delivered (with online and open learning) and taken up. Over the next 10 years on-line learning is projected to grow fifteen fold, accounting for 30% of all education provision, according to the recent report to the European Commission on New modes of learning and teaching in higher education. It is a great pleasure to see the varied contributions to this 1st International Workshop on Software Process Education, Training and Professionalism and we hope that our joint dedication, passion and innovation will lead to success for the profession through the publication of the manifesto as a key outcome from the workshop. On behalf of the SPETP 2015 conference Organizing Committee, we would like to thank all participants. Firstly all the authors, whose quality work is the essence of the conference, and the members of the Program Committee, who helped us with their expertise and diligence in reviewing all of the submissions. As we all know, organizing a conference requires the effort of many individuals. We wish to thank also all the members of our Organizing Committee, whose work and commitment were invaluable

Study of Productivity Rates for Geographically Distributed Agile Teams

A reality for many information technology (IT) organizations is the need to hire IT talent from other cities or countries to supplement their employee staff. As organizations extend their software development work to remote locations, however, a distinct productivity gap can emerge between co-located and distributed teams. The problem this study addresses is the reduced productivity levels for teams practicing the Agile methodology when team members are distributed by location or time zone. Specifically, it was unknown if there are organizational factors which can improve the productivity of these distributed development teams. The purpose of this study was to determine whether any amount of separation of team members impacts productivity, or if various degrees of time zone overlap allows for sufficient synchronous communication to overcome the communication lag inherit with having distributed teams. Productivity was measured by the number of story points per cycle day completed by the team. Two additional variables were collected to study the impact of sourcing and task complexity on distributed team productivity. A quantitative data analysis was conducted on a large, globally distributed technology organization practicing the Agile methodology across the Americas, Europe, Africa, Asia, and Australia. Teams were classified in the study based on the amount of time zone overlap of the team members. The results of the study found that teams which were co-located or had any amount of time zone overlap performed at similar levels of productivity, while teams with no overlapping business day experienced significantly lower levels of productivity (p \u3c .05). Conversely, sourcing of the resources either as contractors or employees did not demonstrate a significant difference in team productivity. The data analysis on task complexity showed mixed results; there was a different level of productivity when some teams were working tasks of different complexity, but the data was further nuanced by team member location. This study indicates the importance of resource location as a key factor in team productivity. Further study on organizational design could be beneficial to better understand how organizations should select locations to optimize productivity

Demographic change: towards a framework to manage IT- personnel in times of scarcity of talent

En un entorno en el que el crecimiento demográfico negativo es una realidad en la mayoría de los estados europeos, las organizaciones deben enfrentar necesidades incrementos de la productividad laboral y una menor disponibilidad de empleados competentes. Uno de los sectores en que la situación expuesta es más evidente es el de las Tencnologías de la Información. Las teconologías de la información son cruciales para casi cualquier organización en cualquier sector y para cualquier persona. En un entorno socioeconómico en continuo cambio las organizaciones y sus departamentos de tecnologías de la información deben asumir los cambios en el mercado y ser capaces de desenvolverse de una forma ágil y con una orientación al cliente sin precedentes. Para las organizaciones, y en particular para sus elementos organizacionales más relacionados con las tecnologías de la información, la productividad de los empleados es un componente clave. De esta forma, la gestión de los recursos humanos, abarcando aspectos como su selección, desarrollo y retención es un aspecto clave para las organizaciones. El reto para las organizaciones es lograr la mejora en el ámbito de los procesos corporativos incluyendo como una parte importante de los mismos la gestión de los recursos humanos. La simbiosis de disciplinas como las tecnologías de la información, la economía, la psicología y la gestión puede lograr el incremento de la lealtad de los empleados. Para los profesionales modernos, los cambios de empleador se consideran dentro de la normalidad hasta encontrar un entorno adecuado que colme sus expectativas y necesidades. Dichas expectativas no se encuentran basadas únicamente en incentivos económicos, por lo que las organizaciones deben anticipar las expectativas y alinear sus estrategias a las expectativas de su fuerza laboral. La temática de este trabajo ha tenido repercusión en la literatura científica, sin embargo, no existe un estudio que identifique los factores que se presentan y determinan la retención de los trabajadores de las tecnologías de la información en los entornos organizacionales. Este es el objetivo de la presente tesis doctoral. Para ello, el primer paso que se pretende dar es concretar los aspectos organizacionales que son relevantes para el estudio del fenómeno. A partir de esta identificación, el autor diseña un marco en el que las partes identificadas se encuentran conectadas. El citado marco de trabajo presenta cinco niveles. Estos cinco niveles son: los salarios, la educación y capacidad de fuerza laboral, salud psicológica, salud fisiológica y balance de la vida laboral y profesional. Adicionalmente, el marco de trabajo presenta una aproximación jerárquica. Cada nivel presenta diferentes factores y métricas para definir y medir la situación organizacional ofreciendo oportunidades de derivar medidas para mejorar la situación. El marco de trabajo presenta 22 factores y 44 métricas. Adicionalmente, se ha desarrollado un modelo de implantación para el método propuesto. Con vistas a refinar el marco de trabajo y su modelo de implantación, se han llevado a cabo pruebas cualitativas y cuantitativas en el seno de un departamento de tecnologías de la in-formación perteneciente a una organización dedicada a los servicios financieros en Alemania. Se formularon y respondieron diversas preguntas de investigación en relación a ámbitos como el cambio demográfico, el estrés y los factores para el rendimiento laboral. Los resultados demuestran que el estrés está determinado por diferentes factores y que la mayoría de ellos deben ser tomados en consideración en la asignación de tareas y en el diseño de los entornos de trabajo. De la misma forma, se presentan diversos factores que incrementan la productividad laboral. Algunos de ellos como la conciliación de la vida laboral y la personal, la cultura organizacional o el salario deben ser tomados en consideración en las estrategias de gestión de recursos humanos en ámbitos organizacionales. Una estrategia de gestión de recursos humanos debe incluir adicionalmente aspectos relativos al reclutamiento, teniendo en cuenta la complentaridad con los factores anteriormente expuestos. Los resultados obtenidos también revelan que no existen evidencias de diferencias de género o de edad en la importancia de los factores de productividad o en los factores de estrés.Due to an unsatisfying demographic development in most European states, companies have to solve a trade-off between a needed increase of productivity on the one hand and fewer highly skilled employees on the other hand. One of the first sectors that will be influenced by this development is the Information Technology-industry (IT). Information technology is crucial for every company in every industry and for the people itself. In a permanently changing business environment, companies and especially their IT-departments must adapt to changes in the market and be more agile and customer oriented than ever before. To succeed in the IT sector, the productivity of employees is the key comonent. Therefore, the allocation and retention of these scarce resources in the best possible way is even more important. The challenge for companies is to improve the enterprise not only on the side of the organizational and process level, but to develop new strategies and approaches in human resource management. Only a symbiosis of the disciplines information technology, economics, psychology and management will enable relevant and indispensable employees to promote loyalty to the company. For a well-trained professional, frequent change of the employer, is as long associated with normality until the employees find the most suitable environment for fulfilling their needs and expectations. These expectations are no longer just based on financial incentives, consequently companies need to anticipate these expectations and align their strategies to them. Although the topic is quite popular in scientific literature, there is not a study devoted to identify these factors in organizational contexts. This Thesis is aimed to bridge this gap. The first step to achieve this goal is creating transparency over all parts of an organisation that are relevant to this topic. The author created a method that connects these relevant parts in one holistic framework. The framework consists of five layers. These layers are baseline wages, education and employee pool, psychological healthiness, physiological healthiness and work live balance. Also, the framework follows a hierarchical approach. Every layer has distinct factors and metrics to define and measure the status of the company and offers opportunities to derive measures to improve this situation. In total the framework consist of 22 factors and 44 metrics. Besides the framework, the author developed an implementation model for the proposed method. To refine the developed framework and implementation model, qualitative and quantitative tests were conductedn the IT-department of a financial service company in Germany. X Several research questions regarding demographic change, psychological stress and factors for employee performance were analysed and answered. The results show, that stress is influenced by several different stressors and the most of them need to be considered by companies when they allocate work or design workspaces. On the other side, there are several factors that promote employee productivity. Some of them, like work-life balance, company culture or salary are more important and should be a relevant part of every human resource management (HRM) strategy. A HRM strategy should involve proper measures for the recruiting and the development of employees because they complement each other and should be considered with the same importance. The results also show, that there is no evidence suggesting an age or gender related difference of the importance or the impact of productivity factors or psychological stressors.Programa Oficial de Doctorado en Ciencia y Tecnología InformáticaPresidente: Antonio de Amescua Seco.- Secretario: Edmundo Tov0ar Carlo.- Vocal: Cristina Casado Lumbrera

Rethinking Productivity in Software Engineering

Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll Learn Review the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology. ; Collects the wisdom of software engineering thought leaders in a form digestible for any developer Shares hard-won best practices and pitfalls to avoid An up to date look at current practices in software engineering productivit

Rethinking Productivity in Software Engineering

Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll Learn Review the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology. ; Collects the wisdom of software engineering thought leaders in a form digestible for any developer Shares hard-won best practices and pitfalls to avoid An up to date look at current practices in software engineering productivit

Medidas de productividad en los proyectos de desarrollo de software: una aproximación por puestos de trabajo

La productividad es una medida, principalmente económica, creada a finales del siglo XVIII. Desde entonces, numerosas modificaciones se han realizado sobre la definición inicial y se han incorporando a diversas áreas de conocimiento. Dentro de la Ingeniería del Software (IS), la productividad comenzó a ser objeto de estudio a finales de los años 70, casi de forma paralela a la concepción de la misma y al inicio del estudio de conceptos relacionados, tales como la estimación de esfuerzo. La medición de la productividad en IS ha sido ampliamente analizada a nivel de proyecto y organización, sin embargo a nivel de puesto de trabajo no ha sido tan investigada. En estos escasos estudios, las medidas utilizadas suelen ser las mismas medidas que las empleadas en niveles superiores de medición. En concreto, las medidas empleadas suelen ser ratios entre una medida de tamaño de producto (p. ej., líneas de código o puntos función) y una medida de esfuerzo o tiempo (p. ej., horas-hombre u horas). Este tipo de medidas son muy específicas y no reflejan la realidad del trabajo desempeñado en todo el proceso de desarrollo, ya que no tienen en cuenta las características inherentes a cada puesto de trabajo. Así pues, la eficacia de estas medidas, en este nivel de medición, parece estar en entredicho y la realización de estudios que aporten nuevas medidas de productividad en IS a nivel de puesto de trabajo cobra sentido. En la presente tesis doctoral se ha analizado la situación actual de la medición de la productividad en IS a nivel de puesto de trabajo con el objetivo de crear nuevas medidas. Para conseguir este objetivo se ha realizado un estudio del estado de la cuestión utilizando una metodología clásica de revisión de referencias junto con una revisión sistemática de la literatura. Una vez analizado el estado de la cuestión se ha planteado un conjunto de hipótesis relacionadas con la construcción de nuevas medidas de productividad: Hipótesis 1. En los puestos de trabajo involucrados en la ejecución de proyectos de desarrollo de software se emplean otras entradas, además del tiempo y el esfuerzo. Hipótesis 2. Las entradas utilizadas son distintas para cada puesto de trabajo involucrado en la ejecución de proyectos de desarrollo de software. Hipótesis 3. En los puestos de trabajo involucrados en la ejecución de proyectos de desarrollo de software se producen otras salidas, además de líneas de código y funcionalidad. Hipótesis 4. Las salidas producidas son distintas para cada puesto de trabajo involucrado en la ejecución de proyectos de desarrollo de software. Hipótesis 5. Las medidas de productividad más utilizadas a nivel de puesto de trabajo en los proyectos de desarrollo de software tienen una eficacia limitada para medir la productividad real de los trabajadores. Hipótesis 6. Es posible medir de forma más eficaz la productividad de los puestos de trabajo en los proyectos de desarrollo de software con nuevas medidas que combinen varios elementos: entradas, salidas y factores. Tras el análisis del estado de la cuestión, se ha realizado una fase de investigación cualitativa mediante el empleo de entrevistas a trabajadores de IS y un posterior análisis de contenido, con el fin de obtener información suficiente para: (1) contrastar las cuatro primeras hipótesis con información cualitativa, y (2) construir el medio de recogida de información para la siguiente fase de la investigación. Con respecto al primer objetivo, ha sido posible contrastar dos hipótesis (H1 y H3). En la segunda fase, mediante una metodología cuantitativa, se han contrastado las cuatro primeras hipótesis planteadas. Para la recogida de información se ha utilizado un formulario construido a partir de los resultados de la fase cualitativa. Los resultados de esta fase indican que en los puestos de trabajo analizados (programador, analista, consultor, y jefe de proyecto): se utilizan otros recursos además del tiempo, se producen otras salidas además del código fuente y la funcionalidad entregada al cliente. Además, se han encontrado diferencias en el grado de uso de las entradas y en la producción de las salidas, por lo que el uso de una misma medida de productividad para todos los puestos bajo estudio es, en principio, ilógico. Para contrastar las dos, y últimas, hipótesis se han construido nuevas medidas de productividad, teniendo en cuenta los resultados previos. En concreto, se ha utilizado Data Envelopment Analysis (DEA) como metodología personalizable para medir la productividad; y se han realizado cuatro casos de estudio empleando dicha metodología. Los resultados tras los casos de estudio indican que mediante DEA es posible medir la productividad de los puestos de trabajo vinculados con los proyectos de desarrollo y mantenimiento de software de forma más eficaz que con las medidas más utilizadas. Además, esta metodología permite conocer los puntos de mejora para que los trabajadores menos productivos aumenten su productividad, lo que supone una gran ventaja frente a otras medidas de productividad si el objetivo de medir, como es lógico suponer, es mejorar la productividad, y no simplemente evaluarla. Así pues, se contrastan las dos últimas hipótesis y se insta, entre otras futuras líneas de investigación, a continuar con nuevos estudios que comparen el uso de DEA con otras medidas de productividad. Finalmente, se concluye que la medición de la productividad en los puestos de trabajo vinculados con los proyectos de desarrollo y mantenimiento de software continua siendo un reto. Para reducir la dificultad de éste, la presente tesis doctoral arroja luz aportando un marco de trabajo para analizar y plantear nuevas medidas de productividad, tanto en estos puestos de trabajo como en otros. ------------------------------Productivity is mainly an economic measure, created in the late eighteenth century. Since then, many changes have been made on its initial definition and have been incorporated into various areas of knowledge. Within Software Engineering (SE), productivity began to be studied in the late '70s. These efforts ran parallel to SE developments, such as effort estimation. Measuring productivity in SE has been extensively analyzed at the project and organization level; however job level has not been investigated with the same depth. In these few studies, the measures used are often the same ones than those used in higher levels of measurement. Specifically, the measures employed are usually ratios between a measure of product size (e.g., lines of code or function points) and a measure of effort or time (e.g., man-hours or hours). Such measures do not reflect the reality of the work performed throughout the development process because they do not take into account the inherent characteristics of each job. Thus, the effectiveness of these measures, in this measurement level, seems to be in question and studies that provide new measures of productivity at job level make sense. In this thesis we have analyzed the current state of productivity measurement at job level within SE with the goal of creating new measures. In order to achieve this objective a study of the state of the art has been carried out with a classical methodology along with a systematic review of the literature. After analyzing the state of the art, a number of hypotheses related to the construction of new productivity measures have been stated: Hypothesis 1. In the jobs involved in the implementation of software development projects other inputs are used in addition to time and effort. Hypothesis 2. The inputs used are different for every job involved in software development projects. Hypothesis 3. In the jobs involved in the implementation of software development projects other outputs are produced in addition to source code lines and functionality. Hypothesis 4. The outputs produced are different for every job involved in software development projects. Hypothesis 5. The most used productivity measures at job level in software development projects have limited effectiveness for measuring real productivity of workers. Hypothesis 6. It is possible to measure more effectively the productivity of jobs in software development projects with new measures that combine several elements: inputs, outputs and factors. After analyzing the state of the art, a qualitative phase has been performed using interviews with SE workers and a subsequent content analysis of them in order to obtain pertinent information: (1) to test the first four hypotheses with qualitative information, and (2) to build the information gathering instrument for the next phase of research. Regarding the first objective, it has been possible to test two hypotheses (H1 and H3). In the second phase, using a quantitative method, the first four hypotheses have been contrasted and accepted. For the information gathering a form constructed from the results of the qualitative phase has been used. The results of this phase indicate that the analyzed job positions (programmer, analyst, consultant, and project manager): use other resources in addition to time, and deliver other outputs in addition to source code and functionality delivered to the client. Also some differences in the degree of use of inputs and production of outputs have been found. Therefore, the use of the same measure of productivity for all positions under study is, in principle, illogical. To contrast the last two hypotheses new productivity measures have been built taking into account the previous results. Specifically, a customizable methodology for measuring productivity such as Data Envelopment Analysis (DEA) was used in four case studies. The results after these studies indicate that using DEA is a mean to measure the productivity of job level for job positions related to the development and maintenance of software projects in a more effectively way. Furthermore, this methodology allows knowing the points for improvement for the least productive workers in order to increase their productivity. This knowledge is a great advantage over other productivity measures if the goal of measuring, as is logical to assume, is to improve productivity, not simply to evaluate it. So the last two hypotheses has been supported. Consequently we call, among other future research, to continue with further studies comparing the use of DEA with other measures of productivity. Finally, it is concluded that the measurement of productivity in job positions related with software development and maintenance projects remains a challenge. To reduce this difficulty, this thesis sheds some light on the topic by providing a framework to analyze and propose new measures of productivity for SE job roles.Presidente: María Belén Ruiz Mezcua; Vocal: Rafael Valencia García; Secretario: Edmundo Tovar Car

A influência de fatores na produtividade do desenvolvimento de software de acordo com um modelo de estruturas teóricas

This work presents an evidence-based model describing the effects of a set of factors on software development productivity, obtained through an evidence synthesis method in Software Engineering. Thus, the relationships among this set and the software development productivity (observed phenomena) are described as results of combining theoretical structures capable of expressing and dealing with differences between different effects and uncertainties varying according to the types of studies found in the literature. Besides, to evaluate the model found, its findings are confronted with a survey capturing the practitioners’ perception (managers and leaders of software projects in Brazilian organizations). The degree of agreement between research (the model) and practice (the practitioners’ perception) shows that scientific knowledge does not differ considerably from the reality experienced by software projects when both of them refer to the influence of factors on software development productivity. The impression that research and practice on the theme go through different paths persists. According to this work, the reasons for this impression are more related to the use of non-standardized and, perhaps, inappropriate measures used to perceive and monitor the influence of factors as well as to measure the software development productivityEste trabalho apresenta um modelo baseado em evidências que descreve efeitos de alguns fatores na produtividade do desenvolvimento de software, obtidos através de um método de síntese de evidências em Engenharia de Software. Deste modo, as relações entre um conjunto de fatores e a produtividade do desenvolvimento de software (fenômenos observados) são descritas como resultados da combinação de estruturas teóricas capazes de expressar e tratar diferenças entre efeitos e incertezas variadas de acordo com os tipos de estudos primários encontrados na literatura. Além disso, para avaliar o modelo encontrado, seus achados são confrontados com uma pesquisa de opinião realizada para capturar a percepção de profissionais da prática (gestores e líderes de projetos de software em organizações brasileiras). O grau de concordância entre a pesquisa (o modelo) e a prática (a percepção dos profissionais) demonstra que, aparentemente, o conhecimento científico não diverge consideravelmente da realidade vivenciada pelos projetos de software no Brasil, quando ambos se referem à influência de fatores na produtividade do desenvolvimento de software. Persiste a impressão, entretanto, de que a pesquisa e a prática no tema percorrem caminhos distintos. De acordo com este trabalho, a impressão do distanciamento parece estar relacionadas à questão do uso de medidas não-padronizadas e, talvez, inapropriadas para mensurar os fatores e a produtividade do desenvolvimento de softwar