3/10/2025

SIT309 AGILE TEST DRIVEN S/W DEVELOPMENT

Lecture 8b
Scrum Software Development Framework
• Scrum is an Agile framework for managing and completing
complex projects. Originally designed for software
development, it is now widely used across many industries
for project management. Scrum is a highly structured
framework that emphasizes collaboration, flexibility, and
incremental progress through iterative cycles called Sprints.

• Key Principles of Scrum

• Transparency: All aspects of the project are visible to all
stakeholders.
Agile - Scrum Framework • Inspection: Regular assessment of progress to identify any
issues or improvements.
• Adaptation: Adjustments are made based on feedback and
By Mbogo Njoroge
the results of inspections.

1 2

Artifacts in Scrum
Roles in Scrum
There are three key artifacts that help manage the product development
There are three main roles in Scrum: process:
• Product Owner (PO): • Product Backlog:
• Represents the stakeholders and is responsible for ensuring the product • A list of features, improvements, and bug fixes that are needed for
meets business needs. the product.
• Prioritizes the product backlog and makes decisions about features. • Managed by the Product Owner and is continuously updated and
• Defines the Product Vision and goals. prioritized.
• Makes trade-offs between features, resources, and time. • The backlog is dynamic and evolves as new requirements emerge.
• Scrum Master: • Sprint Backlog:
• Facilitates the Scrum process and helps the team stay organized and • A subset of the Product Backlog that the team commits to complete
productive. during a Sprint.
• Removes any impediments or blockers that may hinder the team's progress. • Created during the Sprint Planning meeting.
• Acts as a liaison between the development team and the Product Owner. • The Development Team defines how to accomplish the work in the
• Ensures the team follows Scrum principles and practices. Sprint.
• Development Team: • Increment:
• A self-organizing group of professionals responsible for building the product. • The working product delivered at the end of each Sprint.
• Cross-functional team members (designers, developers, testers, etc.). • Must meet the Definition of Done (DoD) set by the team.
• Works collaboratively to achieve the goals set for each Sprint. • Represents the sum of all completed Product Backlog items during
• Delivers the increment of the product at the end of each Sprint. 3 the Sprint. 4

Scrum Events (Ceremonies) • Sprint Review:

There are five events in Scrum, and each has a specific purpose: • Held at the end of each Sprint to demonstrate the
• Sprint: completed increment.
• A time-boxed period (typically 2–4 weeks) during which a set of tasks (from • The team presents the work done, and stakeholders
the Sprint Backlog) is completed.
provide feedback.
• The Sprint begins with a Sprint Planning meeting and ends with a Sprint
Review and Sprint Retrospective. • The Product Owner discusses the progress on the
• Sprint Planning: product and adjusts the Product Backlog as needed.
• Held at the start of each Sprint to determine what can be delivered during the • Sprint Retrospective:
Sprint and how that work will be achieved.
• Involves the Product Owner, Scrum Master, and Development Team. • Held after the Sprint Review to reflect on the Sprint.
• Daily Scrum (Standup): • The team discusses what went well, what didn’t, and
• A short, 15-minute meeting held every day to inspect progress and adapt the how they can improve in the next Sprint.
plan for the day. • Focuses on continuous improvement and team
• Team members answer three questions: collaboration.
• What did you do yesterday?
• What will you do today?
• Are there any blockers or impediments?
• Helps ensure alignment and identify any issues early.
5 6

1
 3/10/2025

The Scrum Process Flow The Scrum Framework Process Flow

1. Product Backlog Creation:
• The Product Owner creates the Product Backlog, which is a prioritized list of
features, bugs, and other tasks.
2. Sprint Planning:
• During the Sprint Planning meeting, the Scrum Team selects Product Backlog
items to work on during the Sprint.
• These items are moved into the Sprint Backlog.
3. Sprint Execution:
• The Development Team works on the tasks from the Sprint Backlog, using the
Daily Scrum to ensure alignment and remove blockers.
• The team develops, tests, and delivers the product increment.
4. Sprint Review:
• The team demonstrates the increment to the Product Owner and stakeholders.
Feedback is collected, and the Product Backlog is adjusted as needed.
5. Sprint Retrospective:
• The team reviews the process and identifies ways to improve.
6. Repeat:
• A new Sprint begins, with the Product Backlog updated and the team focusing
on the next set of tasks.

7 8

1. Initial Setup: Scrum Roles

• Kumbuka, in Scrum, there are three key roles:
Getting Closer to Scrum Reality
• Product Owner: a representative of the client, responsible
for defining and prioritizing the features of the banking
application. The Product Owner ensures the development
A detailed Scenario for You to Understand Scrum in team works on the most important tasks that provide the
Software Development most value to the client. Let's assume the Product Owner is
Halima.
Scenario Overview: • Scrum Master: facilitates the Scrum process by ensuring
that the team is following Scrum practices, helps remove
• Imagine you are part of a software development team any obstacles, and ensures smooth communication between
working on a new online banking application for a the Product Owner and the team. In this case, the Scrum
client. The client wants a system that allows customers Master is Njeru.
to manage their accounts, check balances, transfer • Development Team: consists of developers, testers, and
money, and receive notifications. designers who are responsible for building the product. The
• Your task is to work with your team to develop this team is cross-functional, meaning they can perform all the
necessary tasks to complete the work. In this scenario, the
application using the Scrum framework, and this team includes four members: Sarah, a backend developer;
scenario will guide you step by step through each stage Makena, a frontend developer; Nduku, a UI/UX designer;
of the Scrum process. and Ruto, a tester.

9 10

2. Create the Product Backlog 3. Sprint Planning

