911 resultados para agile project management method
Resumo:
Il presente elaborato di tesi riguarda uno studio che è stato portato avanti durante il tirocinio curriculare svolto nell’ufficio Engineering di Marchesini Group S.p.A., azienda leader nella produzione di macchine automatiche per il packaging di prodotti farmaceutici e cosmetici. Dopo aver riscontrato alcune criticità nelle modalità con le quali vengono attualmente pianificate e gestite le risorse appartenenti ai team produttivi e con le quali vengono valutati i carichi di lavoro, si sono elaborati dei modelli e degli strumenti che permettono di migliorare ed ottimizzare l’assegnazione delle risorse ai gruppi e di visualizzare in tempo reale la distribuzione dell’impegno di lavoro dei reparti in relazione alla disponibilità in produzione. Le proposte supportano il trend dell’attuale contesto produttivo di garantire un elevato livello di servizio al cliente rispettandone le richieste e i tempi stabiliti. Difatti, un’assegnazione corretta delle risorse in produzione consente di ridurre i ritardi e le inefficienze e, di conseguenza, di migliorare i lead time. In aggiunta, una correlazione chiara e strutturata fra le risorse e gli obiettivi raggiungibili permette di conseguire con maggiore sicurezza i risultati economici stabiliti, evitando di perdere parte del valore potenzialmente collaudabile.
Resumo:
An ecological control method, using environmental management operations, based on biological and behavioral characteristics of Triatoma dimidiata (Latreille, 1811), was implemented as a pilot project in an area of Costa Rica where the bug is prevalent. The sample was represented by 20 houses with peridomestic colonies (two also had indoor infestation), divided in two equivalent groups of 10 each. In one group we intervened the houses, i.e. all objects or materials that were serving as artificial ecotopes for the bugs were removed, and the second group was used as control houses. After a year of periodic follow up, it became evident that in those houses with a modified environment the number of insects had decreased notoriously even after the first visits and this was more evident after a period of 12.5 to 13.5 months in which no insects were detected in eight of the houses. It also became clear that in this group of houses, recolonization by wild bugs from the surrounding areas, became more difficult, probably due to the absence of protection from bug predators. In the control houses, with the exception of three in which the inhabitants decided to intervene on their own, and another house with a peculiar situation, the insect populations remained the same or even showed a tendency to increase, as confirmed at the end of the experiment. We believe that the method is feasible, low costing and non contaminating. It could be used successfully in other places where T. dimidiata is common and also in countries where other species colonize peridomestic areas of homes. Environmental management of this kind should seek the participation of the members of the communities, in order to make it a more permanent control measure.
Resumo:
Requirements-relatedissues have been found the third most important risk factor in software projects and as the biggest reason for software project failures. This is not a surprise since; requirements engineering (RE) practices have been reported deficient inmore than 75% of all; enterprises. A problem analysis on small and low maturitysoftware organizations revealed two; central reasons for not starting process improvement efforts: lack of resources and uncertainty; about process improvementeffort paybacks.; In the constructive part of the study a basic RE method, BaRE, was developed to provide an; easy to adopt way to introduce basic systematic RE practices in small and low maturity; organizations. Based on diffusion of innovations literature, thirteen desirable characteristics; were identified for the solution and the method was implemented in five key components:; requirements document template, requirements development practices, requirements; management practices, tool support for requirements management, and training.; The empirical evaluation of the BaRE method was conducted in three industrial case studies. In; this evaluation, two companies established a completely new RE infrastructure following the; suggested practices while the third company conducted continued requirements document; template development based on the provided template and used it extensively in practice. The; real benefits of the adoption of the method were visible in the companies in four to six months; from the start of the evaluation project, and the two small companies in the project completed; their improvement efforts with an input equal to about one person month. The collected dataon; the case studies indicates that the companies implemented new practices with little adaptations; and little effort. Thus it can be concluded that the constructed BaRE method is indeed easy to; adopt and it can help introduce basic systematic RE practices in small organizations.
Resumo:
A software development process is a predetermined sequence of steps to create a piece of software. A software development process is used, so that an implementing organization could gain significant benefits. The benefits for software development companies, that can be attributed to software process improvement efforts, are improved predictability in the development effort and improved quality software products. The implementation, maintenance, and management of a software process as well as the software process improvement efforts are expensive. Especially the implementation phase is expensive with a best case scenario of a slow return on investment. Software processes are rare in very small software development companies because of the cost of implementation and an improbable return on investment. This study presents a new method to enable benefits that are usually related to software process improvement to small companies with a low cost. The study presents reasons for the development of the method, a description of the method, and an implementation process for the method, as well as a theoretical case study of a method implementation. The study's focus is on describing the method. The theoretical use case is used to illustrate the theory of the method and the implementation process of the method. The study ends with a few conclusions on the method and on the method's implementation process. The main conclusion is that the method requires further study as well as implementation experiments to asses the value of the method.
Resumo:
This Master´s thesis illustrates how growing a business ties up the company´s working capital and what the cost of committed capital. In order to manage a company´s working capital in rapid business growth phase, the thesis suggests that by monitoring and managing the operating and cash conversion cycles of customers´ projects, a company can find ways to secure the required amount of capital. The research method of this thesis was based on literature reviews and case study research. The theoretical review presents the concepts of working capital and provides the background for understanding how to improve working capital management. The company in subject is a global small and medium-sized enterprise that manufactures pumps and valves for demanding process conditions. The company is expanding, which creates lots of challenges. This thesis concentrates to the company´s working capital management and its efficiency through the supply chain and value chain perspective. The main elements of working capital management are inventory management, accounts receivable management and accounts payable management. Prepayments also play a significant role, particularly in project-based businesses. Developing companies´ working capital management requires knowledge from different kind of key operations´ in the company, like purchasing, production, sales, logistics and financing. The perspective to develop and describe working capital management is an operational. After literature reviews the thesis present pilot projects that formed the basis of a model to monitor working capital in the case company. Based on analysis and pilot projects, the thesis introduces a rough model for monitoring capital commitments in short time period. With the model the company can more efficiently monitor and manage their customer projects.
Resumo:
Liiketoiminnan organisoiminen projekteiksi on erittäin yleistä nykyisin. Suuri osa projekteista erityisesti IT-alalla epäonnistuu kuitenkin saavuttamaan tavoitteensa. Projektin menestys on tyypillisesti mitattu budjetin, aikataulun, laadun ja sidosryhmien tyytyväisyyden perusteella. Tämän Pro Gradu -tutkielman tarkoituksena on etsiä tyypillisimpiä syitä projektien epäonnistumiseen ja löytää projektien seurannan ja mittaamisen avulla keinoja näiden epäonnistumisten ehkäisemiseen. Tutkimusmenetelmänä on laadullinen tapaustutkimus. Empiirinen aineisto on kerätty haastattelujen, eri materiaalien analysoinnin ja havainnoinnin avulla. Teoriaosuus tarjoaa kattavan yhteenvedon projektiliiketoiminnan ja yksittäisten projektien johtamiseen sekä projektien seurantaan ja mittaamiseen aikaisemman kirjallisuuden perusteella. Empiirisessä osiossa suoritetaan analyysi Case -yrityksen projektien seurantaan ja valittuihin projekteihin. Analyysien, haastattelujen ja havainnoinnin pohjalta tehdään johtopäätökset tyypillisimmistä, ongelmia projekteissa aiheuttavista tekijöistä sekä näiden esiintymisestä projektin elinkaaren eri vaiheissa. Mahdolliset ongelmia ehkäisevät keinot esitetään myös. Ehdotuksia kehityskohteiksi esitetään lopuksi teorian ja empirian pohjalta.
Resumo:
This thesis was carried out as a case study of a company YIT in order to clarify the sev-erest risks for the company and to build a method for project portfolio evaluation. The target organization creates new living environment by constructing residential buildings, business premises, infrastructure and entire areas worth for EUR 1.9 billion in the year 2013. Company has noted project portfolio management needs more information about the structure of project portfolio and possible influences of market shock situation. With interviews have been evaluated risks with biggest influence and most appropriate metrics to examine. The major risks for the company were evaluated by interviewing the executive staff. At the same time, the most appropriate risk metrics were considered. At the moment sales risk was estimated to have biggest impact on company‟s business. Therefore project port-folio evaluation model was created and three different scenarios for company‟s future were created in order to identify the scale of possible market shock situation. The created model is tested with public and descriptive figures of YIT in a one-year-long market shock and the impact on different metrics was evaluated. Study was conducted using con-structive research methodology. Results indicate that company has notable sales risk in certain sections of business portfolio.
Resumo:
A perennial issue for land use policy is the evaluation of landscape biodiversity and the associated cost effectiveness of any biodiversity conservation policy actions. Based on the CUA methodology as applied to species conservation, this paper develops a methodology for evaluating the impact on habitats of alternative landscape management scenarios. The method incorporates three dimensions of habitats, quantity change, quality change and relative scarcity, and is illustrated in relation to the alternative landscape management scenarios for the Scottish Highlands (Cairngorms) study area of the BioScene project. The results demonstrate the value of the method for evaluating biodiversity conservation policies through their impact on habitats.
Resumo:
Organisations typically define and execute their selected strategy by developing and managing a portfolio of projects. The governance of this portfolio has proved to be a major challenge, particularly for large organisations. Executives and managers face even greater pressures when the nature of the strategic landscape is uncertain. This paper explores approaches for dealing with different levels of certainty in business IT projects and provides a contingent governance framework. Historically business IT projects have relied on a structured sequential approach, also referred to as a waterfall method. There is a distinction between the development stages of a solution and the management stages of a project that delivers the solution although these are often integrated in a business IT systems project. Prior research has demonstrated that the level of certainty varies between development projects. There can be uncertainty on what needs to be developed and also on how this solution should be developed. The move to agile development and management reflects a greater level of uncertainty often on both dimensions and this has led the adoption of more iterative approaches. What has been less well researched is the impact of uncertainty on the governance of the change portfolio and the corresponding implications for business executives. This paper poses this research question and proposes a govemance framework to address these aspects. The governance framework has been reviewed in the context of a major anonymous organisation, FinOrg. Findings are reported in this paper with a focus on the need to apply different approaches. In particular, the governance of uncertain business change is contrasted with the management approach for defined IT projects. Practical outputs from the paper include a consideration of some innovative approaches that can be used by executives. It also investigates the role of the business change portfolio group in evaluating and executing the appropriate level of governance. These results lead to recommendations for executives and also proposed further research.
Resumo:
Background: Pharmaceutical care services became recognized in New Zealand in the mid-1990s, albeit with limited evidence of the acceptability and effectiveness of the model. An asthma-specific pharmaceutical care service was trialled in southern New Zealand, based on a 'problem-action-outcome' method, with pharmacists adopting a patient-centred, outcome-focused approach with multidisciplinary consultation. Objective: To report on the implementation and outcomes of a specialist asthma service offered by community pharmacists. Design: Pharmacists in five pharmacies, servicing predominantly rural, established clientele, received training in the asthma service and research documentation. Ten patients per pharmacy were recruited in each year (years 1 and 2) of the study. The patients were entered into the study in cohorts of five per pharmacy twice yearly, with year 2 mirroring year 1. The phase-in design minimized the impact on the pharmacists. The patients acted as their own controls. All patients received individualized care and had approximately monthly consultations with the pharmacist, with clinical and quality of life (QoL) monitoring. Results: A total of 100 patients were recruited. On average, 4.3 medication-related problems were identified per patient; two-thirds of them were compliance-related. The most common interventions were revision of patients' asthma action plans, referral and medication counselling. Clinical outcomes included reduced bronchodilator use and improved symptom control in around two-thirds of patients. Asthma-specific QoL changes were more positive and correlated well with clinical indicators. Conclusion: Further research is warranted to integrate this service into daily practice. Clinical outcomes were generally positive and supported by QoL indicators. Characteristics of New Zealand practice and this sample of pharmacies may limit the generalizability of these findings.
Resumo:
In the last few years Agile methodologies appeared as a reaction to traditional ways of developing software and acknowledge the need for an alternative to documentation driven, heavyweight software development processes. This paper shortly presents a combination between Rational Uni ed Process and an agile approach for software development of e-business applications. The resulting approach is described stressing on the strong aspects of both combined methodologies. The article provides a case study of the proposed methodology which was developed and executed in a successful e-project in the area of the embedded systems.
Resumo:
Stakeholder engagement is important for successful management of natural resources, both to make effective decisions and to obtain support. However, in the context of coastal management, questions remain unanswered on how to effectively link decisions made at the catchment level with objectives for marine biodiversity and fisheries productivity. Moreover, there is much uncertainty on how to best elicit community input in a rigorous manner that supports management decisions. A decision support process is described that uses the adaptive management loop as its basis to elicit management objectives, priorities and management options using two case studies in the Great Barrier Reef, Australia. The approach described is then generalised for international interest. A hierarchical engagement model of local stakeholders, regional and senior managers is used. The result is a semi-quantitative generic elicitation framework that ultimately provides a prioritised list of management options in the context of clearly articulated management objectives that has widespread application for coastal communities worldwide. The case studies show that demand for local input and regional management is high, but local influences affect the relative success of both engagement processes and uptake by managers. Differences between case study outcomes highlight the importance of discussing objectives prior to suggesting management actions, and avoiding or minimising conflicts at the early stages of the process. Strong contributors to success are a) the provision of local information to the community group, and b) the early inclusion of senior managers and influencers in the group to ensure the intellectual and time investment is not compromised at the final stages of the process. The project has uncovered a conundrum in the significant gap between the way managers perceive their management actions and outcomes, and community's perception of the effectiveness (and wisdom) of these same management actions.
Resumo:
The main purpose of this paper is to propose and test a model to assess the degree of conditions favorability in the adoption of agile methods to develop software where traditional methods predominate. In order to achieve this aim, a survey was applied on software developers of a Brazilian public retail bank. Two different statistical techniques were used in order to assess the quantitative data from the closed questions in the survey. The first, exploratory factorial analysis validated the structure of perspectives related to the agile model of the proposed assessment. The second, frequency distribution analysis to categorize the answers. Qualitative data from the survey opened question were analyzed with the technique of qualitative thematic content analysis. As a result, the paper proposes a model to assess the degree of favorability conditions in the adoption of Agile practices within the context of the proposed study.
Resumo:
Many authors point out that the front-end of new product development (NPD) is a critical success factor in the NPD process and that numerous companies face difficulties in carrying it out appropriately. Therefore, it is important to develop new theories and proposals that support the effective implementation of this earliest phase of NPD. This paper presents a new method to support the development of front-end activities based on integrating technology roadmapping (TRM) and project portfolio management (PPM). This new method, called the ITP Method, was implemented at a small Brazilian high-tech company in the nanotechnology industry to explore the integration proposal. The case study demonstrated that the ITP Method provides a systematic procedure for the fuzzy front-end and integrates innovation perspectives into a single roadmap, which allows for a better alignment of business efforts and communication of product innovation goals. Furthermore, the results indicated that the method may also improve quality, functional integration and strategy alignment. (C) 2010 Elsevier Inc. All rights reserved.