[1]
(2017-18 onward) High-performing teams: A timeless leadership topic | McKinsey & Company: http://www.mckinsey.com/business-functions/organization/our-insights/high-performing-teams-a-timeless-leadership-topic?cid=other-eml-alt-mkq-mck-oth-1706&hlkid=c65b3bce65394c58bcd20b42734768fb&hctky=9780532&hdpid=78eda6de-3cf8-4fd5-8864-a05f38db34d5.
[2]
Andersen, E.S. 2008. Rethinking project management: an organisational perspective. FT Prentice Hall.
[3]
Ashrov, A. et al. 2015. A use-case for behavioral programming: An architecture in JavaScript and Blockly for interactive applications with cross-cutting scenarios. Science of Computer Programming. 98, (Feb. 2015), 268–292. DOI:https://doi.org/10.1016/j.scico.2014.01.017.
[4]
Augustine, S. 2005. Managing Agile Projects. Prentice Hall.
[5]
Bass, L. et al. 2003. Software architecture in practice. Addison-Wesley.
[6]
Bernard Marr 2012. Key performance indicators. Pearson Financial Times Pub.
[7]
Bott, F. 2014. Professional issues in information technology. BCS Learning and Development Ltd.
[8]
British Computer Society Code of conduct (i.e. professional ethics): http://www.bcs.org/category/6030.
[9]
Brown, N. et al. 2010. Enabling Agility Through Architecture. Software Engineering Institute.
[10]
Chapman, C.B. et al. 2011. How to manage project opportunity and risk: why uncertainty management can be a much better approach than risk management. Wiley.
[11]
CMMI Product Team 2010. CMMI for Development, Version 1.3 (Technical Report CMU/SEI-2010-TR-033). Software Engineering Institute, Carnegie Mellon University.
[12]
Cohn, M. 2010. Succeeding with agile: software development using Scrum. Addison-Wesley.
[13]
Cohn, M. 2004. User stories applied: for agile software development. Addison-Wesley.
[14]
Collins, G. 2017. Agile Project Management. Project Management, Planning and Control. Elsevier. 523–538.
[15]
ComputerWeekly.com | Information Technology (IT) News, UK IT Jobs, Industry News: http://www.computerweekly.com/.
[16]
Ekas, L. and Will, S. 2013. Being Agile: Eleven Breakthrough Techniques to Keep You from "Waterfalling Backward”. IBM Press.
[17]
Eklund, U. and Arts, T. 2010. A Classification of Value for Software Architecture Decisions. Software Architecture. M.A. Babar and I. Gorton, eds. Springer Berlin Heidelberg. 368–375.
[18]
Finding and fixing software bugs automatically with SapFix and Sapienz - Facebook Code: https://code.fb.com/developer-tools/finding-and-fixing-software-bugs-automatically-with-sapfix-and-sapienz/.
[19]
Finkelstein, A. et al. 2009. A search based approach to fairness analysis in requirement assignments to aid negotiation, mediation and decision making. Requirements Engineering. 14, 4 (Dec. 2009), 231–245. DOI:https://doi.org/10.1007/s00766-009-0075-y.
[20]
Guide to the GDPR: 2018. https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/.
[21]
Harman, M. 2012. The role of Artificial Intelligence in Software Engineering. 2012 First International Workshop on Realizing AI Synergies in Software Engineering (RAISE) (Jun. 2012), 1–6.
[22]
van Heesch, U. et al. 2014. (2017-18 onward) Decision-Centric Architecture Reviews. IEEE Software. 31, 1 (Jan. 2014), 69–76. DOI:https://doi.org/10.1109/MS.2013.22.
[23]
Humble, J. et al. 2018. Accelerate. IT Revolution Press.
[24]
Humble, J. et al. 3AD. Lean Enterprise: How High Performance Organizations Innovate at Scale (Lean (O’Reilly)). O’Reilly Media; 1 edition.
[25]
Inclusive Design Toolkit Home: http://www.inclusivedesigntoolkit.com/betterdesign2/.
[26]
IT Jobs Watch, Tracking the IT Job Market: http://www.itjobswatch.co.uk/.
[27]
Jones, C. 2010. Software engineering best practices: lessons from successful projects in the top companies. McGraw-Hill.
[28]
Jones, C. 2010. Software engineering best practices: lessons from successful projects in the top companies. McGraw-Hill.
[29]
Kahneman, D. 2011. Thinking, fast and slow. Allen Lane.
[30]
Kaplan, R.S. and Norton, D.P. 1996. The balanced scorecard: translating strategy into action. Harvard Business School Press.
[31]
Kim, G. et al. 2016. (2017-18 onward) The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organisations. IT Revolution.
[32]
Knight, J.C. and Leveson, N.G. 2002. Should software engineers be licensed? Communications of the ACM. 45, 11 (Nov. 2002). DOI:https://doi.org/10.1145/581571.581601.
[33]
Laplante, P.A. 2013. An international perspective on U.S. licensure of software engineers. IEEE Technology and Society Magazine. 32, 1 (Spring 2013), 28–30. DOI:https://doi.org/10.1109/MTS.2013.2241295.
[34]
Laplante, P.A. 2014. Licensing professional software engineers. Communications of the ACM. 57, 7 (Jul. 2014), 38–40. DOI:https://doi.org/10.1145/2618111.
[35]
Lester, A. 2014. Project management, planning and control: managing engineering, construction and manufacturing projects to PMI, APM, and BSI standards. Butterworth-Heinemann.
[36]
Microservices: http://martinfowler.com/articles/microservices.html.
[37]
NASA 2015. Appendix J - Joint Cost and Schedule Confidence level (JCL) Analysis. NASA Cost Estimating Handbook Version 4.0. National Aeronautics and Space Administration. J-1-45.
[38]
NASA Understanding Joint Confidence Level (JCL) at NASA. NASA.
[39]
News and analysis for UK IT directors, CTOs and CIOs - Computing: http://www.computing.co.uk/.
[40]
October, 2014 - Insufficient data from Andrew Fryer - Site Home - TechNet Blogs: http://blogs.technet.com/b/andrew/archive/2014/10.aspx.
[41]
Personas: http://www.usability.gov/how-to-and-tools/methods/personas.html.
[42]
Schmidt, E. et al. Google: how Google works. Grand Central Publishing.
[43]
Schwartz, M. 2016. (2017-18 onward) The Art of Business Value. IT Revolution.
[44]
SD Times - Software Development News: http://sdtimes.com/.
[45]
Slashdot: http://slashdot.org/.
[46]
Strode, D.E. et al. 2012. Coordination in co-located agile software development projects. Journal of Systems and Software. 85, 6 (Jun. 2012), 1222–1238. DOI:https://doi.org/10.1016/j.jss.2012.02.017.
[47]
Taleb, N. 2007. Fooled by randomness: the hidden role of chance in life and in the markets. Penguin.
[48]
The Register: Sci/Tech News for the World: http://www.theregister.co.uk/.
[49]
UI in an Agile Process - The Quick ‘n’ Dirty Approach in the Real World: http://www.infoq.com/presentations/UI-in-an-Agile-Process.
[50]
Watts S. Humphrey 2010. Reflections on management. Addison-Wesley.
[51]
2007. Beautiful code. O’Reilly.
[52]
Lastminute.com energises product discovery and development.
[53]
22AD. Lean-Agile Software Development: Achieving Enterprise Agility (Net Objectives Lean-Agile Series). Addison-Wesley Professional; 1 edition.