Agile Software Development

By,Sanjeev Nandivada

Agenda

•Agile Software Development•What is Scrum•Scrum Roles•Scrum Process in detail•Points to remember

What is Agile Software Development

Agile Software Development is a group of software development methodologies and a disciplined project management process that encourages frequent inspection and adaption based on a iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.

What is Waterfall Model of Software Development

Draw backs of Waterfall Model

• The main draw back of the waterfall model is the difficulty of accommodating change after the process is underway. One phase has to be complete before moving onto the next phase.• Inflexible partitioning of the project into distinct stages makes

it difficult to respond to changing customer requirements.• Therefore this model is only appropriate when the

requirements are well-understood and changes will be fairly limited during the design process.• The waterfall model is mostly used for large systems

engineering projects where a system is developed at various sites.

What is Scrum

“Scrum is a framework for developing complex products and systems. It is grounded in empirical process and control theory. Scrum employs an iterative and incremental approach to optimize predictability and control risk.”- Ken Schwaber

Scrum Roles

Scrum Process in detail

Product Owner takes all the requirements/features from Customer, Stakeholders, Users etc and creates user stories

All the requirements are taken and broken down into User stories

All the user stories written are collected and formed into Product Backlog. All this process happens after discussing with and with the consent of Customers, Stakeholders, Users, etc.

Product owner will prioritize the user stories in the Product Backlog considering various aspects like Business Value, Cost and effort of Implementation, Complexity and Difficulty to Implement, Third Parties/Vendor Involvement, etc and create a Release Backlog.

Product owner along with Scrum master and the team initiates the sprint planning meeting in which they will discuss about the duration of the sprint, user stories that need to be considered for that particular sprint, etc.

After completion of Spring planning meeting some user stories are considered and a Sprint Backlog is created

Sprint Backlog is further broken down into various Tasks and sub-tasks. Based on the progress of the work the status of the task is changed In Progress, To Verify and Done

A scrum master is the facilitator for a team, he manages the process for how information is exchangedThe scrum master is responsible for:1. Helping the team to reach consensus for what can be achieved during a specific period of time2. Helping the team to reach consensus during the daily scrum3. Helping the team to stay focused and follow the agreed-upon rules for daily scrums4. Removing obstacles that are impeding the team's progress.5. Protecting the team from outside distractions

A daily stand-up meeting (or simply "stand-up") is a meeting in which attendees typically participate while standing. 1. What did you do yesterday?2. What will you do today?3. Are there any impediments in your way?

A Potentially Shippable Product is the sum of the Product Backlog Items delivered each Sprint. Delivering Potentially Shippable Product each Sprint is fundamental to the Scrum because when work is divided into simple pieces it can be finished in a short iterations.

Sprint Review meeting takes place at the end of each sprint, where in the scrum team will demonstrate the developed product to the Customer, Stakeholders, Product owner, etc

Each Sprint ends with a retrospective. At this meeting, the team reflects on its own process. They inspect their behavior and take action to adapt it for future Sprints. In this meeting they will ask themselves three questions:1. What went well in the scrum2. What did not went well in the scrum3. Was there any impediments occurred and how to

handle them if they reoccur in next sprint

Questions