1.
British Computer Society Code of conduct (i.e. professional ethics), http://www.bcs.org/category/6030.
2.
Laplante, P.A.: Licensing professional software engineers. Communications of the ACM. 57, 38–40 (2014). https://doi.org/10.1145/2618111.
3.
Knight, J.C., Leveson, N.G.: Should software engineers be licensed? Communications of the ACM. 45, (2002). https://doi.org/10.1145/581571.581601.
4.
Laplante, P.A.: An international perspective on U.S. licensure of software engineers. IEEE Technology and Society Magazine. 32, 28–30 (2013). https://doi.org/10.1109/MTS.2013.2241295.
5.
Guide to the GDPR, https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/.
6.
Bott, F.: Professional issues in information technology. BCS Learning and Development Ltd, Swindon, UK (2014).
7.
Harman, M.: The role of Artificial Intelligence in Software Engineering. In: 2012 First International Workshop on Realizing AI Synergies in Software Engineering (RAISE). pp. 1–6. IEEE (2012). https://doi.org/10.1109/RAISE.2012.6227961.
8.
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/.
9.
The Register: Sci/Tech News for the World, http://www.theregister.co.uk/.
10.
News and analysis for UK IT directors, CTOs and CIOs - Computing, http://www.computing.co.uk/.
11.
ComputerWeekly.com | Information Technology (IT) News, UK IT Jobs, Industry News, http://www.computerweekly.com/.
12.
SD Times - Software Development News, http://sdtimes.com/.
13.
Slashdot, http://slashdot.org/.
14.
IT Jobs Watch, Tracking the IT Job Market, http://www.itjobswatch.co.uk/.
15.
Jones, C.: Software engineering best practices: lessons from successful projects in the top companies. McGraw-Hill, New York (2010).
16.
Humble, J., Kim, G., Forsgren, N.: Accelerate. IT Revolution Press (2018).
17.
Kim, G., Humble, J., Debois, P., Willis, J.: (2017-18 onward) The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organisations. IT Revolution (2016).
18.
Schwartz, M.: (2017-18 onward) The Art of Business Value. IT Revolution (2016).
19.
van Heesch, U., Eloranta, V.-P., Avgeriou, P., Koskimies, K., Harrison, N.: (2017-18 onward) Decision-Centric Architecture Reviews. IEEE Software. 31, 69–76 (2014). https://doi.org/10.1109/MS.2013.22.
20.
Scott Keller, Mary Meaney: (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.
21.
Ekas, L., Will, S.: Being Agile: Eleven Breakthrough Techniques to Keep You from "Waterfalling Backward”. IBM Press (2013).
22.
Lean-Agile Software Development: Achieving Enterprise Agility (Net Objectives Lean-Agile Series). Addison-Wesley Professional; 1 edition (22)AD.
23.
Schmidt, E., Rosenberg, J., Eagle, A., Page, L.: Google: how Google works. Grand Central Publishing, New York.
24.
Cohn, M.: Succeeding with agile: software development using Scrum. Addison-Wesley, Upper Saddle River, N.J. (2010).
25.
Cohn, M.: User stories applied: for agile software development. Addison-Wesley, Boston [Mass.] (2004).
26.
Lester, A.: Project management, planning and control: managing engineering, construction and manufacturing projects to PMI, APM, and BSI standards. Butterworth-Heinemann, Amsterdam (2014).
27.
Humble, J., Molesky, J., O’Reilly, B.: Lean Enterprise: How High Performance Organizations Innovate at Scale (Lean (O’Reilly)). O’Reilly Media; 1 edition (3)AD.
28.
Augustine, S.: Managing Agile Projects. Prentice Hall (2005).
29.
Bass, L., Clements, P., Kazman, R.: Software architecture in practice. Addison-Wesley, Boston, MA (2003).
30.
Watts S. Humphrey: Reflections on management. Addison-Wesley, Upper Saddle River, NJ (2010).
31.
Andersen, E.S.: Rethinking project management: an organisational perspective. FT Prentice Hall, Harlow (2008).
32.
Jones, C.: Software engineering best practices: lessons from successful projects in the top companies. McGraw-Hill, New York (2010).
33.
Chapman, C.B., Ward, S., Chapman, C.B.: How to manage project opportunity and risk: why uncertainty management can be a much better approach than risk management. Wiley, Chichester (2011).
34.
Taleb, N.: Fooled by randomness: the hidden role of chance in life and in the markets. Penguin, London (2007).
35.
Beautiful code. O’Reilly, Beijing (2007).
36.
Kaplan, R.S., Norton, D.P.: The balanced scorecard: translating strategy into action. Harvard Business School Press, Boston, Mass (1996).
37.
Bernard Marr: Key performance indicators. Pearson Financial Times Pub., New York (2012).
38.
Kahneman, D.: Thinking, fast and slow. Allen Lane, London (2011).
39.
CMMI Product Team: CMMI for Development, Version 1.3 (Technical Report CMU/SEI-2010-TR-033), http://resources.sei.cmu.edu/library/asset-view.cfm?AssetID=9661, (2010).
40.
Strode, D.E., Huff, S.L., Hope, B., Link, S.: Coordination in co-located agile software development projects. Journal of Systems and Software. 85, 1222–1238 (2012). https://doi.org/10.1016/j.jss.2012.02.017.
41.
Collins, G.: Agile Project Management. In: Project Management, Planning and Control. pp. 523–538. Elsevier (2017). https://doi.org/10.1016/B978-0-08-098324-0.15001-2.
42.
Lewis, J., Fowler, M.: Microservices, http://martinfowler.com/articles/microservices.html.
43.
Eklund, U., Arts, T.: A Classification of Value for Software Architecture Decisions. In: Babar, M.A. and Gorton, I. (eds.) Software Architecture. pp. 368–375. Springer Berlin Heidelberg, Berlin, Heidelberg (2010). https://doi.org/10.1007/978-3-642-15114-9_30.
44.
Brown, N., Nord, R.L., Ozkaya, I.: Enabling Agility Through Architecture, https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=28851, (2010).
45.
Finkelstein, A., Harman, M., Mansouri, S.A., Ren, J., Zhang, Y.: A search based approach to fairness analysis in requirement assignments to aid negotiation, mediation and decision making. Requirements Engineering. 14, 231–245 (2009). https://doi.org/10.1007/s00766-009-0075-y.
46.
October, 2014 - Insufficient data from Andrew Fryer - Site Home - TechNet Blogs, http://blogs.technet.com/b/andrew/archive/2014/10.aspx.
47.
NASA: Understanding Joint Confidence Level (JCL) at NASA, https://www.nasa.gov/pdf/724371main_76646-Risk_Analysis_Brochure-Final6.pdf.
48.
NASA: Appendix J - Joint Cost and Schedule Confidence level (JCL) Analysis. In: NASA Cost Estimating Handbook Version 4.0. p. J-1-45. National Aeronautics and Space Administration, Washington, D.C. (2015).
49.
Ashrov, A., Marron, A., Weiss, G., Wiener, G.: A use-case for behavioral programming: An architecture in JavaScript and Blockly for interactive applications with cross-cutting scenarios. Science of Computer Programming. 98, 268–292 (2015). https://doi.org/10.1016/j.scico.2014.01.017.
50.
UI in an Agile Process - The Quick ‘n’ Dirty Approach in the Real World, http://www.infoq.com/presentations/UI-in-an-Agile-Process.
51.
Lastminute.com energises product discovery and development, http://thoughtworks.fileburst.com/clients/lastminute-casestudy.pdf.
52.
U.S. Department of Health & Human Services: Personas, http://www.usability.gov/how-to-and-tools/methods/personas.html.
53.
Inclusive Design Toolkit Home, http://www.inclusivedesigntoolkit.com/betterdesign2/.