Ganhos de produtividade e de sucesso de metodologias ágeis Vs metodologias em cascata no desenvolvimento de projectos de software
Miniatura indisponível
Data
2012
Autores
Título da revista
ISSN da revista
Título do Volume
Editora
Edições Universitárias Lusófonas
Resumo
Hoje em dia muitas empresas procuram cada vez mais inovar os seus sistemas informáticos. É hoje uma realidade que as novas tecnologias, os novos sistemas devem disponibilizar a informação correcta, no formato certo, à pessoa certa e em tempo exacto. “Ontem” tínhamos sistemas inflexíveis, hoje, têm que ser transversais, partilhados e em rede. Inerentes a esta inovação, as Empresas também pretendem que os seus sistemas sejam práticos, funcionais e rentáveis. Assim, tendo como base estas premissas, as mesmas procuram no mercado “parceiros” que possuam estas características e que lhes possam garantir/oferecer o que necessitam para desenvolverem as suas áreas de negócios, de uma forma sustentada, acrescentando valor aos seus próprios Clientes. Neste contexto, as Empresas prestadoras deste tipo de serviço para se poderem diferenciarem de uma forma positiva no mercado, quer nacional quer estrangeiro, devem adoptar sistemas que possam ir ao encontro das necessidades dos seus actuais Clientes e dos seus Clientes futuros. Várias empresas já tiveram um histórico de problemas relativos a elevados investimentos em que estes não conseguiram atingir os objectivos a que se propuseram atingir, visto que, muitas vezes não efectuam uma escolha adequada dos métodos, do âmbito e dos critérios que necessitam para desenvolverem esses mesmos projectos, originando perda de qualidade e diminuição da sua produtividade. Como reflexo destas escolhas, não conseguem alcançar os objectivos de negócio previamente definidos e propostos. Neste âmbito, é fundamental perceber a importância da utilização de uma metodologia, a qual se pode definir como: um conjunto de técnicas, procedimentos, ferramentas e documentação que sustentam e auxiliam os gestores/responsáveis no desenvolvimento e implementação de um sistema de informação. Dentro de uma metodologia, existe ainda várias fases que orientam os gestores/responsáveis do projecto para a correcta definição e escolha de técnicas apropriadas de acordo com as etapas que ocorrem durante o desenvolvimento e implementação de um sistema de informação. O que muitos desconhecem, é que muitas vezes o sucesso de um projecto de software depende de vários factores, tais como o planeamento, a definição dos objectivos a atingir e principalmente na escolha da metodologia mais adequada e compatível com o projecto em curso. Hoje em dia muitas empresas adoptaram a fundo as metodologias ágeis como sendo as mais eficazes e acessíveis à mudança proporcionando melhorias em diversos aspectos durante o processo de desenvolvimento de software, tais como: o tempo de entrega, qualidade do produto final e a redução de custos operacionais. Por outro lado temos a modelo em cascata/tradicional que foi e é a metodologia mais conhecida e a mais antiga. Para desenvolver um projecto nesta metodologia é preciso seguir cada etapa sequencialmente, ela implica que, um grande esforço seja feito em duas das fazes consideradas cruciais no desenvolvimento do projecto: levantamento de requisitos/necessidades e o design. O presente trabalho tem como objectivo principal o estudo dos ganhos de produtividade e de sucesso de metodologias ágeis vs. metodologias em cascata no desenvolvimento de projectos de software.
Nowadays many companies are increasingly looking to innovate their systems. It is now a reality that new technologies, new systems must provide the correct information in the right format, to the right person and exact time. "Yesterday" had inflexible systems today have to be cross-sharing and networking. Inherent in this innovation, the companies also claim that their systems are practical, functional and profitable. Thus, based on these premises, they seek to market "partners" that possess these characteristics and that they can ensure / provide what they need to develop their business area, in a sustained manner, adding value to their own customers. In this context, the companies providing such service to be able to differentiate in a positive way in the market, both domestic and foreign, should adopt systems that can meet the current needs of its clients and its future customers. Several companies have already had a history of problems relating to high investments in that they failed to achieve the objectives they set out to achieve, since they often do not make a proper choice of methods, scope and the criteria they need to develop these same projects, resulting in quality loss and decreased productivity. As a consequence of these choices, fail to achieve business objectives previously defined and proposed. In this context, it is essential to realize the importance of using a methodology which can be defined as: a set of techniques, procedures, tools and documentation that support and assist managers / guardians in the development and implementation of an information system. Within a method, there are still several steps that guide managers / project leaders for the correct definition and choice of appropriate techniques according to the steps that occur during the development and implementation of an information system. What many do not know, is that often the success of a software project depends on several factors, such as planning, defining the objectives to be achieved and especially in choosing the most appropriate methodology and compatible with the ongoing project. Nowadays many companies have adopted agile methodologies in depth as the most effective and accessible to change by providing improved in several respects during the process of software development, such as delivery time, product quality and reduce operating costs. On the other hand we have the waterfall model / traditional approach was and is the oldest and best known. To develop a project of this methodology is necessary to follow each step sequentially, it implies that a major effort be made in two of doing considered crucial in the development of the project: requirements gathering / requirements and design. The present work has as main objective the study of the productivity gains and successful Agile vs. waterfall methodologies in developing software projects.
Nowadays many companies are increasingly looking to innovate their systems. It is now a reality that new technologies, new systems must provide the correct information in the right format, to the right person and exact time. "Yesterday" had inflexible systems today have to be cross-sharing and networking. Inherent in this innovation, the companies also claim that their systems are practical, functional and profitable. Thus, based on these premises, they seek to market "partners" that possess these characteristics and that they can ensure / provide what they need to develop their business area, in a sustained manner, adding value to their own customers. In this context, the companies providing such service to be able to differentiate in a positive way in the market, both domestic and foreign, should adopt systems that can meet the current needs of its clients and its future customers. Several companies have already had a history of problems relating to high investments in that they failed to achieve the objectives they set out to achieve, since they often do not make a proper choice of methods, scope and the criteria they need to develop these same projects, resulting in quality loss and decreased productivity. As a consequence of these choices, fail to achieve business objectives previously defined and proposed. In this context, it is essential to realize the importance of using a methodology which can be defined as: a set of techniques, procedures, tools and documentation that support and assist managers / guardians in the development and implementation of an information system. Within a method, there are still several steps that guide managers / project leaders for the correct definition and choice of appropriate techniques according to the steps that occur during the development and implementation of an information system. What many do not know, is that often the success of a software project depends on several factors, such as planning, defining the objectives to be achieved and especially in choosing the most appropriate methodology and compatible with the ongoing project. Nowadays many companies have adopted agile methodologies in depth as the most effective and accessible to change by providing improved in several respects during the process of software development, such as delivery time, product quality and reduce operating costs. On the other hand we have the waterfall model / traditional approach was and is the oldest and best known. To develop a project of this methodology is necessary to follow each step sequentially, it implies that a major effort be made in two of doing considered crucial in the development of the project: requirements gathering / requirements and design. The present work has as main objective the study of the productivity gains and successful Agile vs. waterfall methodologies in developing software projects.
Descrição
Orientação: Jose Rogado ; co-orientação: Rui Ribeiro
Palavras-chave
INFORMÁTICA, METODOLOGIAS, MESTRADO EM ENGENHARIA INFORMÁTICA E SISTEMAS DE INFORMAÇÃO, PROJETOS DE SOFTWARE, PRODUTIVIDADE, SOFTWARE PROJECTS, PRODUCTIVITY, METHODOLOGIES, COMPUTER SCIENCE
Citação
Semedo, M J M 2012, 'Ganhos de produtividade e de sucesso de metodologias ágeis Vs metodologias em cascata no desenvolvimento de projectos de software', Default journal.