Agile Software Pipelines

COMP33312 Agile Software Pipelines 10 Semester 2 Undergraduate Level 3 Suzanne Embury Unit coordinator 1 FHEQ level (Framework for Higher Education Qualifications) ' Last part of a Bachelors ' European Credit Transfer & Accumulation System Rating : 5.0 The approach to software development known as “agile software engineering” is now well established within the industry as the most reliable and cost-effective in all but a handful of rarely occurring circumstances.  Agile approaches emphasise the early and frequent delivery of releasable software artefacts to the client, combined with disciplined but flexible approaches to project progress tracking, to the continuous and active collection of feedback on the success (or otherwise) of the work done so far and to the creation of high-quality code bases that are easy and safe to change.  In an agile project, the first usable executable artefacts will be created very early in the project’s lifetime and may be in active use while other parts of the required functionality are still in various stages of development.  New and changed functionality is delivered incrementally at short intervals throughout the duration of the project, blurring the distinction between the development and the operational project phases. While the human processes used to manage and carry out agile software engineering are highly iterative, the artefacts produced by the processes are increasingly viewed as passing through one or more linear “pipelines”, on their journey to deployment and use in the end-user environment.  New models for the delivery of software (such as continuous delivery) depend upon a carefully configured technical pipeline as much as they do upon effective and efficient human design and feedback processes. In this course unit, we will examine how the combination of these iterative human processes and technical development and delivery pipelines is used to create software that provides real value and return on investment for clients and end-users, while also being of sufficiently high quality to allow frequent and sometimes substantial changes throughout the software’s lifetime. The approach to software development known as “agile software engineering” is now well established within the industry as the most reliable and cost-effective in all but a handful of rarely occurring circumstances.  Agile approaches emphasise the early and frequent delivery of releasable software artefacts to the client, combined with disciplined but flexible approaches to project progress tracking, to the continuous and active collection of feedback on the success (or otherwise) of the work done so far and to the creation of high-quality code bases that are easy and safe to change.  In an agile project, the first usable executable artefacts will be created very early in the project’s lifetime and may be in active use while other parts of the required functionality are still in various stages of development.  New and changed functionality is delivered incrementally at short intervals throughout the duration of the project, blurring the distinction between the development and the operational project phases. While the human processes used to manage and carry out agile software engineering are highly iterative, the artefacts produced by the processes are increasingly viewed as passing through one or more linear “pipelines”, on their journey to deployment and use in the end-user environment.  New models for the delivery of software (such as continuous delivery) depend upon a carefully configured technical pipeline as much as they do upon effective and efficient human design and feedback processes. In this course unit, we will examine how the combination of these iterative human processes and technical development and delivery pipelines is used to create software that provides real value and return on investment for clients and end-users, while also being of sufficiently high quality to allow frequent and sometimes substantial changes throughout the software’s lifetime. The unit aims to: Provide you with a working understanding of software pipelines, their use in the development, delivering and operation of software systems, and the iterative and incremental human processes through which they are managed. <ul> <li>Explain how agile approaches to software development compare with earlier “big up-front” approaches, and how modern software development pipelines complement the iterative, agile approach to delivering value to clients and users in a predictable way.</li> <li>Select and apply a variety of agile practices for planning and tracking progress on software projects, and for coordinating the movement of the developed artefacts through software pipelines, to maximise the value delivered by the resulting software and the return on investment for the client.</li> <li>Explain the vital role of feedback in the management of agile projects. Select and apply a variety of feedback-oriented practices (such as peer review and retrospectives) to identify and correct problematics aspects of team behaviour.</li> <li>Select and apply a variety of practices for the management of software quality in agile software projects, with particular emphasis on the key role of software testing pipelines in managing the complexity of modern projects.</li> <li>Explain the concept of DevOps and its role in agile software projects. Design simple software delivery and management pipelines that ensure the long-term generation of value to the clients and users of the systems created by the projects.</li></ul> Learning and teaching processes will be tailored to the specific topics being covered each week, and will consist of a mixture of: Workshops allowing discussion of and practice in applying key ideas. Face-to-face and online interactive group activities, including (where feasible) the use of coaching games used in industry for teaching agile development. Online reading material, case studies and videos. Self-paced TA supported working exercises (to be carried out synchronously or asynchronously as appropriate to the topic being taught).   1 Written exam 100% Assessment Task: Examination    Length: 2 hours  How and when feedback is provided: Through post-exam feedback sessions  Assessment Task: Self-tests  Length: 2.5 hours  How and when feedback is provided: Automatically on demand through Blackboard  Assessment Task: Group activities  Length: 2.5 hours  How and when feedback is provided: Group discussion and staff feedback when the activity is performed  COMP23311 Software Engineering 1 Pre-Requisite Compulsory COMP23412 Software Engineering 2 Pre-Requisite Compulsory COMP33312 pre-requisites are COMP23311 and COMP23412 N Assessment written exam 2 Practical classes & workshops 22 0 76