Gestión de Proyectos

Gestión de proyectos con PRince2

Buenas prácticas en la Gestión de Propyectos

Sitio web oficial: Sitio oficial de PRINCE2

http://www.lcc.uma.es/~guzman/prince2/PRINCE2.pdf

Gestión de proyectos

[1] PMI, 2014: http://www.pmi.org/Certification/New-PMI-Agile-Certification/PMI-Agile-Toolbox.aspx

[2] Enero de 2012 eJournal “PM World Today”, del artículo “Enhanced PMBOK ® by Comparing it eith P2M, ICB, PRINCE2, APM and Scrum Project Managment Standars” escrito por Sam Ghosh, Danny Forrest, Thomas DiNetta Brian Wolfe & Danielle C. Lambert para “Masters in Project Management Degree Program” para la escuela “James A. Clarke School of Engineering, University of Maryland, USA”.

[3] PMBOK, 2014: http://www.pmi.org/PMBOK-Guide-and-Standards.aspx

[4] PRINCE2, 2014: https://www.axelos.com/prince2

[5] SCRUM, 2014: http://www.scrummanager.net/oks/

[6] ELSEVIER, 2013. Prince2 or PMBOK – a question of choice. Sandra Matos, Eurico Lopes.

[7] Farid, W.M.; Mitropoulos, F.J., "NORPLAN: Non-functional Requirements Planning for agile processes,"Southeastcon, 2013 Proceedings of IEEE , vol., no., pp.1,8, 4-7 April 2013

doi: 10.1109/SECON.2013.6567463

[8] Farid, W.M.; Mitropoulos, F.J., "Visualization and scheduling of non-functional requirements for agile processes," Southeastcon, 2013 Proceedings of IEEE , vol., no., pp.1,8, 4-7 April 2013

doi: 10.1109/SECON.2013.6567413

20150901-TFM_Prince2Scrum_RafaelReina.pdf

Bibliografía

Desarrollo ágiL

[1] Khan, P.M.; Beg, M.M.S.S., "Extended Decision Support Matrix for Selection of SDLC-Models on Traditional and Agile Software Development Projects," Advanced Computing and Communication Technologies (ACCT), 2013 Third International Conference on , vol., no., pp.8,15, 6-7 April 2013 (doi: 10.1109/ACCT.2013.12)

[2] Ernst, N.A.; Murphy, G.C., "Case studies in just-in-time requirements analysis," Empirical Requirements Engineering (EmpiRE), 2012 IEEE Second International Workshop on , vol., no., pp.25,32, 25-25 Sept. 2012 (doi: 10.1109/EmpiRE.2012.6347678)

[3] Duran, K.; Burns, G.; Snell, P., "Lehman's laws in agile and non-agile projects," Reverse Engineering (WCRE), 2013 20th Working Conference on , vol., no., pp.292,300, 14-17 Oct. 2013 (doi: 10.1109/WCRE.2013.6671304)

[4] Martakis, A.; Daneva, M., "Handling requirements dependencies in agile projects: A focus group with agile software development practitioners,"Research Challenges in Information Science (RCIS), 2013 IEEE Seventh International Conference on , vol., no., pp.1,11, 29-31 May 2013 (doi: 10.1109/RCIS.2013.6577679)

[5] W. W. Royce, “Managing the development of large software systems,” in proceedings of IEEE WESCON, vol. 26, no. 8. Los Angeles, 1970.

[6] D. Leffingwell, Scaling software agility: best practices for large enterprises. Pearson Education, 2007.

[7] K. Beck, M. Beedle, A. Van Bennekum, A. Cockburn, W. Cunningham, M. Fowler, J. Grenning, J. Highsmith, A. Hunt, R. Jeffries et al., “Manifesto for agile software development,” 2001.

[8] R. C. Martin, Agile software development: principles, patterns, and practices. Prentice Hall PTR, 2003.

[9] S. McConnell, “Technical debt,” 10x Software Development Blog,(Nov 2007). Construx Conversations. URL= http://blogs.construx.com/blogs/stevemcc/archive/2007/11/01/technical-debt-2.aspx, 2007.

[10] W. Cunningham, “The WyCash portfolio management system,” in Addendum to the proceedings on Object-oriented programming systems, languages, and applications (OOPSLA), vol. 18, no. 22, 1992, pp. 29–30.

[11] N. Brown, Y. Cai, Y. Guo, R. Kazman, M. Kim, P. Kruchten, E. Lim, A. MacCormack, R. Nord, I. Ozkaya et al., “Managing technical debt in software-reliant systems,” in Proceedings of the FSE/SDP workshop on Future of software engineering research. ACM, 2010, pp. 47–52.

[12] I. Ozkaya, P. Kruchten, R. L. Nord, and N. Brown, “Managing technical debt in software development: report on the 2nd international workshop on managing technical debt, held at icse 2011,” SIGSOFT Softw. Eng. Notes, vol. 36, no. 5, pp. 33–35, Sep. 2011.

[13] P. Kruchten, R. L. Nord, I. Ozkaya, and J. Visser, “Technical debt in software development: from metaphor to theory report on the third international workshop on managing technical debt,” ACM SIGSOFT Software Engineering Notes, vol. 37, no. 5, pp. 36–38, 2012.

[14] C. Seaman, Y. Guo, C. Izurieta, Y. Cai, N. Zazworka, F. Shull, and A. Vetro, “Using technical debt data in decision making: Potential decision approaches,” in Managing Technical Debt (MTD), 2012 Third International Workshop on. IEEE, 2012, pp. 45–48.

