841 resultados para software project management
Resumo:
Route through project plan no resume
Resumo:
The academic activities carried out at the School of Chemistry make indispensable to develop actions oriented toward the consolidation of a reagent and residue management system, especially in the teaching laboratories. The project “Management of reagents and residues in the teaching laboratories of the School of Chemistry” works under the Green Chemistry values which designs products and chemical processes that reduce or eliminate the use and production of dangerous substances, to benefit the environment. With a preventive vision, a change from the laboratory practices is looked to select those with less environmental impact. Additionally, residue quantification is made and its management protocols are developed for each practice. The project has several stages: diagnose, action implementation, student, teacher and administration personnel training and evaluation during the process and at the end of it. The article describes methodological aspects of the project operation emphasizing on reagent and residue quantification through flow diagrams.
Resumo:
Abstract – Background – The software effort estimation research area aims to improve the accuracy of this estimation in software projects and activities. Aims – This study describes the development and usage of a web application tocollect data generated from the Planning Poker estimation process and the analysis of the collected data to investigate the impact of revising previous estimates when conducting similar estimates in a Planning Poker context. Method – Software activities were estimated by Universidade Tecnológica Federal do Paraná (UTFPR) computer students, using Planning Poker, with and without revising previous similar activities, storing data regarding the decision-making process. And the collected data was used to investigate the impact that revising similar executed activities have in the software effort estimates' accuracy.Obtained Results – The UTFPR computer students were divided into 14 groups. Eight of them showed accuracy increase in more than half of their estimates. Three of them had almost the same accuracy in more than half of their estimates. And only three of them had loss of accuracy in more than half of their estimates. Conclusion – Reviewing the similar executed software activities, when using Planning Poker, led to more accurate software estimates in most cases, and, because of that, can improve the software development process.
Resumo:
The research investigates the feasibility of using web-based project management systems for dredging. To achieve this objective the research assessed both the positive and negative aspects of using web-based technology for the management of dredging projects. Information gained from literature review and prior investigations of dredging projects revealed that project performance, social, political, technical, and business aspects of the organization were important factors in deciding to use web-based systems for the management of dredging projects. These factors were used to develop the research assumptions. An exploratory case study methodology was used to gather the empirical evidence and perform the analysis. An operational prototype of the system was developed to help evaluate developmental and functional requirements, as well as the influence on performance, and on the organization. The evidence gathered from three case study projects, and from a survey of 31 experts, were used to validate the assumptions. Baselines, representing the assumptions, were created as a reference to assess the responses and qualitative measures. The deviation of the responses was used to evaluate for the analysis. Finally, the conclusions were assessed by validating the assumptions with the evidence, derived from the analysis. The research findings are as follows: 1. The system would help improve project performance. 2. Resistance to implementation may be experienced if the system is implemented. Therefore, resistance to implementation needs to be investigated further and more R&D work is needed in order to advance to the final design and implementation. 3. System may be divided into standalone modules in order to simplify the system and facilitate incremental changes. 4. The QA/QC conceptual approach used by this research needs to be redefined during future R&D to satisfy both owners and contractors. Yin (2009) Case Study Research Design and Methods was used to develop the research approach, design, data collection, and analysis. Markus (1983) Resistance Theory was used during the assumptions definition to predict potential problems to the implementation of web-based project management systems for the dredging industry. Keen (1981) incremental changes and facilitative approach tactics were used as basis to classify solutions, and how to overcome resistance to implementation of the web-based project management system. Davis (1989) Technology Acceptance Model (TAM) was used to assess the solutions needed to overcome the resistances to the implementation of web-base management systems for dredging projects.
Resumo:
Requirements specification has long been recognized as critical activity in software development processes because of its impact on project risks when poorly performed. A large amount of studies addresses theoretical aspects, propositions of techniques, and recommended practices for Requirements Engineering (RE). To be successful, RE have to ensure that the specified requirements are complete and correct what means that all intents of the stakeholders in a given business context are covered by the requirements and that no unnecessary requirement was introduced. However, the accurate capture the business intents of the stakeholders remains a challenge and it is a major factor of software project failures. This master’s dissertation presents a novel method referred to as “Problem-Based SRS” aiming at improving the quality of the Software Requirements Specification (SRS) in the sense that the stated requirements provide suitable answers to real customer ́s businesses issues. In this approach, the knowledge about the software requirements is constructed from the knowledge about the customer ́s problems. Problem-Based SRS consists in an organization of activities and outcome objects through a process that contains five main steps. It aims at supporting the software requirements engineering team to systematically analyze the business context and specify the software requirements, taking also into account a first glance and vision of the software. The quality aspects of the specifications are evaluated using traceability techniques and axiomatic design principles. The cases studies conducted and presented in this document point out that the proposed method can contribute significantly to improve the software requirements specification.
Resumo:
The aim of this text is to discuss how it is possible to manage the art creating process in a film project, where the circumstances are often turbulent. In normative project management literature one proceeds from the idea that a project is realised in a stable world from a clear goal. In a film project there is often a need to change your plans, to improvise both in front of the camera as well as behind the camera. In the theoretical cinematic literature the responsibility for the final film text is more and more being viewed as a product of not only the director, but of the whole team’s work. Consequently, the narrative of leadership/management in a film team can be viewed from a relational perspective where the director and those s/he interacts with, are responsible for the action, relations and social situations they construe jointly in the process of filmmaking. The organization of a film project is a temporary one. The members of a team are seldom the same from one production to another, as well as the creative process always being unique. According to process thinking, organizing can be seen as the ongoing creative activity where we structure and stabilize the chaotic, moving reality. As concerns a film project, the process of becoming of the filmic expression; careful plans, on the one hand, and improvisation and flexibility in action, on the other hand, are a precondition for its realisation. The director when setting a linguistic formulation to what is to be done, can be considered as a practical author.
Resumo:
Con el objetivo de mejorar el rendimiento de los equipos de desarrollo de software se han definido muchas metodologías de desarrollo, entre las que se encuentran las prescriptivas y las ágiles. Pese a esto, los equipos no suelen emplear ninguna por no encontrarlas ajustadas a su contexto particular, y se van directamente a la tarea de programar. En este artículo se propone una metodología de desarrollo de software ligera y adaptada a un contexto preciso y bien definido, que alinea Microsoft Solutions Framework for Agile Software Development (MSF4ASD) con los lineamientos de gestión de proyectos presentados en la Guía del PMBOK. Además, se brindan elementos para la implementación de una plataforma Microsoft de desarrollo de software en equipo para soportarla.
Resumo:
The universities rely on the Information Technology (IT) projects to support and enhance their core strategic objectives of teaching, research, and administration. The researcher’s literature review found that the level of IT funding and resources in the universities is not adequate to meet the IT demands. The universities received more IT project requests than they could execute. As such, universities must selectively fund the IT projects. The objectives of the IT projects in the universities vary. An IT project which benefits the teaching functions may not benefit the administrative functions. As such, the selection of an IT project is challenging in the universities. To aid with the IT decision making, many universities in the United States of America (USA) have formed the IT Governance (ITG) processes. ITG is an IT decision making and accountability framework whose purpose is to align the IT efforts in an organization with its strategic objectives, realize the value of the IT investments, meet the expected performance criteria, and manage the risks and the resources (Weil & Ross, 2004). ITG in the universities is relatively new, and it is not well known how the ITG processes are aiding the nonprofit universities in selecting the right IT projects, and managing the performance of these IT projects. This research adds to the body of knowledge regarding the IT project selection under the governance structure, the maturity of the IT projects, and the IT project performance in the nonprofit universities. The case study research methodology was chosen for this exploratory research. The convenience sampling was done to choose the cases from two large, research universities with decentralized colleges, and two small, centralized universities. The data were collected on nine IT projects from these four universities using the interviews and the university documents. The multi-case analysis was complemented by the Qualitative Comparative Analysis (QCA) to systematically analyze how the IT conditions lead to an outcome. This research found that the IT projects were selected in the centralized universities in a more informed manner. ITG was more authoritative in the small centralized universities; the ITG committees were formed by including the key decision makers, the decision-making roles, and responsibilities were better defined, and the frequency of ITG communication was higher. In the centralized universities, the business units and colleges brought the IT requests to ITG committees; which in turn prioritized the IT requests and allocated the funds and the resources to the IT projects. ITG committee members in the centralized universities had a higher awareness of the university-wide IT needs, and the IT projects tended to align with the strategic objectives. On the other hand, the decentralized colleges and business units in the large universities were influential and often bypassed the ITG processes. The decentralized units often chose the “pet” IT projects, and executed them within a silo, without bringing them to the attention of the ITG committees. While these IT projects met the departmental objectives, they did not always align with the university’s strategic objectives. This research found that the IT project maturity in the university could be increased by following the project management methodologies. The IT project management maturity was found higher in the IT projects executed by the centralized university, where a full-time project manager was assigned to manage the project, and the project manager had a higher expertise in the project management. The IT project executed under the guidance of the Project Management Office (PMO) has exhibited a higher project management maturity, as the PMO set the standards and controls for the project. The IT projects managed by the decentralized colleges by a part-time project manager with lower project management expertise have exhibited a lower project management maturity. The IT projects in the decentralized colleges were often managed by the business, or technical leads, who often lacked the project management expertise. This research found that higher the IT project management maturity, the better is the project performance. The IT projects with a higher maturity had a lower project delay, lower number of missed requirements, and lower number of IT system errors. This research found that the quality of IT decision in the university could be improved by centralizing the IT decision-making processes. The IT project management maturity could be improved by following the project management methodologies. The stakeholder management and communication were found critical for the success of the IT projects in the university. It is hoped that the findings from this research would help the university leaders make the strategic IT decisions, and the university’s IT project managers make the IT project decisions.
Resumo:
Doutoramento em Gestão
Resumo:
The increasing emphasis on aid effectiveness, accountability and impact measurement in international development and humanitarian work has generated a requirement for high quality internal systems for the management of programmes. To help to address this requirement, Trócaire adopted Results Based Management in the 20 countries in which it works. This paper provides an overview of Trócaire’s RBM journey, including the process of embedding the new approach in the organisation, lessons learnt from this process, the subsequent benefits that are emerging at field programme level and the challenges going forward.
Resumo:
Short time-to-market is a key success factor in the todays’ dynamic business environment and many companies are trying to improve their product development processes. A challenge is to develop products according to the time plan and at the same time keeping the cost low and the quality high. This study focuses on the project management within the product development process in an automotive industry. The background of this study started as a request from the research and development department at the automotive company, which led to the following questions; 1) what are the most crucial factors for project success? 2) How can these factors contribute to a more successful outcome? 3) How can project management decrease product development lead time by sharing knowledge? The research approach is a case study and the data collection consist of interviews and questioners at two companies connected to project management in product development projects. Spider charts are created from the collected data containing eleven dimensions to show similarities and differences between the project managers working within the research and development department as well as between the two companies. The main conclusions are that there is a need to allow a certain level of flexibility when managing projects, in order to more easily handle late changes. Being involved in a project from the concept phase could facilitate the product development activities later on, due to a deeper understanding regarding previous decisions. Further, knowledge sharing methods, such as databases, has to be designed to be suitable for a specific organization and user friendly which enables the users to more easily search for specific types of knowledge. Lastly, a low level on the detailed focus is shown to be another success factor, however, in some cases there is still a need of this detailed focus to solve specific problems but the details may never become a higher focus than the holistic view.
Resumo:
History has shown that projects move in and out of poor status through the life of the project. Predicting the success or failure of a project to complete on time because of its recent history on the contract status report could provide our project managers another tool for monitoring contract progress. In many instances, poor contract progress results in the loss of contract time and late completion of projects. This research evaluates the combinations of work type, point in time physical work begins, recent poor status, and contract bid amount as indicators of late project completion.
Resumo:
Even though today’s corporations recognize that they need to understand modern project management techniques (Schwalbe, 2002, p2), many researchers continue to provide evidence of poor IT project success. With Kotnour, (2000) finding that project performance is positively associated with project knowledge, a better understanding of how to effectively manage knowledge in IT projects should have considerable practical significance for increasing the chances of project success. Using a combined qualitative/quantitative method of data collection in multiple case studies spanning four continents, and comprising a variety of organizational types, the focus of this current research centered on the question of why individuals working within IT project teams might be motivated towards, or inhibited from, sharing their knowledge and experience in their activities, procedures, and processes. The research concluded with the development of a new theoretical model of knowledge sharing behavior, ‘The Alignment Model of Motivational Focus’. This model suggests that an individual’s propensity to share knowledge and experience is a function of perceived personal benefits and costs associated with the activity, balanced against the individual’s alignment to a group of ‘institutional’ factors. These factors are identified as alignments to the project team, to the organization, and dependent on the circumstances, to either the professional discipline or community of practice, to which the individual belongs.