Satish Kumar Jayaram

Agenda

• Introduction

• Waterfall model

• Agile Overview

• Best Practices in Agile

• Summary

• Questions

About myself

Water fall model

Requirement

Analysis

Design

Implementation

Deployment

Time Day 14 Day 28 Day 42 Day n

Pain Points

• Frequent requirement change

• Estimation inaccuracy

• Too many documentation

• Cascading effect in schedule impact

Agile model

Requirement

Analysis

Design

Implementation

Deployment

Requirement

Analysis

Design

Implementation

Deployment

Requirement

Analysis

Design

Implementation

Deployment

Requirement

Analysis

Design

Implementation

Deployment

SPRINT nSPRINT 2 SPRINT 3SPRINT 1

Time Day 14 Day 28 Day 42 Day n

Agile Overview

• Agility - The power of moving quickly and easily

• Fail early and recover soon

• Wastage is minimum

• Minimal documentation

• Constant effort

Agile Manifesto

Processes and tools

Individuals and interactions

Comprehensive documentation

Working software

Contract negotiation

Customer collaboration

Following a plan

Responding to change

Waterfall vs Agile

Fixed Scope / Features Resources Time

Scope / FeaturesEstimated Resources Time

Plan Driven

Value Driven

What kind of project is Agile suited

• Business is very Dynamic

• High complexity

• Uniqueness

• Yield business value more quickly

Months have turned into weeks. Weeks have turned into days. The world of IT is a fast-paced world and if a project is carried out too slowly, it is simply no longer relevant.

- Author unknown

Slicing the cake

GUI Layer

Application Layer

Business logic layer

DB interface layer

Database Layer

US 1

Slicing the cake (contd..)

GUI Layer

Application Layer

Business logic layer

DB interface layer

Database Layer

US #

US 3

US 2

Types of Agile Methodologies

Agile Methodologies

Scrum KanbanTest-driven

developmentExtreme

ProgrammingFeature Driven development

Scrum – How it works

WBS in SCRUM

Epics

Product backlog

User stories

High level task

Low level task

User stories

High level task

Low level task

Product backlog

User stories

High level task

Low level task

User stories

High level task

Low level task

Scrum

• A scrum team can consist of 7±2

Product Owner

Scrum master

Dev engineers

Test engineers

Product Owner

• Responsibilities

– Write user stories

– Prioritize them

– Negotiate with the team and client

Product Owner

Scrum Master

• Servant - Leader

• Not a SPOC

• Need not be a dedicated resource

• Facilitator

Scrum master

Ceremonies in Scrum

• Release planning

• Sprint planning

• Poker planning

• Daily standup meeting

• Retrospection

• Product backlog grooming

Agile best practices

• Test driven development

• Short releases

• Continuous Integration

• Collective Ownership

• Cross-team integration

• Daily standup

• Code Refactoring

Summary

What’s in for me

• Adapt some of the best practices

• Try Agile methodology to pursue in-house projects

• Try to write user stories from requirements and break them into smaller tasks

• Try the poker planning method for estimation

Known is a drop unknown is an ocean

Questions