Slide 2
Last lecture in one minute
Waterfall
Incremental
Reuse
Spiral
Plan everything, then follow the plan
Build and deliver in small pieces
Integrate and configure what exists
Deal with the biggest risk first
Change: expensive
Change: cheap
Change: limited
Change: planned for
Plan-driven
Agile
Waterfall
V-model
Spiral
Incremental
Scrum, XP
Today: we stand at the agile end of the line. What does "agile" really mean, where did it come from, and when is it the right choice?
SE Lecture 3
Recap
Sheet 02 of 20
Slide 3
By the end of today, you will be able to
Explain why agile methods appeared
State the four values of the Agile Manifesto, with examples
Explain the twelve agile principles in simple words
Explain agility and how it changes the cost of change
Describe an agile process and the people it needs
Decide when agile fits a project, and give reasons
SE Lecture 3
Objectives
Sheet 03 of 20
Slide 4
Today's plan: 60 minutes
0-6 min
Welcome, recap, objectives
Coming up
6-10 min
Why agile was born
10-18 min
The Agile Manifesto: four values
- Lecture 4: XP
- Lecture 5: Scrum
- Lecture 6: Kanban and other agile models
- Practical 2 this week: a Scrum board in Trello
18-26 min
The twelve principles, quick check
26-33 min
Agility and the cost of change
33-40 min
The agile process and the people in it
40-46 min
When agile fits; four myths
46-55 min
Group activity: agile or not?
55-60 min
Key points, homework, exit ticket
SE Lecture 3
Plan
Sheet 04 of 20
Slide 5
Why agile was born
1980s-1990s: heavyweight processes
Real-world example: a school system
Long documents, detailed designs, formal approval at every step. Fine for aircraft; too slow for fast-changing business software.
- A software house in Lahore spends four months writing a 200-page requirements document for a school.
- By the time the school signs it, the fee policy has changed and the school also wants a mobile app for parents.
- Half the document is now wrong.
Requirements changed before the document was signed
Months of documents were out of date when coding started
Customers saw working software only at the end
February 2001, Snowbird, Utah (USA): 17 developers who used lighter methods (XP, Scrum, DSDM, Crystal) wrote the Manifesto for Agile Software Development.
Word help
manifesto = a public statement of beliefs
SE Lecture 3
Why agile
Sheet 05 of 20
Slide 6
The Agile Manifesto: four values
We value the items on the left more ...
... over the items on the right
Individuals and interactions
over
processes and tools
Working software
over
comprehensive documentation
Customer collaboration
over
contract negotiation
Responding to change
over
following a plan
The last line: "while there is value in the items on the right, we value the items on the left more." Agile does NOT mean no documents or no plans.
SE Lecture 3
Manifesto
Sheet 06 of 20
Slide 7
The four values in practice
Individuals and interactions
Working software
Two developers sit together for 10 minutes to fix a confusing API, instead of filing a ticket and waiting three days.
Show the school principal a working fee-voucher screen in week 2, instead of a 40-page design document.
Customer collaboration
Responding to change
The client's accountant joins a short meeting every two weeks to check the payroll screens.
The State Bank issues a new rule for digital payments. The wallet team moves it to the top of the next two weeks of work.
Pattern: each value moves the focus from paperwork and control to people, feedback and results.
SE Lecture 3
Manifesto
Sheet 07 of 20
Slide 8
Twelve principles in four groups
A. Customer and change
B. Delivery
Satisfy the customer with early, continuous delivery
Deliver working software every few weeks
Welcome changing requirements, even late
Working software is the main measure of progress
Business people and developers work together daily
Keep a sustainable pace
C. People
D. Quality and improvement
Build around motivated people, and trust them
Technical excellence and good design
Talk face to face
Simplicity: maximize the work not done
Self-organizing teams make the best designs
Reflect regularly, then adjust
Word help
sustainable = can continue for a long time without breaking down self-organizing = the team decides for itself how to do the work
SE Lecture 3
Principles
Sheet 08 of 20
Slide 9
Quick check: which principle?
A
The team shows the client a working login and dashboard after only two weeks.
1 / 3 Deliver early and often
B
In month 4 the client asks for Urdu support. The team says: "Good idea, let's plan it for the next cycle."
2 Welcome change
C
Every two weeks the team meets for 30 minutes: "What should we do differently?"
12 Reflect and adjust
D
A developer removes a "print to fax" feature that no user ever asked for.
10 Simplicity
Call out the principle number before your teacher reveals the answer.
SE Lecture 3
Principles
Sheet 09 of 20
Slide 10
What is agility?
Agility = the ability of a team to respond effectively to change.
Real-world example: cricket fielding
- A captain sets the field before the over.
- After every ball, he moves fielders depending on what the batsman does.
- A plan exists, but it changes as soon as new information arrives. That is agility.
Pressman: agility is more than reacting to change. It also means:
Teams that communicate easily
Quick delivery of working software, fewer in-between documents
The customer is part of the team
Plans are flexible, because planning has limits
Word help
agile = quick, able to change direction easily
SE Lecture 3
Agility
Sheet 10 of 20
Slide 11
Agility and the cost of change
Real-world example: one field
- Make the "CNIC / B-Form" field compulsory.
- During requirements: edit one line.
- After go-live with 20,000 records: change the database, fix old records, the form, the tests, re-deploy.
Be careful: the agile curve is flatter only with small increments, automated tests, refactoring and continuous integration. Big architecture changes stay expensive.
Numbers are only to show the shape of the curves.
SE Lecture 3
Agility
Sheet 11 of 20
Slide 12
What is an agile process?
Pressman: three assumptions about most projects
So the process must adapt
Hard to predict which requirements will stay and which will change
Build a small working increment
Design and construction are interleaved: build, test, then design more
Show it to the customer
Get feedback
Analysis, design, coding and testing are less predictable than we would like
Plan the next 1-4 weeks
Agile process = adaptable + small increments + customer feedback. Specification, design, coding and testing happen together in every short cycle.
SE Lecture 3
Agile process
Sheet 12 of 20
Slide 13
Human factors: the team makes agile work
Competence
Common focus
Real-world example: a cricket team
Skill and process knowledge
One goal: a working increment
- The captain does not tell the bowler where to put every ball.
- Bowler, keeper and fielders talk, adjust and decide together. They trust each other's skill and share one goal.
Collaboration
Decision-making
With the team and the customer
The team is trusted to decide
Fuzzy problem solving
Trust and respect
Handles unclear, changing problems
A team stronger than its members
Word help
competence = skill to do a job well
Self-organization
Plans and organizes its own work
Word help
fuzzy = unclear; no exact answer
SE Lecture 3
Human factors
Sheet 13 of 20
Slide 14
Plan-driven and agile side by side
Copy this table into your notes: it is likely exam material, together with the model comparison from Lecture 2.
SE Lecture 3
Comparison
Sheet 14 of 20
Slide 15
When agile fits, and when it does not
Agile usually fits when ...
Plan-driven is safer when ...
- Requirements unclear or likely to change
- Small or medium system, one team in one place
- Customer can give time and feedback regularly
- Software can be released in small pieces
- Skilled team, trusted to decide
- Regulator must approve detailed documents
- Very large system, many teams in many places
- Customer cannot be involved regularly
- Incremental delivery is not realistic (in hardware)
- New team that needs more structure
Often a mix: a planned contract, architecture and deadline, with short agile cycles inside. Many Pakistani software houses with foreign clients work in short cycles; fixed government tenders usually start plan-driven.
SE Lecture 3
Choosing
Sheet 15 of 20
Slide 16
Four myths about agile
"Agile means no documentation."
"Agile means no planning."
Reality: Agile writes less, and only what is useful: user stories, tests, a short design note.
Reality: Agile plans all the time, in small pieces: release, cycle and day.
"Agile is always faster."
"Agile is just Scrum."
Reality: It delivers useful software earlier. Without discipline it can be slower and messier.
Reality: Scrum is one method. XP, Kanban, Lean and DSDM are others (Lectures 4-6).
SE Lecture 3
Myths
Sheet 16 of 20
Slide 17
Activity: agile or not?
Each group gets one project. Choose agile, plan-driven or a mix. Name one manifesto value or principle that supports you, and one risk.
A. Wallet savings goal
B. Railway signalling
A mobile wallet wants a "save for Eid or school fees" feature. Nobody knows if users will like it.
Software that controls railway signals. A safety authority must approve it before use.
minutes
C. UAF admission portal
D. Farmer voice helpline
Must be live in 3 months. Admission rules are fixed; screens can improve.
A startup app answering farmers' questions in Urdu and Punjabi. Unsure what farmers will ask.
- 6 min in groups of 4-5
- 3 min to share answers
SE Lecture 3
Activity
Sheet 17 of 20
Slide 18
Key points to remember
Agile appeared because heavyweight processes could not keep up with change (Manifesto, 2001).
Four values: individuals, working software, customer collaboration, responding to change.
The right-hand side still has value: agile is not "no documents, no plans".
Twelve principles in four groups: customer and change, delivery, people, quality.
Agility = responding effectively to change; good practice flattens the cost-of-change curve.
An agile process adapts in small increments with customer feedback, and depends on people.
Agile is a fit, not a fashion. Many projects mix agile and plan-driven.
SE Lecture 3
Wrap-up
Sheet 18 of 20
Slide 19
Before the next lecture
Read
For Practical 2 (team)
Pressman, Ch. 5.1-5.3, or Sommerville, 10th ed., section 3.1.
Bring 8 features of your project, each as one sentence about a user need:
- "A student can see today's menu with prices."
- "The owner can mark an item as sold out."
- Features, not tasks: "create database" is a task
- In the lab they go on a Trello Scrum board
Look ahead
Next lecture: Extreme Programming (XP). Skim Pressman 5.4 or Sommerville 3.2. Quiz 1 in week 4 covers Lectures 1-6.
SE Lecture 3
Homework
Sheet 19 of 20
Slide 20
Exit ticket
On a small piece of paper, with your name and roll number:
Which Agile Manifesto value matters most for your team project, and why? (One sentence.)
One question you still have after today.
Questions?
SE Lecture 3
Exit ticket
Sheet 20 of 20