Agile manifesto and principles in Software Engineering - Step-by-Step Execution

Concept Flow - Agile manifesto and principles

Start: Project begins

↓

Apply Agile Manifesto Values

↓

Follow 12 Agile Principles

↓

Iterative Development Cycle

↓

Deliver Working Software Frequently

↓

Gather Feedback & Adapt

↩Back to Iterative Development Cycle

The Agile process starts with the manifesto values, follows the 12 principles, and cycles through iterative development, frequent delivery, and adaptation based on feedback.

Execution Sample

Software Engineering

1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation
4. Responding to change over following a plan

These four lines represent the core values of the Agile Manifesto guiding software development.

Analysis Table

Step	Action	Description	Result
1	Start project	Project team begins work	Ready to apply Agile values
2	Apply Agile Manifesto values	Focus on people, working software, collaboration, and flexibility	Guides team mindset
3	Follow Agile principles	Use 12 principles like frequent delivery, welcoming change	Sets detailed behavior rules
4	Develop iteratively	Work in short cycles called iterations or sprints	Produces small working software parts
5	Deliver working software frequently	Release usable software every few weeks	Stakeholders see progress
6	Gather feedback	Collect input from users and team	Identify improvements
7	Adapt plan	Change priorities and work based on feedback	Keeps project aligned with needs
8	Repeat iterative cycle	Go back to development with updated plan	Continuous improvement
9	End project	When goals met or product complete	Project delivered successfully

💡 Project ends when goals are met or product is complete

State Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6	After Step 7	Final
Team mindset	Undefined	Focused on Agile values	Aligned with Agile principles	Ready for iterative work	Delivering working software	Open to feedback	Flexible to change	Agile mindset fully adopted
Project progress	0%	0%	0%	Partial (iteration 1)	Partial (iteration 1 delivered)	Partial (feedback collected)	Partial (plan adapted)	Complete or ongoing

Key Insights - 3 Insights

Why does Agile emphasize 'working software over comprehensive documentation'?

Because delivering usable software frequently (see execution_table step 5) helps teams and customers see real progress, rather than spending too much time on documents that may become outdated.

How does Agile handle changes in project requirements?

Agile welcomes change even late in development (step 7), adapting plans based on feedback to keep the project aligned with customer needs.

What is the purpose of iterative development cycles in Agile?

Iterative cycles (step 4 and 8) break work into small parts, allowing frequent delivery and continuous improvement through feedback.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does the team first deliver working software?

A Step 4

B Step 5

C Step 6

D Step 7

💡 Hint

Check the 'Result' column for 'Stakeholders see progress' in the execution_table

According to variable_tracker, what is the team mindset after step 3?

A Undefined

B Focused on Agile values

C Aligned with Agile principles

D Ready for iterative work

💡 Hint

Look at the 'Team mindset' row under 'After Step 3' in variable_tracker

If the team skips gathering feedback (step 6), what impact would it have on the Agile cycle?

A Plan adaptation would be less effective or missing

B No impact, cycle continues as normal

C Working software delivery would stop

D Project would end immediately

💡 Hint

Refer to execution_table steps 6 and 7 where feedback leads to plan adaptation

Concept Snapshot

Agile Manifesto has 4 key values:
- People over processes
- Working software over docs
- Customer collaboration over contracts
- Responding to change over plans
Follow 12 principles like frequent delivery and welcoming change.
Work in short cycles, deliver often, get feedback, adapt continuously.

Full Transcript

The Agile Manifesto guides software projects by valuing individuals and interactions, working software, customer collaboration, and flexibility over rigid processes and plans. Teams follow 12 principles that emphasize frequent delivery, welcoming change, and continuous improvement. The process flows from applying these values and principles to working in short iterative cycles called sprints. After each cycle, teams deliver working software, gather feedback, and adapt plans accordingly. This cycle repeats until the project goals are met. Key moments include understanding why working software is prioritized over documentation, how Agile embraces change, and the role of iterative development. Visual tables track the team's mindset and project progress step-by-step, showing how Agile keeps projects flexible and focused on real results.

Practice

1. Which of the following is one of the four main values of the Agile Manifesto?

easy

A. Individuals and interactions over processes and tools

B. Comprehensive documentation over working software

C. Contract negotiation over customer collaboration

D. Following a strict plan over responding to change

Solution

1. Step 1: Recall the Agile Manifesto values

   The Agile Manifesto emphasizes valuing individuals and interactions more than processes and tools.

