Using the project management tool microsoft project for planning and controlling software development projects

1992 ◽  
Vol 16 ◽  
pp. 35-40 ◽  
Author(s):  
W Fritz
Author(s):  
Rafael Queiroz Gonçalves ◽  
Elisa de Freitas Kühlkamp ◽  
Christiane Gresse von Wangenheim

Many problems in software development projects are due to risks and could be avoided or minimized if identified and treated pro-actively. In this context, software tools to support risk management could be very helpful. However, it is difficult to find a project management tool, accessible to Small and Medium Enterprises (SMEs) that provides adequate support to risk management in conformance with best practices such as the PMBOK. Therefore, this paper has the objective to review support provided by popular project management tools with respect to risk management and to present enhancements made to the open-source tool – dotProject – in order to systematically support risk management aligned with the PMBOK. An initial evaluation identified benefits in the implementation of risk management processes in software SMEs, and, thus, contributing to their projects' success.


Author(s):  
Rafael Queiroz Gonçalves ◽  
Elisa de Freitas Kühlkamp ◽  
Christiane Gresse von Wangenheim

Many problems in software development projects are due to risks and could be avoided or minimized if identified and treated pro-actively. In this context, software tools to support risk management could be very helpful. However, it is difficult to find a project management tool, accessible to Small and Medium Enterprises (SMEs) that provides adequate support to risk management in conformance with best practices such as the PMBOK. Therefore, this paper has the objective to review support provided by popular project management tools with respect to risk management and to present enhancements made to the open-source tool – dotProject – in order to systematically support risk management aligned with the PMBOK. An initial evaluation identified benefits in the implementation of risk management processes in software SMEs, and, thus, contributing to their projects' success.


2007 ◽  
Vol 20 (1) ◽  
pp. 70-82 ◽  
Author(s):  
Tom McBride ◽  
Brian Henderson‐Sellers ◽  
Didar Zowghi

PurposeThe paper seeks to investigate whether project managers regard software development projects as design problems or production problems.Design/methodology/approachProject management literature was examined to determine what evidence there should be to indicate whether a software development project was regarded as a problem to be solved or a product to be produced. Data were then collected through structured interview of project managers currently engaged in managing software development projects. The data were analysed to determine how project managers regarded their projects and whether this matched a theoretical expectation.FindingsThe empirical data indicated that most project managers regard their projects as production problems, where it is assumed that the underlying problem is largely understood, the project encapsulated in a planned schedule of activities and there will be an emphasis on monitoring the project against the planned progress.Research limitations/implicationsOwing to the small sample size of fewer than 30 project managers, external validity is weak. More research is needed to confirm these results over a larger sample and to probe more subtle orientation to production or design projects.Practical implicationsThe research developed a simple test to indicate the degree of novelty of the application to be developed. The test indicates whether the application is novel and should be treated as a design problem, or well known and therefore should be treated as a production problem.Originality/valueThe paper draws attention to the need for project managers to evaluate the type of application to be developed and to adopt an appropriate project management approach. The paper also provides a simple test to achieve that objective.


2020 ◽  
Vol 6 (3) ◽  
pp. 27-34
Author(s):  
E.J. Robles Gómez ◽  
J.A. Flores Lara ◽  
J.C. Ontiveros Neri

El juego getKanban es una herramienta para enseñar la metodología Kanban y SCRUM de una manera divertida. Facilita la enseñanza de la gestión de proyectos de software a través de un juego de mesa, donde los jugadores aprenden a formular estrategias de gestión de proyectos y las implementan para elaborar proyectos de calidad en tiempo y forma. El presente artículo muestra los resultados de la implementación del juego en una institución educativa de nivel superior, con alumnos de Ingeniería en Sistemas Computacionales de octavo semestre. Se puede apreciar que al utilizar este juego ayuda de manera efectiva a la enseñanza de Kanban y SCRUM, para la gestión de proyectos de software. Por lo cual se recomienda poder implementar este tipo de juegos como estrategia didáctica para la enseñanza/aprendizaje de Ingeniería de Software aplicada a la Gestión de Proyectos de Desarrollo de Software. The game Kanban is a tool to teach the methodology in a fun way. It facilitates the teaching of software project management through where players learn to formulate strategies and implement them to develop quality projects on time Delivery. This article shows the results of the implementation of the game in an educational institution of higher level, with students of Computer Systems Engineering eighth semester. It can be seen that by using this game it helps in an effective way to teach Kanban for the management of software projects. Therefore, it is recommended to be able to implement this type of games as a didactic strategy for the teaching / learning of Software Engineering applied to the Management of Software Development Projects


Author(s):  
Kitti Photikitti ◽  
Kitikorn Dowpiset ◽  
Jirapun Daengdej

It has been well-known that the chance of successfully delivering a software project within an allocated time and budget is very low. Most of the researches in this area have concluded that “user's requirements” of the systems is one of the most difficult risks to deal with in this case. Interestingly, until today, regardless of amount of effort put into this area, the possibility of project failure is still very high. The issue with requirement can be significantly increased when developing an artificial intelligence (AI) system, where one would like the systems to autonomously behave. This is because we are not only dealing with user's requirements, but we must also be able to deal with “system's behavior” that, in many cases, do not even exist during software development. This chapter discusses a preliminary work on a framework for risk management for AI systems development projects. The goal of this framework is to help project management in minimizing risk that can lead AI software projects to fail due to the inability to finish the projects on time and within budget.


Sign in / Sign up

Export Citation Format

Share Document