From AI Tools as is: The 12 Agile Principles explain how Agile teams should work in practice. Your slides group them as Principles 1–6 and 7–12: early delivery, welcoming change, frequent delivery, daily business/developer cooperation, …
Kanban cadences are the regular meetings or feedback loops used in Kanban to manage flow, improve delivery, and remove blockers. Kanban does not require fixed sprints like Scrum. Instead, work flows continuously, and cadences help …
From AI Tools/ChatGPT as is: Key idea Scrum has formal events.XP has practices/activities more than formal events.Kanban has cadences/meetings, not required sprints.Agile itself is an umbrella approach, so it does not prescribe one fixed set …
Reflection: Reflection in Agile means the team regularly looks back at how the work went and decides how to improve. In Scrum, the formal event for reflection is the Sprint Retrospective. Sprint Retrospective as one …
Story points are related to time, but they are not the same as time. A story point is a relative estimate of the size of a user story. It considers: Factor Meaning Effort How much …
The 12 Agile Principles explain how Agile teams should work in practice. Your slides group them as Principles 1–6 and 7–12: early delivery, welcoming change, frequent delivery, daily business/developer cooperation, motivated teams, face-to-face communication, working software as progress, sustainable pace, technical excellence, simplicity, self-organizing teams, and regular reflection/adaptation.
#
Agile Principle
Simple meaning for students
1
Customer satisfaction through early and continuous delivery
Deliver useful product pieces early and often so customers see value quickly.
2
Welcome changing requirements, even late in development
Agile accepts that needs may change; the team adjusts instead of resisting change.
3
Deliver working software frequently
Release usable increments often, usually in weeks rather than months.
4
Business people and developers work together daily
Product/business stakeholders should stay closely involved with the development team.
5
Build projects around motivated individuals
Give capable people support, trust, and ownership of the work.
6
Face-to-face conversation is the most effective communication
Direct conversation is usually faster and clearer than long documents or email chains.
7
Working software is the primary measure of progress
Real completed product matters more than reports, plans, or documents alone.
8
Sustainable development pace
Teams should work at a pace they can maintain over time without burnout.
9
Continuous attention to technical excellence and good design
Good design, clean code, testing, and quality practices make the team more Agile.
10
Simplicity — maximize the work not done
Do only the work needed to deliver value; avoid unnecessary features or complexity.
11
Self-organizing teams create the best results
Teams closest to the work should decide how to do the work.
12
Regular reflection and adaptation
Teams should regularly review how they work and improve their process.
A simple teaching line:
Agile is not just “work faster.” Agile means delivering value early, accepting change, collaborating closely, building quality, and improving continuously.
Kanban cadences are the regular meetings or feedback loops used in Kanban to manage flow, improve delivery, and remove blockers. Kanban does not require fixed sprints like Scrum. Instead, work flows continuously, and cadences help the team inspect and improve that flow.
Your slides describe Kanban using visual workflow, pull system, continuous flow, WIP limits, and continuous improvement.
Kanban cadence
Purpose
What the action looks like
Daily Kanban Meeting
Check flow, blockers, and WIP limits.
Team looks at the board, usually from right to left: Done → Review → In Progress → To Do. They ask: What is blocked? What can move forward? Are WIP limits exceeded?
Replenishment Meeting
Decide what work should enter the system next.
Team/Product Owner reviews the backlog and selects ready, high-priority items to move into “Ready” or “To Do.”
Delivery Planning Meeting
Decide when completed work will be released or delivered.
Team checks finished items and plans release timing, packaging, handoff, or customer delivery.
Service Delivery Review
Review how well the team is delivering value.
Team checks lead time, cycle time, throughput, quality, and customer satisfaction.
Operations Review
Review performance across teams/services.
Managers or multiple teams look at system-level issues, bottlenecks, capacity, and coordination problems.
Risk Review
Identify and manage delivery risks.
Team reviews blocked items, aging work, dependencies, recurring defects, or items stuck too long.
Strategy Review
Align Kanban work with business goals.
Leadership or product stakeholders check whether the work being delivered still supports organizational priorities.
Retrospective / Improvement Meeting
Improve the process.
Team discusses what to improve: WIP limits, policies, bottlenecks, handoffs, quality checks, or workflow design.
A simple explanation:
In Scrum, the team uses sprint events. In Kanban, the team uses cadences. These cadences are regular checkpoints that help the team manage continuous flow.
For students, you can say:
Kanban cadences are not about starting and ending a sprint. They are about keeping work moving smoothly through the board.
Example:
A team has many items stuck in Review. During the Daily Kanban Meeting, they notice the Review column is full. During the Service Delivery Review, they see cycle time is increasing. During the Retrospective, they decide to reduce new work and assign more people to help with reviews. That is how Kanban cadences support continuous improvement.
Scrum has formal events. XP has practices/activities more than formal events. Kanban has cadences/meetings, not required sprints. Agile itself is an umbrella approach, so it does not prescribe one fixed set of events.
Your Scrum slides identify the five Scrum events as Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Methodology
Event / Activity
What it means
What the action looks like
Scrum
Sprint
Fixed time-box where the team creates a usable product increment. Usually 1–4 weeks.
Team works on selected sprint backlog items and aims to meet the sprint goal.
Scrum
Sprint Planning
Meeting at the start of the sprint to decide what will be done and how.
Product Owner explains top backlog items; team selects work; team creates sprint goal and sprint backlog.
Scrum
Daily Scrum / Daily Standup
Short daily meeting to inspect progress and coordinate work.
Team discusses progress toward sprint goal, blockers, and next steps.
Scrum
Sprint Review
End-of-sprint meeting to inspect the product increment with stakeholders.
Team demonstrates completed work and gets feedback.
Scrum
Sprint Retrospective
End-of-sprint reflection meeting to improve team process.
Team discusses what went well, what did not, and what to improve next sprint.
XP events / practices
XP, or Extreme Programming, is Agile but more engineering-focused. It does not usually list “events” the same way Scrum does. It uses short iterations and technical practices.
XP practice / activity
What it means
What the action looks like
Iteration Planning
Team plans work for a short iteration, often 1–2 weeks.
Customer/Product Owner selects stories; team estimates and commits to work.
Small Releases
Deliver working software frequently.
Release a small, useful feature quickly instead of waiting for a large release.
Pair Programming
Two developers work together on the same code.
One writes code, the other reviews/thinks; they switch roles.
Test-Driven Development / TDD
Tests are written before code.
Write test → write code → pass test → refactor.
Continuous Integration
Code is integrated and tested frequently.
Developers commit code often; automated tests run regularly.
Refactoring
Improve internal code design without changing visible behavior.
Team asks questions and adjusts stories based on feedback.
Kanban events / cadences
Kanban does not require fixed sprint events. Kanban as visual workflow, pull system, continuous flow, WIP limits, and continuous improvement.
Kanban cadence / meeting
What it means
What the action looks like
Daily Kanban Meeting
Short meeting focused on flow, blockers, and WIP limits.
Team looks at the board from right to left: what is blocked, what can move to Done, what needs help?
Replenishment Meeting
Decides what new work should be pulled into the system.
Product Owner/team reviews backlog and selects ready items for To Do.
Delivery Planning Meeting
Plans when completed work can be released or delivered.
Team checks finished items and decides delivery timing.
Service Delivery Review
Reviews how well the team is delivering work.
Team checks lead time, cycle time, throughput, and customer satisfaction.
Operations Review
Looks at performance across teams or services.
Managers/teams review bottlenecks and system-level improvement needs.
Risk Review
Reviews blocked, delayed, or risky work items.
Team identifies recurring blockers and actions to reduce risk.
Retrospective / Improvement Meeting
Reflects on process improvement.
Team discusses how to improve flow, reduce bottlenecks, or adjust WIP limits.
Agile events
Agile itself does not define a fixed event list. Agile is a broad mindset based on values and principles such as customer collaboration, responding to change, frequent delivery, and team reflection. Agile as emphasizing flexibility, customer feedback, and iterative progress.
Team identifies lessons learned and improvement actions.
Backlog Refinement
Prepare future work.
Clarify user stories, split large items, add acceptance criteria.
Release / Delivery
Deliver usable value to users.
Deploy or hand over completed product increment.
Simple explanation
You can say:
Scrum has five formal events. XP has short iterations and engineering practices. Kanban has continuous flow and optional cadences. Agile is the umbrella, so events depend on the specific Agile framework being used.
Reflection in Agile means the team regularly looks back at how the work went and decides how to improve.
In Scrum, the formal event for reflection is the Sprint Retrospective. Sprint Retrospective as one of the five Scrum events, along with Sprint, Sprint Planning, Daily Scrum, and Sprint Review.
Simple definition
Term
Meaning
Reflection
Thinking back on recent work to learn what went well, what did not go well, and what should be improved.
Sprint Retrospective
A Scrum meeting held at the end of the sprint where the team reflects on process, teamwork, tools, communication, and improvement actions.
Adaptation
Changing the team’s approach based on what was learned from reflection.
Why do we need reflection?
Reflection helps the team improve continuously. It supports one of the Agile principles: teams should regularly reflect and adapt. Your slides mention “regular reflection and team adaptation” as part of the Agile principles.
It helps the team answer:
What worked well? What problems slowed us down? What should we change in the next sprint?
What the action looks like
At the end of a sprint, the team may hold a retrospective and discuss:
Question
Example student/team answer
What went well?
We completed most of the high-priority user stories.
What did not go well?
Some stories were unclear, so estimation was difficult.
What should we improve?
Add better acceptance criteria before sprint planning.
What action will we take next sprint?
Product Owner will clarify stories before estimation.
Story points are related to time, but they are not the same as time.
A story point is a relative estimate of the size of a user story. It considers:
Factor
Meaning
Effort
How much work may be required
Complexity
How difficult the work is
Uncertainty
How unclear or risky the work is
Dependencies
Whether the story depends on other people, teams, systems, or information
Your slides explain that story points are used for relative sizing and consider complexity, effort, uncertainty, and dependencies, while hours are better used for task breakdown inside a sprint.
Simple example
Story
Story points
Possible meaning
Add a button label change
1 point
Very small, low risk
Create login page
3 points
Moderate work
Build password reset with email verification
5 points
More effort and testing
Build recommendation engine
13 points
Large, complex, uncertain
A 5-point story does not always mean 5 hours. It means the team believes it is roughly bigger than a 3-point story and smaller than an 8-point story.
How story points connect to time
Story points become useful over multiple sprints through velocity.
Velocity = average story points completed per sprint.
For example:
Sprint
Completed story points
Sprint 1
22
Sprint 2
26
Sprint 3
24
Average velocity = about 24 story points per sprint.
So if the remaining backlog has 96 story points, the team may estimate:
96 ÷ 24 = 4 sprints
So story points help forecast time at the sprint/release level, not at the individual-hour level.
Explanation
You can say:
Story points are not hours. Story points are a relative measure of story size. After a team completes a few sprints, we can use their average velocity to estimate how many sprints are needed to finish the backlog.
Good classroom warning
Avoid saying:
1 story point = 1 hour
That is usually not correct.
Better:
For this team, based on past performance, 20 story points may usually fit into a 2-week sprint.
So the relationship is:
Story points → help calculate velocity → velocity helps forecast time.
Agile is a broad mindset, not one fixed process. Different Agile frameworks use different time-boxes.
Scrum
Sprint
Usually 1–4 weeks
Scrum uses a fixed-length sprint to plan, build, review, and improve. Your slides define a sprint as a time-boxed period of 1–4 weeks that creates a potentially shippable product increment.
XP / Extreme Programming
Iteration
Usually 1–2 weeks, sometimes up to 3 weeks
XP uses short iterations to support frequent feedback, continuous integration, testing, refactoring, and small releases.
Kanban
No sprint required
No fixed sprint length
Kanban is based on continuous flow. Work is pulled through the board as capacity becomes available, rather than being planned into fixed sprints. Your slides describe Kanban as continuous flow with no fixed iterations.
Simple explanation
A sprint is a fixed time-box used mainly in Scrum. For example, a team may choose a 2-week sprint. At the beginning, they plan the work. During the sprint, they execute and track progress. At the end, they review the completed increment and hold a retrospective.
In XP, the idea is similar, but the term iteration is more common. XP iterations are usually short because XP emphasizes quick feedback, frequent releases, testing, and continuous improvement.
In Kanban, there is normally no sprint length because work flows continuously. Instead of saying, “What can we finish in the next two weeks?”, a Kanban team asks, “What is the next highest-priority item we can pull now, based on available capacity and WIP limits?”
For students, you can say:
Scrum works in fixed sprints. XP works in short iterations. Kanban works in continuous flow. Agile is the umbrella concept that can include all of these approaches.
WIP Limits:
WIP limits means Work-In-Progress limits.
In Kanban, a WIP limit sets the maximum number of work items allowed in one workflow stage at the same time. For example, a team may decide that only 3 user stories can be in In Progress at once. Your slides define WIP limits as a constraint-based approach used to optimize flow and prevent overloading the team.
Term
Meaning
WIP
Work currently started but not yet finished
WIP Limit
Maximum number of items allowed in a stage
Purpose
Prevent too much work from being started at once
Benefit
Helps reveal bottlenecks and improves delivery speed
Common Kanban columns
Backlog → To Do → In Progress → Review/Testing → Done
Example:
Kanban Column
WIP Limit
Meaning
To Do
No limit
Work waiting to be started
In Progress
3
Only 3 items can be actively worked on
Review / Testing
2
Only 2 items can wait for review/testing
Done
No limit
Completed work
Simple explanation:
WIP limits stop the team from starting too many things at the same time. Instead of everyone beginning new tasks, the team focuses on finishing existing work first.
What the action looks like:
A team has 3 stories already in In Progress, and the WIP limit is 3. A developer cannot pull another story into In Progress until one of the current stories moves to Review or Done.
This helps the team ask:
“Why is work stuck here?” “Do we need to help finish current work before starting new work?” “Is testing or review becoming a bottleneck?”
In Jira or a Kanban board, WIP limits usually appear as a number on top of a column, such as:
In Progress 3/3
That means the column is full. The team should finish or move existing work before starting more.
Windows 11 host: 192.168.55.1
DC01: 192.168.55.10
MEM01: 192.168.55.21
Also make sure no other VM is running with 192.168.55.20. The duplicate message usually means another machine already has that IP, or the clone/network adapter still has a conflict.
Quiz: Root Access, Boot Process, File Systems, Partitions, and Mounting
1. True/False
The root user is the superuser account and has the highest access rights on a Linux system.
Answer: True
2. True/False
It is recommended to stay logged in as root for normal daily work because it is faster.
Answer: False Explanation: Staying logged in as root is risky because mistakes may affect the entire system.
3. Multiple Choice
Which command is preferred when you need to run one privileged command?
A. su - B. sudo command C. exit D. whoami
Answer: B. sudo command
4. Multiple Choice
What does the command below do?
su -
A. Runs one command as root B. Opens a login shell as root C. Shows the current user D. Lists mounted filesystems
Answer: B. Opens a login shell as root
5. Multiple Choice
Which process is usually started by the kernel as the first userspace process?
A. GRUB B. BIOS C. systemd or init D. fdisk
Answer: C. systemd or init
6. Multiple Choice
Which systemd target usually represents a non-graphical multi-user system?
A. poweroff.target B. rescue.target C. multi-user.target D. graphical.target
Answer: C. multi-user.target
7. Multi-Select
Which of the following are risks of using the root account directly?
Select all that apply.
A. Accidental system-wide file changes B. Running ordinary tasks with unnecessary privileges C. Forgetting that you are logged in as root D. More accountability than sudo E. Background processes may run with root privilege
Answers: A, B, C, E
8. Multi-Select
Which commands are commonly part of the basic partition, format, mount, and verify workflow?
Select all that apply.
A. lsblk B. fdisk C. mkfs D. mount E. df -h F. passwd
Answers: A, B, C, D, E
9. Multi-Select
Which statements about filesystems are correct?
Select all that apply.
A. A filesystem organizes data and metadata on storage B. Journaling can reduce recovery time after an unclean shutdown C. ext4 is commonly used on many Linux distributions D. FAT is a modern Linux-native journaling filesystem E. NTFS is associated with Microsoft Windows
Answers: A, B, C, E
10. Fill in the Blank with Choices
A filesystem defines how __________ and metadata are organized and accessed on a storage device.
A. users B. data C. passwords D. targets
Answer: B. data
11. Fill in the Blank with Choices
The Linux filesystem table is stored in the file __________.
A. /etc/passwd B. /etc/fstab C. /boot/grub D. /var/log
Answer: B. /etc/fstab
12. Fill in the Blank with Choices
On modern systems, __________ is normally preferred over MBR for large disks unless compatibility requires MBR.
A. FAT B. GPT C. ext2 D. BIOS
Answer: B. GPT
13. Matching
Match each FHS directory with its purpose.
Directory
Purpose
1. /etc
A. User home directories
2. /var
B. Device files
3. /home
C. System-wide configuration files
4. /dev
D. Logs and changing data
5. /boot
E. Boot loader files and kernels
Answer:
Directory
Correct Purpose
/etc
C
/var
D
/home
A
/dev
B
/boot
E
14. Matching
Match each command with its purpose.
Command
Purpose
1. lsblk
A. Format a partition with a filesystem
2. fdisk
B. Show block devices
3. mkfs
C. Modify partition tables
4. mount
D. Attach a filesystem to the Linux directory tree
5. umount
E. Detach a mounted filesystem
Answer:
Command
Correct Purpose
lsblk
B
fdisk
C
mkfs
A
mount
D
umount
E
15. Ordering
Put the boot stages in the correct order.
A. Kernel starts init/systemd B. BIOS/UEFI starts C. GRUB loads the selected kernel D. System reaches target/services E. MBR or boot loader code begins the boot manager stage
Correct Order:
B
E
C
A
D
16. Ordering
Put the storage setup steps in the correct order.
A. Format the partition with mkfs B. Identify the disk with lsblk C. Mount the filesystem D. Create a partition using fdisk E. Verify using df -h
Correct Order:
B
D
A
C
E
17. Short Answer
Explain the difference between sudo and su -.
Sample Answer: sudo runs a single command with elevated privileges and logs the action. su - opens a new login shell as another user, usually root if no username is provided. sudo is safer for one administrative task, while su - is used when a full shell as another user is needed.
18. Hands-on Short Answer
Write commands to format /dev/sdb1 as ext4, create /mnt/test, mount the partition, and verify it.
Why is /dev/sdb commonly used with fdisk, but /dev/sdb1 is commonly used with mkfs?
Sample Answer: /dev/sdb represents the whole disk, so fdisk uses it to create or modify the disk’s partition table. /dev/sdb1 represents a specific partition, so mkfs formats that partition with a filesystem.
20. Higher-Order Short Answer
A server should automatically mount a new ext4 partition after every reboot. Which file should be configured, and what information does it need?
Sample Answer: The file /etc/fstab should be configured. It needs the filesystem or UUID, mount point, filesystem type, mount options, dump value, and filesystem check pass value. Example pattern:
UUID=... /mnt/data ext4 defaults 0 2
This allows the system to mount the filesystem automatically during boot.
Users can create files, but they cannot delete other users’ files.
Final Blog Summary
SUID: Run an executable as the file owner.
SGID: Run an executable as the file group, or make files inherit a directory group.
Sticky Bit: In shared directories, users can delete only their own files.
The lowercase letters mean the related execute permission is present:
s = SUID/SGID + execute
t = Sticky Bit + execute
The uppercase letters mean the special permission is set, but execute is missing:
S = SUID/SGID set, execute missing
T = Sticky Bit set, execute missing
For practical use, lowercase s and t are usually what you expect to see. Uppercase S or T often indicates a permission setup that should be reviewed.
From AI Tools/ChatGPT as is: Key idea Scrum has formal events.XP has practices/activities more than formal events.Kanban has cadences/meetings, not ...