Week 1

2.1 Understand the values of agile methodologies and work practices

Agile methodologies are based on the Agile Manifesto, which was introduced in 2001. The core philosophy of Agile focuses on adaptability, collaboration, and the continuous delivery of working products. Agile is built around four key values:

Individuals and interactions over processes and tools.

Agile places importance on the people involved in a project. It is the individuals within an organisation who respond to business needs, solve problems, and drive the development process. Tools and processes can support the work, but they should not control it. Over-reliance on tools can limit flexibility and reduce the team’s ability to respond to change.

Working software over comprehensive documentation.

Agile focuses on producing a working product rather than spending too much time creating detailed documentation. This does not mean documentation is unimportant. Documentation can still have value for an organisation, but it should support the development process rather than become the main priority. The main aim is to deliver software that works and meets user needs.

Customer collaboration over contract negotiation.

Customer involvement is a key part of Agile project management. In traditional project management approaches, the customer’s requirements are often agreed before the project begins and may be difficult to change later. In Agile, the customer is treated as an important part of the development process. Their feedback is used throughout the project to help shape and improve the final product.

Responding to change over following a plan.

Agile projects are completed in short development cycles, often called iterations or sprints. This allows changes to be introduced quickly and more cost-effectively. Being able to respond to change is seen as a strength because it helps the team improve the product and better meet the needs of the customer.

Investigating the Agile Manifesto
Activity title: Agile Values in Action
Group size: 3–4 learners
Time: 45–60 minutes
Outcome: Learners investigate one Agile value and present how it could be applied in a real project.

Task Overview
Each group will investigate one of the four Agile values. They will explain what the value means, why it is important, and how it could be used in a project such as developing a website, mobile app, booking system, or school/college digital service.

Group Investigation Tasks
Each group should research and prepare answers to the following:
1 - What does the Agile value mean?
Explain it in simple terms.
2 - Why is this value important in project management?
Explain how it helps a development team.
3 - How is this different from a traditional project approach?
Compare Agile with a more fixed or planned approach.
4 - Example scenario
Give an example of how this value could be used in a real project.
5 - Benefits and possible problems
Identify at least two benefits and one possible challenge of using this Agile value.

Presentation Requirements

Each group should create a short presentation lasting 3–5 minutes.
The presentation should include:
Slide 1 - Title and Group Members
Slide 2 - The Agile Value being investigated
Slide 3 - Explaination of what the value means
Slide 4 - Example of the value being used in a project
Slide 5 - Benefit and possible Challenges

Suggested Presentation Roles
Each learner should take on a role:
Researcher - Finds key information about the Agile value
Scenario Designer - Creates a real-world example
Slide Designer - Creates the presentation slides
Presenter - Leads the spoken presentation

Example Project Scenarios
Groups may choose one of these:
College app - An app to help students check timetables and assignments
Online shop - A website for customers to buy products
Booking system - A system for booking appointments or rooms
Revision website - A website that gives students quizzes and revision resources

Extension Task
After all presentations, learners should answer this question individually:
Which Agile value do you think is the most important when developing a digital product? Explain your answer using an example.

2.2 Understand the applications of agile methodologies and work practices in support of continuous innovation and development in a digital environment

Scrum:

Scrum is one of the most widely used Agile frameworks. It provides a structured way for teams to organise work, manage progress, and deliver improvements in short cycles. Scrum is often used in software development, website development, app creation, digital transformation projects, and other technology-based environments.

Scrum supports continuous development because it breaks large projects into smaller, manageable sections. These sections are completed during short time periods called sprints. At the end of each sprint, the team should have produced a usable improvement or working part of the product.

Defined Roles

Scrum usually includes three main roles:

Product Owner
The Product Owner represents the needs of the customer, user, or organisation. They decide what features are most important and manage the product backlog. Their role is to make sure the team is working on tasks that provide the most value.

Scrum Master
The Scrum Master supports the team by helping them follow Scrum practices. They remove barriers, support communication, and make sure the team can work effectively. The Scrum Master does not usually manage the team in a traditional way; instead, they act as a facilitator.

Development Team
The Development Team is responsible for creating the product. This may include developers, designers, testers, analysts, or other technical specialists. The team works together to complete the tasks agreed for each sprint.

Scrum Events

Scrum includes regular events to organise work and review progress:

Sprint Planning
This happens at the start of a sprint. The team agrees what work will be completed during the sprint and how it will be achieved.

Daily Scrum
This is a short daily meeting where the team discusses progress, problems, and plans for the next stage of work.

Sprint Review
This happens at the end of the sprint. The team demonstrates what has been completed and receives feedback from stakeholders.

Sprint Retrospective
This is used to reflect on how the team worked during the sprint. The team discusses what went well, what could be improved, and what changes should be made for the next sprint.

Scrum Artefacts

Scrum uses artefacts to make work visible and organised:

Product Backlog
This is a prioritised list of features, requirements, fixes, or improvements needed for the product.

Sprint Backlog
This is the set of tasks selected from the product backlog to be completed during the current sprint.

Increment
The increment is the completed and usable work produced during a sprint. It should add value to the product.

Scrum Rules

Scrum rules help the team work consistently. These rules include working in fixed-length sprints, keeping tasks visible, reviewing progress regularly, and making sure completed work meets an agreed standard. The team should also use feedback to improve both the product and their working practices.

Applying Daily Scrums

Daily scrums are short meetings, usually lasting around 15 minutes. They are used to help the team stay organised and aware of progress. During a daily scrum, team members usually discuss what they completed recently, what they plan to work on next, and whether there are any problems blocking their progress.

Daily scrums support continuous development because issues can be identified early. For example, if a developer is struggling with a login feature, the team can quickly offer support or adjust the workload before the problem delays the whole project.

