Magic of Agile

Introduction

Various SDLC

Agile

Various Agile Frameworks

Scrum

Q & A

• AGILE – Quick Moving

-Iterative and Incremental Methods of Software Development

• Available Software Development Approach

– Traditional –Plan driven models like waterfall, Spiral, Iterative etc

– Agile-Undefined methods-People Oriented Excellent example of teamwork.

Introduction

Various SDLC

• Challenges for Traditional SDLC

- Sequential Approach of development

- In Practice not possible to freeze all the requirement before starting development.

- Product Realization only after end of development.

- After development, any changes need to revisit entire system

• Solution

- Incremental and Iterative Development

- Dynamic Planning

- Focused Team

- Value for Customer

Various SDLC

• Agile Manifesto Released in 2001

- Individuals and interactions over processes and tools

- Working software over comprehensive documentation

- Customer collaboration over contract negotiation

- Responding to change over following a plan

Agile

Agile

Define Initial RequirementDefine Initial Requirement

High Level Use CaseHigh Level Use Case

High Level PlanningHigh Level Planning

Begin Iteration NBegin Iteration N

Build & Unit TestBuild & Unit Test

System TestSystem Test

User EvaluationUser Evaluation

Change Change RequestedRequested

??

Final System TestFinal System Test

Product Product

ReleaseRelease

Refine RequirementsRefine Requirements

• Main Stages in Agile:-• Define Initial Requirement:

Business will come up with high level requirements to the project. Business has good idea about the facilities or product they want.

• Prepare High level use cases

Based on the initial business requirement, project business analyst will come up with High Level Use cases.

• Prepare High Level Plan

Once the high level use cases finalized and approved Project Manager will prepare a high level plan. Normally this plan will be dynamic .

• Begin iteration

Iteration starts from here and goes in cycle.

• Build and Unit Test

Task of development and Unit test completed here for given use cases. End of this phase Prototype or system released for System Test.

Agile

• System Test

Full System tested before releasing for user evaluation

• User Evolution

Representative of client evaluate the developed system against the requirement and use cases. They also suggest additional requirement those are not clear while initial requirement gathering.

• Are more changes required or any new requirement?

This is the decision point for Next Iteration. If user is not happy with product or need more functionality next iteration will start. Iteration will be stopped Once user all requirements satisfied. .

• Refine requirement/Use case

After user evaluation stage if client asked change in existing options. Its require to change in Requirement and Use case also. Development and Testing Team will use these changes for development and testing.

• Final System Test

Product release

Agile

• Strength

-Quick Start , Incremental Release and Regular customer

Reviews and Feedback

- Evaluation of Requirements Over time

- Ability to respond to change quickly

-Less Rework , achieved through continuous testing and customer involvement

- Real time communication among the development team and customer

• Weakness

- Product with low documentation

- Un-Planned

- Need more expert and cross functional people

- Focused Team (One activity at one time)

Agile

Various Agile Frameworks

Scrum

• Scrum is an iterative and incremental agile software development framework for managing software product or application development

Scrum Cycle

• RolesScrum

The Live Interactive Estimation Session

• Supports– In House Development

– Cross Functional Teams

– More User Interaction

• Against– Lack of Focused Team

– Technical Expertise

– Change of Mindset

• Suggestion

- One Project with dedicated team can be executed with Scrum

Scrum in SBG prospective

Q & A

Mail to subodh_patna@yahoo.comThank You