Agile

Points

•Software Development Methodologies

• Pros and Cons

• Deep dive

• Value Proposition

Software Development Methodologies

• Waterfall• Agile Scrum XP Kanban

Waterfall workflow

Gather Requirement

Create Design

Develop Product

Test Deliverables

Deploy Product

Maintenance

Waterfall workflow

Gather Requirement

Create Design

Develop Product

Test Deliverables

Deploy Product

Maintenance

Real World Scenario

Change

Takes too long

Gets skipped

Re-done

Delayed

Expensive

Waterfall Usage

• Stable Requirements• Sponsors can visualize clearly at conceptualization stage• Well documented deliverables• Constant market scenario• Product retains its relevance throughout SDLC

What is Agile?

• Sponsors conceptualization evolves gradually• Iterative development• Requirement and Solutions evolve• Collaborative effort between self-organizing cross-functional members

Agile Manifesto

Individuals & Interactions

Processes & Tools

Working SoftwareComprehensive Documentation

Customer Collaboration

Contracts and Negotiation

Responding to Change

Following a Plan

over

over

over

over

Agile Manifesto

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Embrace Change

Agile Manifesto

Deliver working software frequently, ranging from a couple of weeks to a couple of months, with a preference to the shorter timescale.

Frequent Delivery

Agile ManifestoEarly Delivery

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

Agile ManifestoCollaboration

Business people and developers must work together daily throughout the project.

Agile ManifestoMotivated Individuals

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

Agile ManifestoConversation

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Agile ManifestoWorking Software

Working software is the primary measure of progress.

Agile ManifestoSustainable

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

Agile ManifestoSimplicity

Simplicity--the art of maximizing the amount of work not done is essential.

Simply Google

Agile ManifestoTechnical Excellence

Continuous attention to technical excellence and good design enhances agility.

Agile ManifestoSelf Organizing Teams

The best architectures, requirements, and designs emerge from self-organizing teams.

Agile ManifestoTune and Adjust

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile Shift What’s the approach?

Agile flavors

Scrum Most commonly used…

Scrum How to play?

Scrum What they mean?

User story It captures the 'who', 'what' and 'why' of a requirement in a simple, concise way, often limited in detail by what can be hand-written on a small paper note.E.g. As a sales manager, I want to search for my customers by their first and last names so I can communicate with them with ease.

Velocity The total effort a team is capable of in a sprint. The number is derived by evaluating the story points completed from the last few sprint's stories/features. This is a guideline for the team and assists them in understanding how many stories they can do in a future sprint.

Daily Scrum Each day during the sprint, a project team communication meeting occurs at the same location and same time every day for 15mins.

Sprint planning meeting It is held at the beginning of the sprint cycle where team selects what work is to be done, Prepare the time-bound Sprint Backlog, Identify and communicate how much of the work is likely to be done during the current sprint.

Burn down The sprint burn down chart is a publicly displayed chart showing pending work in the sprint backlog. It is updated every day. It gives a simple view of the sprint progress. It also provides quick visualizations for reference.

Scrum Master The person responsible for the Scrum process, making sure it is used correctly and maximizing its benefits. He is not a member Scrum team(s).

Product Owner The person responsible for maintaining the Product Backlog by representing the interests of the stakeholders, and ensuring the work done by Development Team adds value to end Product.

Why Agile? What’s in it for me?

Reduced Cost Project Success

Improved Business Value

Conclusion