Daily scrums also improve communication. In digital projects, different team members may be working on coding, testing, design, security, documentation, or user feedback. Regular communication helps make sure everyone understands what is happening and how their work connects to the wider project.

Breaking Workloads Down into Sprints

In Scrum, large workloads are broken down into smaller sections called sprints. A sprint is a short, fixed period of work, often lasting between one and four weeks. During each sprint, the team focuses on completing a specific set of tasks from the sprint backlog.

Breaking work into sprints makes digital development easier to manage. Instead of trying to deliver a complete system all at once, the team can focus on smaller improvements. This reduces complexity and allows progress to be reviewed more regularly.

For example, if a team is developing an online booking system, the work could be split into several sprints:

• Sprint 1: Create user login and account registration
• Sprint 2: Build the booking calendar
• Sprint 3: Add email confirmations
• Sprint 4: Test security, fix errors, and improve the user interface

This approach supports continuous innovation because each sprint creates an opportunity to test, gather feedback, and improve the product. If user needs change, the team can adjust future sprints rather than having to restart the whole project.

Overall, Scrum supports Agile working by giving teams a clear structure while still allowing flexibility. It helps teams manage workloads, communicate regularly, respond to feedback, and deliver ongoing improvements in a digital environment.

Kanban

Manages workloads by balancing demands with available capacity

Kanban is an Agile work practice used to manage tasks by making work visible and controlling how much work is being completed at one time. In digital support services and security, teams often receive a constant flow of tasks, such as support tickets, password resets, software updates, incident reports, security alerts, and system maintenance requests.

Kanban helps teams balance demand with the capacity they have available. This means the team only takes on a realistic amount of work based on the number of staff, their skills, the urgency of the tasks, and the time available. For example, if a digital support team has several staff absent, Kanban can help prevent too many tickets from being started at once. Instead, the team can prioritise the most important work, such as restoring access to critical systems or responding to a possible security breach.

In a security context, balancing workload is important because some tasks are higher risk than others. A malware alert or failed backup may need to be prioritised over a routine software request. Kanban supports this by allowing teams to see all tasks clearly and decide which work should be completed first.

Identifies bottlenecks in workload

A bottleneck happens when work builds up at a certain stage and slows down the overall process. Kanban helps teams identify bottlenecks because tasks are displayed visually on a board. If too many tasks are sitting in one column, it shows that part of the process may need attention.

For example, in a digital support team, lots of tickets may build up in a “Waiting for Technician” or “Testing” column. This could show that there are not enough staff available, that tasks are too complex, or that users are not providing the information needed to resolve the issue.

In a cyber security team, bottlenecks may occur during incident investigation, vulnerability patching, or approval stages. For example, if several security updates are waiting for testing before deployment, this creates a risk because systems may remain vulnerable for longer. Kanban helps the team spot this issue quickly and take action, such as assigning more staff, simplifying the approval process, or escalating urgent security tasks.

Identifying bottlenecks improves service quality because users receive faster support and security issues are less likely to be delayed.

Manages work using a Kanban board

A Kanban board is a visual tool used to track work as it moves through different stages. It usually contains columns such as:

• To Do
• In Progress
• Waiting
• Testing
• Complete

Each task is represented by a card. The card may include the task name, priority, deadline, person responsible, and any important notes.

In digital support services, a Kanban board could be used to manage support tickets. For example, a ticket about a printer fault may start in “To Do”, move to “In Progress” when a technician begins work, move to “Testing” when the fix is checked, and finally move to “Complete” once the user confirms the issue is resolved.

In security, a Kanban board could be used to manage tasks such as vulnerability scanning, patch deployment, user access reviews, phishing investigations, firewall rule changes, and backup checks. This makes it easier for the team to understand what work is active, what is urgent, and what has already been completed.

Kanban boards also support communication. Managers, technicians, analysts, and stakeholders can quickly see the status of work without needing constant meetings or email updates.

Uses work in progress (WIP) limits to prevent over-commitment.

Work in progress, often shortened to WIP, means the amount of work currently being completed. Kanban uses WIP limits to control how many tasks can be active at one time. This prevents teams from starting too many tasks before finishing existing ones.

For example, a digital support team may set a WIP limit of five tasks in the “In Progress” column. This means that only five tasks can be actively worked on at once. If the limit has been reached, the team must complete or move an existing task before starting a new one.

This is useful because too much active work can lead to mistakes, delays, poor communication, and unfinished tasks. In digital support, this could mean users waiting longer for issues to be resolved. In security, it could mean important tasks such as patching, malware investigation, or access control reviews being delayed.

WIP limits help teams focus on finishing work rather than simply starting new tasks. This improves efficiency and reduces the risk of over-commitment. In security-related work, it also supports safer practice because analysts and technicians are less likely to rush or miss important details when investigating threats or applying fixes.

Overall, Kanban supports digital support services and security by making work visible, helping teams prioritise tasks, reducing delays, and ensuring that workloads remain manageable.

Dynamic systems development method (DSDM)

Fixed cost, quality and time

Uses MoSCoW in the prioritisation of scope.

which dictates whether features Must, Should, Could, or Won't be delivered within a given timeframe. This means if time runs tight, the least valuable features are dropped first to preserve deadlines and quality

Feature-driven development:

o breaks down development into smaller features

o plans, designs and builds by feature.

Crystal:

o focuses on communications and interactions between people over

processes and tools.

Lean (7 principles)

o eliminate waste

o build in quality

o create knowledge

o defer commitment

o deliver fast

o respect people

o optimise the whole.

Extreme programming (XP)

o advocates frequent releases in short development cycles

o introduces check points when new customer requirements can be adopted

o uses planning and feedback loops.

Last Updated
2026-07-13 10:01:43