Unit-I

Agile Methodologies in Software Engineering

 Agile Methodologies in Software Engineering
• Agile methodology is a set of principles for software development where
requirements and solutions evolve through collaboration between self-
organizing cross-functional teams.

• Key Characteristics:
– Iterative and incremental development.
– Flexibility and responsiveness to change.
– Emphasis on customer collaboration and satisfaction.

2 v 1.2
• Scenario: A software development team is tasked with creating a new mobile
application for online banking. The project requirements are not fully defined at the
start, as the customer’s needs are expected to change during development.
• Agile Approach:
• Iteration Planning: The project is divided into short iterations (sprints), each lasting
two weeks. At the start of each sprint, the team meets with the customer to discuss
the most important features to develop during that sprint.
• Collaboration: The team, consisting of developers, testers, and a product owner
(who represents the customer), works closely together. Daily stand-up meetings are
held to discuss progress, challenges, and plans for the day.
• Incremental Delivery: At the end of each sprint, the team delivers a functional
version of the application with the features developed during that sprint. The
customer reviews the product and provides feedback, which is used to refine future
sprints.
• Adaptation: Based on customer feedback and any new requirements, the team
3 adjusts the project scope and priorities.
v 1.2 This flexibility allows the project to adapt to
changing customer needs.
 Agile Manifesto

• Four Core Values: Individuals and Interactions over

processes and tools.
– Working Software over comprehensive documentation.
– Customer Collaboration over contract negotiation.
– Responding to Change over following a plan.
• Twelve Principles:
– Cover continuous delivery, welcoming changing requirements,
sustainable development, and technical excellence, among
others.

4 v 1.2
 Agile vs. Traditional Methodologies

• Traditional (Waterfall) Methodology:

– Sequential design process (e.g., Waterfall model).
– Emphasis on up-front planning and documentation.
– Late testing and high risk of project failure if requirements change.
• Agile Methodology:
– Iterative cycles, frequent releases.
– Testing throughout the development process.
– Lower risk due to ongoing feedback and flexibility.

5 v 1.2
 Agile Methodologies Overview
• Scrum:
– Iterative sprints, daily stand-ups, and roles like Scrum Master and Product Owner.
• Kanban:
– Visualize work, limit work in progress (WIP), and enhance flow.
• Extreme Programming (XP):
– Focus on technical practices like Test-Driven Development (TDD), pair programming,
and continuous integration.
• Lean Software Development:
– Eliminate waste, build quality in, and deliver fast.

6 v 1.2
 Scrum Framework in Detail

• Key Roles:
– Product Owner: Defines the product backlog and priorities.
– Scrum Master: Facilitates the process and removes obstacles.
– Development Team: Cross-functional group responsible for delivering
increments.
• Ceremonies:
– Sprint Planning: Define the sprint goal and select backlog items.
– Daily Stand-Up: Short daily meeting to synchronize the team.
– Sprint Review: Review completed work and gather feedback.
– Sprint Retrospective: Reflect on the process and improve.
• best sprint goals are SMART goals: Specific, Measurable, Attainable,
Relevant, and Time-Based.
7 v 1.2
 Kanban Framework in Detail

• Principles )(jira tool)

– Visualize Workflow: Use Kanban boards to track work
progress.
– Limit Work in Progress (WIP): Avoid bottlenecks by limiting
tasks in progress.
– Manage Flow: Focus on the movement of tasks through
stages.
• Kanban vs. Scrum:
– Continuous delivery vs. time-boxed sprints.
– Flexible vs. structured approach to tasks.
8 v 1.2
 Extreme Programming (XP)

• Core Practices:
– Test-Driven Development (TDD): Writing tests before code to ensure
functionality.
– Pair Programming: Two developers work together at one workstation.
– Continuous Integration: Frequent integration of code into the main
branch.
– Refactoring: Continuous improvement of code without altering
functionality.

9 v 1.2
 Agile Practices in Action

• Continuous Feedback:
– Regular customer feedback loops to ensure the product meets user
needs.
• Adaptive Planning:
– Adjusting plans based on ongoing learning and discovery.
• Incremental Delivery:
– Delivering small, functional pieces of software regularly.
• Simplicity:
– Maximizing the amount of work not done, focusing only on essential
features.

10 v 1.2
 Challenges in Agile Adoption

• Common Challenges:
– Cultural Resistance: Teams accustomed to traditional methods.
– Scaling Agile: Difficulties in applying Agile to large projects or teams.
– Maintaining Quality: Rapid iterations may lead to compromised quality
if not managed properly.
• Solutions:
– Strong leadership, continuous training, and adaptation of Agile to fit the
organization.

11 v 1.2
 Conclusion

• Summary:
– Agile methodologies offer a flexible, responsive approach to software
development.
– Emphasis on collaboration, continuous improvement, and customer
satisfaction.
– Agile is not a one-size-fits-all solution; it must be tailored to the specific
context of the project.

• Final Thought:
– Continuous learning and adaptation are key to successful Agile
implementation.

12 v 1.2