Agile Principles

CSE4033 - IT Project Management | Module 4: Agile Project Management

Learning Outcomes

By the end of this section, you will be able to:

The 12 Agile Principles

While the Agile Manifesto provides the core values, these 12 principles guide how we implement Agile in practice:

1 Customer satisfaction through early and continuous delivery
2 Welcome changing requirements, even late in development
3 Deliver working software frequently (weeks rather than months)
4 Business people and developers must work together daily
5 Build projects around motivated individuals
6 The most efficient method of face-to-face communication
7 Working software is the primary measure of progress
8 Sustainable development pace indefinitely
9 Continuous attention to technical excellence
10 Simplicity—maximizing work not done—is essential
11 Self-organizing teams produce best architectures and designs
12 Regular reflection and adaptation to become more effective

Agile Principles in Action

Why Principles Matter More Than Practices

Agile methodologies like Scrum and Kanban provide specific practices, but the principles are what guide teams to adapt these practices to their unique context. Understanding these principles helps teams:

Interactive: Prioritizing with Agile Principles

Product Backlog Prioritization

Drag the features below to prioritize them according to Agile principles (most important at the top):

High Priority

Medium Priority

Low Priority

User login functionality
Advanced reporting dashboard
Password recovery feature
Custom theme color options
Basic search functionality
Social media sharing integration

Test Your Understanding

Agile Principles Quiz

1. Which Agile principle emphasizes delivering working software frequently?

Principle 5: Build projects around motivated individuals
Principle 3: Deliver working software frequently
Principle 8: Sustainable development pace
Principle 11: Self-organizing teams

2. What does Agile Principle 10 mean by "maximizing the amount of work not done"?

Avoiding unnecessary documentation
Eliminating all meetings
Focusing on simplicity and essential features
Reducing team size to minimum

3. Which principle suggests that business people and developers should work together daily?

Principle 1
Principle 4
Principle 7
Principle 12

4. What is the Agile approach to changing requirements?

They should be avoided after project start
They should be documented for future versions
They should be welcomed, even late in development
They should trigger contract renegotiation

Further Learning Resources