• The Scrum process begins with Sprint Planning. A Sprint is a time-boxed
• At the start of the project, the Product Owner (Halima) works with period (typically 2–4 weeks) during which the team works on a subset of the
the Development Team to create the Product Backlog. The Product Product Backlog.
Backlog is a list of all the features, enhancements, bug fixes, and • At the Sprint Planning meeting:
technical tasks that need to be done for the banking application. The • Halima (Product Owner) explains the highest priority features.
Product Backlog is prioritized by the Product Owner based on • The Development Team (Sarah, Makena, Nduku, and Ruto) selects the
business value. Here's a sample Product Backlog for this project: items they believe they can complete during the Sprint.
• Together, they break down each selected item into smaller, actionable
tasks and define how they will complete each one.
ID User Story / Task Priority
P1 As a user, I want to log in to my account securely. High • For example, during this Sprint Planning, the team selects the following tasks:
• P1: Login feature (high priority).
P2 As a user, I want to view my account balance. High • P2: View account balance (high priority).
• P3: Money transfer feature (high priority).
P3 As a user, I want to transfer money to another account. High Each feature is divided into smaller tasks:
P4 As a user, I want to receive email notifications for transfers. Medium • P1:
• Task 1: Design login screen (Nduku)
P5 As a user, I want to change my password. Medium • Task 2: Implement backend login functionality (Sarah)
• Task 3: Write unit tests for login functionality (Ruto)
P6 As an admin, I want to view user account activity. Low • P2:
• Task 1: Design account balance UI (Nduku)
NB: The Product Owner continually updates this backlog as new requirements emerge, • Task 2: Implement account balance retrieval logic (Makena)
and as features are completed, they are marked as "done." 11 • Task 3: Write unit tests for account balance feature (Ruto) 12

2
 3/10/2025

4. Sprint Execution (Development)

• Once the Sprint starts, the team works together on the tasks 5. Sprint Review
defined in the Sprint Backlog. The team holds a Daily Scrum • At the end of the Sprint, the team holds a Sprint
(Daily Standup) to discuss their progress:
Review. During the Sprint Review:
• Each member answers the following three questions:
1) What did I do yesterday? • The Development Team demonstrates the
2) What will I do today? completed work to the Product Owner and
3) Are there any blockers or impediments? stakeholders.
• For example, on the first day, Sarah (backend developer) might • Halima (Product Owner) reviews the work done and
say: provides feedback.
• Yesterday, I worked on the login API.
• Today, I will continue to work on integrating the API with the
• For instance, the team shows the login feature and
frontend. the account balance view, both of which are
• I need help from Makena with the frontend integration. working as expected. The money transfer feature
• If any blockers arise (such as the need for clarification or might still be in progress, but the team is on track.
dependencies), the Scrum Master (Njeru) will help remove • The Product Backlog is then updated to reflect any new
those blockers by facilitating communication or resolving issues. insights, bugs, or features needed based on stakeholder
• The Development Team works collaboratively to implement the feedback.
features, continuously testing and refining them. They update
the Sprint Backlog to reflect progress.
13 14

• 7. Repeat the Cycle

6. Sprint Retrospective
• The next Sprint begins, and the team selects the next set of tasks from
• After the Sprint Review, the team holds a Sprint the Product Backlog based on priority and feasibility.
Retrospective. This meeting is a chance for the team to • For example, in the next Sprint, the team may focus on completing the
reflect on the Sprint and identify ways to improve. money transfer feature (P3), implementing email notifications (P4), and
working on security improvements for user accounts (P5).
• During the Retrospective: • This process repeats, with each Sprint resulting in the delivery of a
• The team discusses what went well, what didn’t go well, and how working increment of the banking application.
they can improve in the next Sprint.
• For example, the team may discuss:
• What went well?: The team worked well together, and the login Final Deliverable
feature was completed on time. • After several Sprints, the Development Team completes the key
• What didn’t go well?: The integration between the frontend and features of the banking application. These features include:
backend was slower than expected because of a • Login functionality.
miscommunication. • Viewing account balances.
• Improvements for next Sprint: The team agrees to have more • Transferring money.
frequent touchpoints between the backend and frontend
developers to ensure better integration. • Email notifications for transfers.
• The Scrum Master (Njeru) ensures that the team takes • The Product Owner (Halima) now works with stakeholders to
ensure the product meets all requirements. The team may
actionable steps to improve their process. continue to develop additional features, fix bugs, and enhance
the product over subsequent Sprints.
15 16

Benefits of Scrum Framework Scrum Challenges

i. Flexibility and Adaptability: i. Scope Creep:
• Scrum allows for quick adjustments and changes, making it ideal for • Without strong Product Backlog management, features can be
projects with evolving requirements. added during Sprints, leading to scope creep and delays.
ii. Increased Transparency: ii. Team Dependency:
• All stakeholders have visibility into progress and obstacles.
• Scrum is most effective when the team is cross-functional and self-
iii. Collaboration: organizing. Lack of skill diversity or external dependencies can be
• Scrum promotes communication among team members and problematic.
stakeholders, enhancing collaboration and team morale.
iii. Overwhelming for Large Teams:
iv. Early and Frequent Delivery: • Scrum can become difficult to manage with larger teams, requiring
• Scrum delivers usable increments early and frequently, allowing coordination, potentially leading to communication breakdowns.
stakeholders to see and use the product regularly.
v. Continuous Improvement: iv. Requires Experienced Product Owner:
• The Sprint Retrospective focuses on process improvement, which • If the Product Owner is not experienced in managing the backlog
helps the team become more efficient over time. and prioritizing effectively, the project can lose focus or direction.

17 18