2. Step 2: Compare options with the values

   Individuals and interactions over processes and tools matches the first value exactly, while others contradict Agile principles.

3. Final Answer:

   Individuals and interactions over processes and tools -> Option A

4. Quick Check:

   Agile value = Individuals and interactions over processes and tools [OK]

Hint: Remember Agile values prioritize people and working software [OK]

Common Mistakes:

• Confusing Agile values with traditional waterfall values
• Choosing options that emphasize documentation or strict plans
• Ignoring the 'over' comparison in values

2. Which of the following correctly states a principle from the Agile Manifesto?

easy

A. Avoid customer involvement during development

B. Maximize documentation to ensure clarity

C. Deliver working software frequently, from a couple of weeks to a couple of months

D. Stick rigidly to the initial plan regardless of changes

Solution

1. Step 1: Identify Agile principles about delivery

   One Agile principle is to deliver working software frequently, enabling quick feedback.

2. Step 2: Match options to Agile principles

   Deliver working software frequently, from a couple of weeks to a couple of months matches this principle; others contradict Agile ideas about flexibility and collaboration.

3. Final Answer:

   Deliver working software frequently, from a couple of weeks to a couple of months -> Option C

4. Quick Check:

   Agile principle = Frequent delivery of working software [OK]

Hint: Look for options about frequent delivery and customer collaboration [OK]

Common Mistakes:

• Choosing options that emphasize heavy documentation
• Ignoring the importance of customer involvement
• Selecting rigid planning over adaptability

3. Consider this Agile principle: "Welcome changing requirements, even late in development." What is the main benefit of this principle?

medium

A. It helps teams deliver software that better fits customer needs

B. It reduces the need for team communication

C. It forces teams to stick to the original plan

D. It allows teams to ignore customer feedback

Solution

1. Step 1: Understand the principle about changing requirements

   Welcoming changes late means teams stay flexible to meet evolving customer needs.

2. Step 2: Identify the benefit of flexibility

   This flexibility helps deliver software that fits customer needs better, improving satisfaction.

3. Final Answer:

   It helps teams deliver software that better fits customer needs -> Option A

4. Quick Check:

   Agile principle = Flexibility improves customer fit [OK]

Hint: Changing requirements improve product fit, not ignore feedback [OK]

Common Mistakes:

• Thinking changes reduce communication
• Believing Agile ignores plans completely
• Confusing flexibility with lack of discipline

4. A team claims they follow Agile but never involve customers during development. What is the main issue with this approach?

medium

A. It improves team autonomy and speed

B. It contradicts Agile principles about customer collaboration

C. It aligns perfectly with Agile values

D. It reduces the need for working software

Solution

1. Step 1: Recall Agile values about customer collaboration

   Agile values customer collaboration over contract negotiation, encouraging ongoing involvement.

2. Step 2: Analyze the team's approach

   Not involving customers contradicts this value and can lead to poor product fit.

3. Final Answer:

   It contradicts Agile principles about customer collaboration -> Option B

4. Quick Check:

   Agile value = Customer collaboration is essential [OK]

Hint: Agile always involves customers during development [OK]

Common Mistakes:

• Assuming no customer means faster delivery
• Thinking Agile discourages customer input
• Confusing customer collaboration with contract negotiation

5. A software team wants to apply Agile principles to improve delivery. They plan to deliver working software every month but struggle with changing requirements and team communication. Which two Agile principles should they focus on to solve these issues?

hard

A. Focus on contract negotiation and detailed upfront design

B. Maximize documentation and avoid customer involvement

C. Stick to the original plan and reduce team meetings

D. Welcome changing requirements and promote face-to-face communication

Solution

1. Step 1: Identify principles related to changing requirements

   Agile encourages welcoming changing requirements to adapt quickly.

2. Step 2: Identify principles related to communication

   Agile values face-to-face communication as the most effective way to share information.

3. Step 3: Match options to these principles

   Welcome changing requirements and promote face-to-face communication correctly combines welcoming change and promoting direct communication.

4. Final Answer:

   Welcome changing requirements and promote face-to-face communication -> Option D

5. Quick Check:

   Agile principles = Embrace change + direct communication [OK]

Hint: Focus on change acceptance and direct team communication [OK]

Common Mistakes:

• Choosing options that emphasize documentation over communication
• Ignoring the importance of adapting to change
• Confusing contract negotiation with collaboration