Mostrar el registro sencillo del ítem
Elaboración de un modelo para la implementación de controles eficaces para la gestión de riesgos en proyectos de software bajo el marco de estándares internacionales en empresas fábricas de software en Bogotá
dc.contributor.advisor | Cifuentes Bernal, Andrés Mauricio | spa |
dc.contributor.author | Garzón Talero, Eduardo | |
dc.coverage.spatial | Calle 100 | spa |
dc.date.accessioned | 2019-12-13T19:16:38Z | |
dc.date.accessioned | 2019-12-26T22:58:14Z | |
dc.date.available | 2019-12-13T19:16:38Z | |
dc.date.available | 2019-12-26T22:58:14Z | |
dc.date.issued | 2019-07-26 | |
dc.identifier.uri | http://hdl.handle.net/10654/32666 | |
dc.description.abstract | La presente propuesta de investigación tiene como objetivo elaborar un modelo para la implementación de controles eficaces que permita identificar y gestionar adecuadamente los riesgos asociados en proyectos de software y verificar su funcionamiento en un caso real en donde, con la identificación de factores de riesgos genéricos de mayor incidencia en este tipo de proyectos y a través del diseño de un modelo de monitoreo de variables basado en los factores de riesgos más relevantes, se diseña el modelo para la gestión de riesgos, con su posterior validación en un proyecto real. La metodología utilizada parte de la identificación de los factores de riesgo, definición del universo y cálculo de la muestra, trabajo de campo (diagnóstico), elaboración de los modelos de variables y de control de gestión de riesgos, aplicación en campo y determinación de su impacto. Los resultados parecen indicar que la utilización del modelo aporto una adecuada planificación y seguimiento a los riesgos, en la definición de requerimientos y en el involucramiento activo de las partes interesadas. Esta investigación propone unos indicadores de control para la gestión de riesgos, que integra distintos ámbitos necesarios durante la cadena de producción de TI permitiendo su adopción e implementación de una manera ágil. | spa |
dc.description.tableofcontents | Introducción 1. DELIMITACIÓN DEL PROYECTO 1.1 Planteamiento del problema 1.2 Objetivos 1.2.1 Objetivo General 1.2.2 Objetivos Específicos 1.3 Justificación 1.4 Hipótesis 1.5 Antecedentes y Estado del arte 1.5.1 Antecedentes 1.5.2 Estado del Arte: Factores de Riesgo en Proyectos de TI 2. MARCO TEÓRICO 2.1. Gestión de Proyectos de TI 2.2. Gestión de Riesgos en Proyectos de TI 2.3. Ciclo de vida del Software 3. METODOLOGÍA 4. RESULTADO DIAGNÓSTICO 4.1. Trabajo de Campo: diagnóstico 5. DEFINICIÓN DEL MODELO 5.1. Diseño Modelo de Monitoreo de Variables 5.2. Modelo para la implementación de Controles para la Gestión de Riesgos en proyectos de TI 5.2.1 Matriz de Riesgos 5.2.2 Matriz de Entregables 5.2.3 Tablero de Control 6. APLICACIÓN DEL MODELO 6.1. Diagnóstico del Control para la Gestión de Riesgos 6.2. Aplicación del modelo en campo 6.3. Captura y análisis de los datos de salida del modelo aplicado 6.4. Determinación del impacto del modelo propuesto y verificación cumplimiento de objetivos 6.4.1 Gestión de Riesgos 6.4.2 Gestión de Entregables 6.4.3 Primeras mediciones de la Implementación del Modelo Conclusiones Trabajos Futuros ANEXO 1 ANEXO 2 Bibliografía | spa |
dc.format | spa | |
dc.format.mimetype | application/pdf | spa |
dc.language.iso | spa | spa |
dc.language.iso | spa | spa |
dc.publisher | Universidad Militar Nueva Granada | spa |
dc.rights | Derechos Reservados - Universidad Militar Nueva Granada, 2019 | spa |
dc.rights.uri | https://creativecommons.org/licenses/by-nc-nd/2.5/co/ | spa |
dc.title | Elaboración de un modelo para la implementación de controles eficaces para la gestión de riesgos en proyectos de software bajo el marco de estándares internacionales en empresas fábricas de software en Bogotá | spa |
dc.type | info:eu-repo/semantics/masterThesis | spa |
dc.rights.accessrights | info:eu-repo/semantics/openAccess | spa |
dc.subject.lemb | ADMINISTRACION DE RIESGOS | spa |
dc.subject.lemb | ELABORACION DE PROYECTOS | spa |
dc.subject.lemb | PROGRAMAS PARA COMPUTADOR | spa |
dc.publisher.department | Facultad de Ingeniería | spa |
dc.type.local | Tesis de maestría | spa |
dc.description.abstractenglish | The present proposal for research has as main objective to develop a model for the implementation of effective controls to identify and manage the risks associated in software projects and check its operation in a real case where, with the identification of generic risk factors of higher incidence in this type of projects and through the design of a model for monitoring of variables based on the most relevant risk factors, is designed the model for risk management, with its subsequent validation in a real project. The methodology used part of the identification of risk factors, and the definition of the universe and calculation of the sample, field work (diagnosis), development of the models of variables and control of risk management, field application, and determination of its impact. The results seem to indicate that the use of the model provided an adequate planning and follow-up to the risks, in the definition of requirements and the active involvement of interested parties. This research proposes monitoring indicators for risk management, which integrates various fields required during the production chain from you allowing its adoption and implementation of an agile. | eng |
dc.title.translated | Development of a model for the implementation of effective controls for risk management in software projects under the framework of international standards in companies software factories in Bogota | spa |
dc.subject.keywords | Model | spa |
dc.subject.keywords | Proyect | spa |
dc.subject.keywords | Risk | spa |
dc.subject.keywords | Software | spa |
dc.subject.keywords | KPI | spa |
dc.subject.keywords | Factory | spa |
dc.publisher.program | Maestría en Gerencia de Proyectos | spa |
dc.creator.degreename | Magíster en Gerencia de Proyectos | spa |
dc.description.degreelevel | Maestría | spa |
dc.publisher.faculty | Ingeniería - Maestría en Gerencia de Proyectos | spa |
dc.type.dcmi-type-vocabulary | Text | spa |
dc.type.version | info:eu-repo/semantics/acceptedVersion | spa |
dc.rights.creativecommons | Atribución-NoComercial-SinDerivadas | spa |
dc.relation.references | A. Tiwana, M. K. (2013). The one-minute risk assessment tool. | spa |
dc.relation.references | AACE, A. A. (2006). Cono de la Incertidumbre. Cono de la Incertidumbre. American Association of Cost Engineers AACE. | spa |
dc.relation.references | Addison, T. V. (2002). Controlling software project risks – an empirical study of methods used by experienced project managers. Proceedings of SAICSIT. | spa |
dc.relation.references | AEC. (2009). ¿Por qué fracasan los proyectos de software? Asociación Española para la Calidad. CSTIC. | spa |
dc.relation.references | Agendum. (2007). Norma UNE 71504. | spa |
dc.relation.references | Aloini, D. D. (2007)(2012). Risk management in ERP project introduction: Review of the literature. Inf. Manag. | spa |
dc.relation.references | Anderson, D. J. (2010). Kanban: successful evolutionary change for your technology business. Blue Hole Press. | spa |
dc.relation.references | Atkinson, R. C. (2006). Fundamental uncertainties in projects and the scope of project management. Int. J. Proj. Manag. | spa |
dc.relation.references | AXELOS Limited, P. (2014). What is PRINCE2?. | spa |
dc.relation.references | Axwloa. (2011). ITIL, continual service improvement. Norwich, UK. | spa |
dc.relation.references | Baccarini, D. (2004). Management of risks in information technology projects. . Ind. Manag. Data Syst. | spa |
dc.relation.references | Balaguera, Y. D. (2015). Metodologías ágiles en el desarrollo de aplicaciones para dispositivos móviles. Revista de Tecnología. | spa |
dc.relation.references | Bannerman, P. (2008). Risk and risk management in software projects: A reassessment. 2118-2133: J. Syst. Softw. | spa |
dc.relation.references | Barki, H. R. (1993). Toward an assessment of software development risk. Journal of Management Information Systems 10. | spa |
dc.relation.references | Beck, K. (2000). Extreme programming explained: embrace change. Addison-Wesley Professional. | spa |
dc.relation.references | Benaroch, M. L. (2006). Real options in information technology risk management: An empirical validation of riskoption relationships. MIS Q. | spa |
dc.relation.references | Boehm, B. (1988). A Spiral Model for Software Development and Enhancement. IEEE Computer, 61-72. | spa |
dc.relation.references | Boehm, B. (2006). Some future trends and implications for systems and software engineering processes. J. Syst. Eng. | spa |
dc.relation.references | Boehm, B. R. (1989). Theory-W software project management: principles and examples. IEEE Transactions on Software Engineering, 902-916. | spa |
dc.relation.references | Boehm, B. T. (2003). Using risk to balance agile and plan-driven methods. 57-66. | spa |
dc.relation.references | Boehm, B. W. (1989). Software Risk Management. IEEE Computer Society. | spa |
dc.relation.references | Boehm, B. W. (1991). Software risk management: principles and practices. 32-41. | spa |
dc.relation.references | BSI, B. S. (2006). nformation security management systems. London, UK: Part 3: Guidelines for information security risk management. | spa |
dc.relation.references | Canós, J. H. (2003). Metodologías ágiles en el desarrollo de software. Universidad Politécnica de Valencia, Valencia. | spa |
dc.relation.references | Carvajal, D. (2019). Modelo Compacto de Gestión de Proyectos de Tecnología. Jornada de Gerencia de Proyectos de TI (pág. 45). Bogotá: ACIS. | spa |
dc.relation.references | CCB. (2019). Cámara de Comercio de Bogotá. Recuperado el 30 de Marzo de 2019, de https://www.ccb.org.co: https://www.ccb.org.co/Preguntas-frecuentes/Camara-de-Comercio-de-Bogota | spa |
dc.relation.references | CERT (Software Engineering Institute, Carnegie Mellon University). (2008). Octave. | spa |
dc.relation.references | Cockburn, A. H. (2001). Crystal methodologies. | spa |
dc.relation.references | Cocho, J. M. (2003). Estudio exploratorio sobre los métodos de gestión de proyectos de alto riesgo. Valencia, España: SOCOTE. | spa |
dc.relation.references | Conference Board Survey. (2001). The Conference Board Survey. | spa |
dc.relation.references | Cule, P. S. (2000). Strategies for heading off project failure. Information Systems Management, 65-73. | spa |
dc.relation.references | Charette, R. (1996). The mechanics of managing IT risk. Journal of Information Technology, 373-378. | spa |
dc.relation.references | Charette, R. N. (1989). Software Engineering Risk Analysis and Management. New York: McGraw-Hill. | spa |
dc.relation.references | Chemuturi, M. (2013). Mastering IT Project Management: Best Practices, Tools and Techniques. Florida, Estados Unidos: J. Ross Publishing. | spa |
dc.relation.references | D. Aloini, R. D. (2007). Risk management in ERP project introduction: Review of the literature. Inf. Manag. | spa |
dc.relation.references | D. Baccarini, G. S. (2004). Management of risks in information technology projects. 104, 286–295: Ind. Manag. Data Syst. | spa |
dc.relation.references | D. Lavbič, O. V. (2010). Ontology-based multi-agent system to support business users and management. Technol. Econ. Dev. Econ. | spa |
dc.relation.references | De Bakker, K. B. (2010). Does risk management contribute to IT project success? A meta-analysis of empirical evidence. Int. J. Proj. Manag. | spa |
dc.relation.references | de Camprieu, R. D. (2007). 'Cultural' differences in project risk perception: an empirical comparison of China and Canada. International Journal of Project Management, 683-693. | spa |
dc.relation.references | de Carvalho, M. R. (2015). Impact of risk management on project performance: the importance of soft skills. Int. J. Prod. | spa |
dc.relation.references | DeMarco Tom, L. T. (2003). Waltzing with Bears. New York: Dorset House Publishing. | spa |
dc.relation.references | DIAN. (2014). Reporte estadístico consolidado de los renglones de la declaración de IVA y la declaración de renta de las empresas del sector TI por códigos CIIU. Bogotá: Subdirección de Gestión de Análisis Operacional. | spa |
dc.relation.references | Drucker, P. (1975). Management. W.H. Heinemann. | spa |
dc.relation.references | Dyer, M. (1992). The Cleanroom Approach to Quality Software Development. Wiley. | spa |
dc.relation.references | E.W.N. Bernroider, C. W. (2014). From dynamic capabilities to ERP enabled business improvements: The mediating effect of the implementation project. Int. J. Proj. Manag. | spa |
dc.relation.references | Echeverry Tobón, L. M. (2007). Caso práctico de la metodología ágil XP al desarrollo de software. | spa |
dc.relation.references | El Tiempo. (1 de Junio de 2001). Sabe qué es la matrícula mercantil. El Tiempo. | spa |
dc.relation.references | Elrad, T. F. (2001). Aspect Oriented Programming. | spa |
dc.relation.references | Enciclopedia de Conceptos. (2019). Microempresa. (E. d. Concepto.de, Productor) Obtenido de https://concepto.de: https://concepto.de/microempresa/ | spa |
dc.relation.references | Fiedler, S. (2010). Managing resistance in an organizational transformation: A case study from a mobile operator company. Int. J. Proj. | spa |
dc.relation.references | Fowler, M. &. (2001). The agile manifesto. Software Development. | spa |
dc.relation.references | Gartner. (2007). Why Some Projects Fail and Others Succeed. Gartner. | spa |
dc.relation.references | Gartner. (2014). How to Increase Your IT Project Success Rate. | spa |
dc.relation.references | Gartner.com. (29 de 01 de 2013). www.gartner.com. Obtenido de Sitio Web de Gartner Inc: http://www.gartner.com/newsroom/id/2319215 | spa |
dc.relation.references | Geraldi, J. K. (2011). Towards a conceptualisation of quality in information technology projects. Int. J. Proj. Manag. | spa |
dc.relation.references | Gimson Saravia, L. E. (2012). Metodologias ágiles y desarrollo basado en conocimiento. Facultad de Informática. | spa |
dc.relation.references | Goldratt, E. (1997). Critical Chain. The North River Press, 124. | spa |
dc.relation.references | Hartono, B. S. (2014). Project risk: Theoretical concepts and stakeholders’ perspectives. Int. J. Proj. Manag. | spa |
dc.relation.references | Haugan, G. (2002). Effective WBS. Vienna, Austria: Management Concepts. | spa |
dc.relation.references | Higuera, R. (1995). Team Risk Management. CrossTalk, U.S. Dept. of Defense, 2-4. | spa |
dc.relation.references | Hillman, P. (2014). According to Gartner, 75 percent of all IT projects fail. Yours don’t? Are you sure? C/D/H Technology Report. | spa |
dc.relation.references | Huijbers, R. L. (2004). Software project management: methodologies & techniques. Department ofMathematics & Computer Science. | spa |
dc.relation.references | IBM. (2012). Seven Reasons IT Projects Fail. IBMSystems Magazine. | spa |
dc.relation.references | IDC. (11 de 08 de 2011). http://www.standishgroup.com/services.php. Obtenido de http://www.standishgroup.com: https://www.reportbuyer.com/product/1711649/improving-it-project-outcomes-by-systematically-managing-and-hedging-risk.html. | spa |
dc.relation.references | Ilies, L. C. (2010). Best Practices in Project Management. Review of International Comparative Management. | spa |
dc.relation.references | International Organization for Standardization (ISO) & International Electrotechnical Commission (IEC). (2011). ISO/IEC 27005: gestión de riesgos de seguridad de la Información. Geneve, Swizerland. | spa |
dc.relation.references | International Organization for Standardization (ISO) & International Electrotechnical Commission (IEC). (2011). Risk management — Risk assessment techniques (IEC/FDIS 31010). | spa |
dc.relation.references | IPMA. (2006). International Project Management Association, IPMA. UK. | spa |
dc.relation.references | ISACA. (2013). The RISK IT Framework. ISACA org. | spa |
dc.relation.references | ISO. (2012). Directrices para la Dirección y Gestión de Proyectos. México: ISO. | spa |
dc.relation.references | Jaureche, S. (2012). Tesis de Maestría en Computación “Métodos de Gestión de Riesgos en Proyectos de Software”. Colibri Conocimiento Libre Repositorio Institucional. | spa |
dc.relation.references | Jennifer, L. (4 de Octubre de 2015). Standish Group 2015 Chaos Report - Q&A with Jennifer Lynch. Obtenido de InfoQ: https://www.infoq.com/articles/standish-chaos-2015. | spa |
dc.relation.references | Jiang, J. K. (2002). A measure of software development risk. 30-41. | spa |
dc.relation.references | Jiang, J. M. (2000). User resistance and strategies for promoting acceptance across system types. Inf. Manag. | spa |
dc.relation.references | Jimenez, J. (2006). Modelos de procesos de Software. Universidad Mayor de San Andrés. | spa |
dc.relation.references | Johnson, J. B. (2001). Project management: the criteria for success. Software Magazine 21. | spa |
dc.relation.references | Juran, J. (1975). The Non-Pareto Principle; Mea Culpa. Juran Institute. | spa |
dc.relation.references | K. El Emam, A. K. (2008). A replicated survey of IT software project failures. IEEE Softw. | spa |
dc.relation.references | K. Hong, Y. K. (2002). The critical success factors for ERP implementation: an organizational fit perspective. Inf. Manag. | spa |
dc.relation.references | K. Kwahk, H. K. (2007). Managing readiness in enterprise systemsdriven organizational change. Behav. Inf. Technol. | spa |
dc.relation.references | Kappelman, L. M. (2006). Early warning signs of IT project failure: The dominant dozen. Inf. Syst. Manag. | spa |
dc.relation.references | Keil, M. C. (1998). A framework for identifying software project risks. Communications of the ACM, 76-83. | spa |
dc.relation.references | Keil, M. T. (2002). Reconciling user and project manager perceptions of IT project risk. Information Systems Journal, 103-119. | spa |
dc.relation.references | Keil, M. W. (2000). An investigation of risk perception and risk propensity on the decision to continue a software development project. Journal of Systems and Software, 145-157. | spa |
dc.relation.references | Kerzner, H. (2003). Project Management: A Systems Approach to Planning, Scheduling, and Controlling. John Wiley & Sons, Hoboken. | spa |
dc.relation.references | Kim, H.-W. (2011). The effects of switching costs on user resistance to enterprise systems implementation. IEEE Trans. | spa |
dc.relation.references | KLCL research group report. (s.f.). Software Risk Management Practices. Estados Unidos: KLCL research group report. | spa |
dc.relation.references | Kniberg, H. S. (2010). Kanban y Scrum-obteniendo lo mejor de ambos. Prólogo de Mary Poppendieck & David Anderson. C4Media Inc. | spa |
dc.relation.references | KPMG Canada. (1997). The KPMG Canada Survey. Canada: KPMG Canada. | spa |
dc.relation.references | Kutsch, E. H. (2005). Intervening conditions on the management of project risk: Dealing with uncertainty in information technology projects. Int. J. Proj. Manag. | spa |
dc.relation.references | L. Wallace, M. K. (2004). Understanding software project risk: a cluster analysis. 115–125: Inf. Manag. | spa |
dc.relation.references | Lam, W. (2004). Technical risk management on enterprise integration projects. Communications of the AIS, 290-315. | spa |
dc.relation.references | Laumer, S. (2011). Why Do people reject technologies – a literature-based discussion of the phenomena “resistance to change”. ECIS. | spa |
dc.relation.references | Letelier, P. (2006). Metodologías ágiles para el desarrollo de software: eXtreme Programming (XP). | spa |
dc.relation.references | Lucas, H. 1. (1981). Implementation: The Key to Successful Information Systems. Columbia University Press. | spa |
dc.relation.references | Lundy, V. M. (2013). Project leadership influences resistance to change: the case of the Canadian public service. Proj. Manag. | spa |
dc.relation.references | Lyytinen, K. M. (1996). A framework for software risk management. 275-285. | spa |
dc.relation.references | Lyytinen, K. M. (1998). Attention shaping and software risk: a categorical analysis of four classical risk management approaches. Information Systems Research, 233-255. | spa |
dc.relation.references | M. Altuwaijri, M. K. (2011). A project-based model for successful IT innovation diffusion. Int. J. Proj. Manag. | spa |
dc.relation.references | Marcelo, J. &. (2003). Estudio exploratorio sobre los métodos de gestión de proyectos de alto riesgo. Primer Congreso Soporte del Conocimiento con la Técnología. Valencia, España: SOCOTE. | spa |
dc.relation.references | MARCO, M. (2013). A Guide to the Agile Management Body of Knowledge (ABOK). ABOK.org. | spa |
dc.relation.references | March, J. S. (1987). Managerial perspectives on risk and risk taking. Management Science, 1404-1418. | spa |
dc.relation.references | McConnell, S. (2006). The Cone of Uncertainty. IEEE SOFTWARE, 8-10. | spa |
dc.relation.references | McFarlan, F. (1981). Portfolio approach to information systems. Harvard Business Review, 142-150. | spa |
dc.relation.references | McKeen, J. S. (2003). Making IT Happen: Critical Issues in IT Management. | spa |
dc.relation.references | Meissonier, R. H. (2010). . Toward an “IT Conflict-Resistance Theory”: action research during IT pre-implementation. Eur. J. Inf. Syst. | spa |
dc.relation.references | Mills, H. D. (1980). Software Engineering-Education. IEEE, 1158-1162. | spa |
dc.relation.references | Mills, H. D. (1987). Cleanroom Software Engineering. IEEE Software, 19-25. | spa |
dc.relation.references | Ministerio de Hacienda y Administraciones Públicas MHAP. (2012). MAGERIT – versión 3.0. Metodología de análisis y gestión de riesgos de los sistemas de información. Madrid, España. | spa |
dc.relation.references | MINTIC. (2014). Conformación del Directorio de Empresas Activas de la Industria del Software y Servicios Asociados con TI de Colombia. Bogotá: MINTIC. | spa |
dc.relation.references | MINTIC. (2015). Caracterización del Sector Teleinformática, Software y TI en Colombia 2015. Bogotá: Observatorio de Tecnologías de Información. | spa |
dc.relation.references | Mursu, A. L. (2003). Identifying software project risks in Nigeria: an international comparative study. European Journal of Information Systems, 182–194. | spa |
dc.relation.references | Nierstrasz, O. S. (1992). Component-Oriented Software Development. CACM, 160.165. | spa |
dc.relation.references | Ordysinski, T. (2014). System Kanban w administracji publicznej. Roczniki Kolegium Analiz Ekonomicznych/Szkola Glowna Handlowa. | spa |
dc.relation.references | Osipova, E. E. (2013). Balancing control and flexibility in joint risk management: Lessons learned from two construction projects. Int. J. Proj. | spa |
dc.relation.references | P. Cule, R. S. (2000). Strategies for Heading Off is Project Failure. Inf. Syst. Manag. | spa |
dc.relation.references | Parkinson, C. N. (1982). Parkinson's Law, or The Pursuit of Progress, C. Northcote Parkinson, 1957. EDICIONES GRIJALBO, S.A., 24-32. | spa |
dc.relation.references | Paul, R. (2014). The Dimensions of Software Engineering Success. 36th International Conference on Software Engineering (págs. 24-35). Hyderabad, India: ACM Digital Library. | spa |
dc.relation.references | Pérez, E. T. (2016). Herramientas tecnológicas aplicables al Kanban para la optimización de los procesos en la empresa. Visión Gerencial. | spa |
dc.relation.references | PeritoIT. (8 de Noviembre de 2016). Perito Informático y Tecnológico. Obtenido de El fracaso de los proyectos TIC’s, incumplimientos prestacionales y su reclamación judicial: https://peritoit.com/2016/11/08/el-fracaso-de-los-proyectos-tics-y-su-reclamacion-judicial/ | spa |
dc.relation.references | Perkins, B. (2007). 12 Things You Know About Projects but Choose to Ignore. | spa |
dc.relation.references | PMI. (2013). Guía de los Fundamentos para la Dirección de Proyectos. USA: PMI. | spa |
dc.relation.references | PMI. (2017). Pulse of the Profession. PMI. | spa |
dc.relation.references | Pressman, R. (2010). Ingeniería de Software. México: McGraw Hill. | spa |
dc.relation.references | Pressman, R. (2011). El software y la Ingeniera de Software. México: McGraw Hill. | spa |
dc.relation.references | PRINCE2. (2009). PRINCE2. UK: Prince2. | spa |
dc.relation.references | Project Management Institute, I. (2014). What is PMI?. | spa |
dc.relation.references | Project Management Institute. (2013). GUÍA DE LOS FUNDAMENTOS PARA LA DIRECCIÓN DE PROYECTOS. Pensilvania, Newtown Square: Project Management Institute. | spa |
dc.relation.references | RAE, R. A. (2018). Diccionario de la Lengua Española. | spa |
dc.relation.references | Ramírez, A. C. (2011). Comparación de cuatro sistemas de certificación del ámbito de la dirección de proyectos. Universidad Politécnica de Madrid, Madrid. | spa |
dc.relation.references | Research and Markets, S. (2010). Global Industry Guide. | spa |
dc.relation.references | Rivard, S. L. (2012). Information technology Implementers’ responses to user resistance: nature and effects. MIS Q. | spa |
dc.relation.references | Rivera Rincón, N. (2014). ¿PORQUE FRACASAN LOS PROYECTOS DE DESARROLLO DE SOFTWARE? Universidad Militar Nueva Granada, Bogotá, Colombia. | spa |
dc.relation.references | Robbins-Gioia LLC. (2001). The Robbins-Gioia Survey. Virgina, USA: The Robbins-Gioia Survey. | spa |
dc.relation.references | Rodriguez Gonzalez, P. (2008). Estudio de la Aplicación de Metodologias Ágiles para la Evolución de Productos Software. Informatica. | spa |
dc.relation.references | Ropponen, J. (1999). Risk assessment and management practices in software development, 247-266. | spa |
dc.relation.references | Ropponen, J. L. (2000). Components of software development risk: How to address them? A project manager survey. IEEE Transactions on Software Engineering , 98-112. | spa |
dc.relation.references | Royce, W. (1970). Managing the development of large software systems. IEEE WESCON. | spa |
dc.relation.references | Ryte. (2019). Heat Map. Obtenido de RYTE WIKI: https://es.ryte.com/wiki/Heat_Map. | spa |
dc.relation.references | Sanderson, J. (2012). Risk, uncertainty and governance in megaprojects: A critical discussion of alternative explanations. Int. J. Proj. Manag. | spa |
dc.relation.references | Schmidt, R. L. (2001). Identifying software project risks: an international Delphi study. Journal of Management Information Systems, 5-36. | spa |
dc.relation.references | Schultz, R. S. (1987). Strategy and tactics in a process model of project implementation. Interfaces, 34-46. | spa |
dc.relation.references | Schwaber, K. &. (2002). Agilé Software Development with Scrum. | spa |
dc.relation.references | Schwalbe, K. (2007). Project Risk Management. 446-488. | spa |
dc.relation.references | Seguridad Informática. (2005). Herramienta de Evaluación de Riesgo-CRAMM. Metodologías de análisis de riesgos. | spa |
dc.relation.references | Shahzad Basit, J. I. (2007). Software Risk Management – Prioritization of frequently occurring Risk in Software Development Phases. Using Relative Impact Risk Model. 2nd International Conference on Information and Communication Technology (ICICT). | spa |
dc.relation.references | Sharma, A. G. (2012). Impact of organisational climate and demographics on project specific risks in context to Indian software industry. Int. J. Proj. Manag. | spa |
dc.relation.references | Shinohara Y. (1995). The OASIG Study. UK: OASIG. | spa |
dc.relation.references | Simister, S. (2004). Qualitative and quantitative risk management. 30-47. | spa |
dc.relation.references | Smith, A. D. (2014). Pulse of the Profession In-Depth Report: Requirements Management — A Core Competency for Project and Program Success. Project Management Institute. Project Management Institute. | spa |
dc.relation.references | Söderlund, J. M. (2012). Project management scholarship: Relevance, impact and five integrative challenges for business and management schools. Int. J. Proj. | spa |
dc.relation.references | Sommerville, I. (2011). Ingeniería de Software. México: Pearson Educación. | spa |
dc.relation.references | Standish Group. (17 de 06 de 2013). CHAOS MANIFESTO 2013 - Think Big, Act Small. Massachusetts, USA. Obtenido de http://www.standishgroup.com/services.php: https://www.standishgroup.com/store/ | spa |
dc.relation.references | Standish Group. (4 de Octubre de 2015). Standish Group. Obtenido de The Standish Group: https://www.standishgroup.com/store/services/chaos-report-2015-blue-pm2go-membership.html | spa |
dc.relation.references | Stretton, A. (2007). A Short History of Modern Project Management. PM World Today. | spa |
dc.relation.references | SUTHERLAND, J. &. (2015). Scrum Guides FrameWork. ScrumGuides.org. | spa |
dc.relation.references | TAKEUCHI, H. &. (1986). The New Development Product Game. Harvard Business Review. | spa |
dc.relation.references | Tan, S. (2014). How to Increase Your IT Project Success Rate. Gartner. | spa |
dc.relation.references | Thamhain, H. (2013). Managing risks in complex projects. Proj. Manag. J. | spa |
dc.relation.references | Tiwana, A. K. (2004). The one-minute risk assessment tool. 73-77. | spa |
dc.relation.references | U.S. Air Force. (1988). Software Risk Abatement. AFCS/AFLC Pamphlet, 800-845. | spa |
dc.relation.references | Universidad EAFIT. (2007). COBIT: modelo para auditoria y control de sistemas de información. Medellín, Colombia. | spa |
dc.relation.references | Vilar, B. (2013). Programación de proyectos con múltiples calendarios. Tesis de maestría, Universidad Politécnica de Valencia. | spa |
dc.relation.references | Wallace, L. K. (2004). How software project risk affects project performance: an investigation of the dimensions of risk and an exploratory model. 289-321. | spa |
dc.relation.references | Weaver, P. (2012). Debunking the myths, a retrospective view of his work. PM World Journal. | spa |
dc.relation.references | Y. Li, M. Y. (2011). The role of team problem solving competency in information system development projects. Int. J. Proj. Manag. | spa |
dc.relation.references | Zander, A. (1950). 50. Resistance to change – its analysis and prevention. Adv. Manag. | spa |
dc.relation.references | Zapata, A. M. (2006). Organización y Management. Cali, Colombia: Editorial Universidad del Valle. | spa |
dc.relation.references | Zmud, R. (1979). Individual differences and MIS success: a review of the empirical literature. Management Science, 966-979. | spa |
dc.relation.references | Žvanut, B. P. (2011). The effect of voluntariness on the acceptance of e-learning by nursing students. Nurse Educ. | spa |
dc.subject.proposal | Software | spa |
dc.subject.proposal | Modelo | spa |
dc.subject.proposal | Proyecto | spa |
dc.subject.proposal | Riesgo | spa |
dc.subject.proposal | Indicadores | spa |
dc.subject.proposal | Fábrica | spa |