[15] P. Kruchten, R. L. Nord, and I. Ozkaya, “Technical debt: From metaphor to theory and practice.” IEEE Software, vol. 29, no. 6, 2012.

[16] ——, “4th international workshop on managing technical debt (mtd 2013),” in Software Engineering (ICSE), 2013 35th International Conference on. IEEE, 2013, pp. 1535–1536.

[17] T. Klinger, P. Tarr, P. Wagstrom, and C. Williams, “An enterprise perspective on technical debt,” in Proceedings of the 2nd Workshop on Managing Technical Debt. ACM, 2011, pp. 35–38.

[18] W. Snipes, B. Robinson, Y. Guo, and C. Seaman, “Defining the decision factors for managing defects: a technical debt perspective,” in Managing Technical Debt (MTD), 2012 Third International Workshop on. IEEE, 2012, pp. 54–60.

[19] R. O. Spinola, A. Vetro, N. Zazworka, C. Seaman, and F. Shull, “Investigating technical debt folklore: Shedding some light on technical debt opinion,” in Managing Technical Debt (MTD), 2013 4th International Workshop on. IEEE, 2013, pp. 1–7.

[20] Z. Codabux and B. Williams, “Managing technical debt: An industrial case study,” in Managing Technical Debt (MTD), 2013 4th International Workshop on. IEEE, 2013, pp. 8–15.

[21] E. Lim, N. Taksande, and C. Seaman, “A balancing act: what software practitioners have to say about technical debt,” Software, IEEE, vol. 29, no. 6, pp. 22–27, 2012.

[22] O. Salo and P. Abrahamsson, “Agile methods in european embedded software development organisations: a survey on the actual use and usefulness of extreme programming and scrum,” Software, IET, vol. 2, no. 1, pp. 58–64, 2008.

[23] B. Bruegge and A. A. Dutoit, Object-oriented software engineering; conquering complex and changing systems. Prentice Hall PTR, 1999.

[24] K. Beck and C. Andres, Extreme programming explained: embrace change. Addison-Wesley Professional, 2004.

[25] L. Vijayasarathy and D. Turk, “Agile software development: A survey of early adopters,” Journal of Information Technology Management, vol. 19, no. 2, pp. 1–8, 2008.

[26] P. Abrahamsson, O. Salo, J. Ronkainen, and J. Warsta, “Agile software development methods: Review and analysis,” 2002.

[27] K. Schwaber and M. Beedle, Agile software development with Scrum. Prentice Hall PTR Upper Saddle Riverˆ eNJ NJ, 2002, vol. 18.

[28] P. L. Alreck and R. B. Settle, The survey research handbook. Irwin Homewood, IL, 1985, vol. 2.

[29] McHugh, O.; Conboy, K.; Lang, M., "Agile Practices: The Impact on Trust in Software Project Teams," Software, IEEE, vol.29, no.3, pp.71,76, May-June 2012. (doi: 10.1109/MS.2011.118)

[30] Melo, C.; Cruzes, D.S.; Kon, F.; Conradi, R., "Agile Team Perceptions of Productivity Factors,"Agile Conference (AGILE), 2011 , vol., no., pp.57,66, 7-13 Aug. 2011 (doi: 10.1109/AGILE.2011.35)

[31] Prokhorenko, S., "Skiing and Boxing: Coaching Product and Enterprise Teams," Agile Conference (AGILE), 2012 , vol., no., pp.191,196, 13-17 Aug. 2012 (doi: 10.1109/Agile.2012.30).

[32] “Agile Software Construction”, John Hunt, Springer, 2006

[33] Agile Movement in General, 2014: www.agilealliance.org (Agile Software Development Alliance)

[34] Agile Modelling, 2014: www.agilemodeling.com (Agile Modelling mailing list)

[35] Agile Manifesto, 2014: www.agilemanifesto.org

SCRUM

[1] B Kitchenham, P Brereton. (2013) "A systematic review of systematic review process research in software engineering". Elsevier. Information and software technology 55 (12), 2049- 2075

[2] Remi-Armand Collaris, Eef Dekker and Jolande van Veen. (2010). Magazine Agile Records. " Scrum in Traditional Project Organization".

[3] Hrafnhildur Sif Sverrisdottira, Helgi Thor Ingasonb, Haukur Ingi Jonassonc, 2014. 27th IPMA World Congress. "The role of the product owner in Scrum - comparison between theory and practices".

[4] Dr. James Mitchell Lee.2012. SCRUMDAY. “Scrum and PRINCE2 ® Together making projects work”.

[5] Rankins G J, Kearns M. (2008). “ Integrating PRINCE2 and Scrum for successful new product development “. Australian Institute of Project Management National Conference.

[6] Martin Tomanek and Jan Juricek. (2015). International Journal of Software Engineering & Applications (IJSEA), Vol.6, No.1. “PROJECT RISK MANAGEMENT MODEL BASED ON PRINCE2 AND SCRUM FRAMEWORKS”. Department of Systems Analysis, University of Economics, Prague, Czech Republic.

[7] 2010. Birds of a Feather session. APMG Best Practice Showcase August 6 2010. Agile and PRINCE2 – Can they work together?

[8]http://www.knowledgetrain.co.uk/blog/prince2-Scrum-comparison.php What’s the difference between PRINCE2 and Scrum?

[9]https://www.Scrumalliance.org/community/articles/2014/march/success-story-prince2- Scrum-delivers-ontrak-on-tim

Success Story: PRINCE2 + Scrum Delivers ONTRAK on Time

[10]http://p-a-m.org/2013/05/prince2-with-Scrum-–-or-–-Scrum-with-prince2/

Report abuse