how to live with agile - aware in bugday bangkok 2012

31

Upload: prathan-d

Post on 05-Nov-2014

1.143 views

Category:

Technology


4 download

DESCRIPTION

 

TRANSCRIPT

Page 1: How to live with agile - Aware in BugDay Bangkok 2012
Page 2: How to live with agile - Aware in BugDay Bangkok 2012

“Quality is the link to Success”

Page 3: How to live with agile - Aware in BugDay Bangkok 2012

• Disadvantage of traditional SDLC • What is Agile? • Agile vs Conventional Testing • Scrum • The soft skills for a Scrum Team • Scrum Activities • Case Study • Benefits of Agile

Agenda

Page 4: How to live with agile - Aware in BugDay Bangkok 2012

Always Delayed Deployment to real time world, impacting customers business.

New Requirements and Change Requirements are not considered in immediate builds.

Customer’s feedback and inputs on AUT are possible at a very later stage of SDLC.

Incomplete Documentation, Complete documentation is a complicated and a time consuming task.

Disadvantage of traditional SDLC

Page 5: How to live with agile - Aware in BugDay Bangkok 2012

What is Agile?

A group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams.

Page 6: How to live with agile - Aware in BugDay Bangkok 2012

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 Manifesto

Page 7: How to live with agile - Aware in BugDay Bangkok 2012

Agile looks like

Page 8: How to live with agile - Aware in BugDay Bangkok 2012

Waterfall V.S. Agile

Page 9: How to live with agile - Aware in BugDay Bangkok 2012

Growing of application

Growing of application

Growing of application

Req. UT + Code

Test Demo Req. UT + Code

Test Demo Req. UT + Code

Test Demo

Iterative functionality

feedback & change

feedback & change

Time

Growing of application

Req. Code + UT Test Release

Waterfall

Agile

The way application is made

Page 10: How to live with agile - Aware in BugDay Bangkok 2012

Non- Agile Agile

Requirement Specifications SRS, large effort to get it all specified up front

Just-Enough, Just-In-Time

Release Cycle Typically 6-18 Months 2-3 months release, 1- 4 wks Iterations

Product An often bloated product that is still missing features (i.e. rejected change requests or features de-scoped to meet deadlines)

The best product according to customers own prioritization, incorporating learning from actual use.

Relationships Contractual. Collaborative.

ROI Revenue stream initiation and value creation are delayed until the lowest priority features are delivered.

Value is generated early, as soon as the minimum key feature set is delivered. Smaller projects mean lower cost per project. More projects are delivered. Greater return on investment.

Difference between Agile and Conventional Testing

Page 11: How to live with agile - Aware in BugDay Bangkok 2012

Continuously Improvement

Page 12: How to live with agile - Aware in BugDay Bangkok 2012

Agile Unified Process (AUP)

Crystal Clear

Dynamic Systems Development Method (DSDM)

Essential Unified Process (EssUP)

Exia Process (ExP)

Extreme Programming (XP)

Feature Driven Development (FDD)

Kanban (development)

Open Unified Process (OpenUP)

Scrum

Types of Agile

Page 13: How to live with agile - Aware in BugDay Bangkok 2012

“Scrum is made up of three roles, three ceremonies

and three artifacts.”

Roles: The Product Owner, who is responsible for the business value of the project; the Scrum-Master, who ensures that the team is functional and productive; and the self-organized team.

Ceremonies: the sprint planning meeting, daily scrum meeting, and sprint review meeting

Artifacts: the product backlog, the sprint backlog, and a burn-down chart

Scrum Basic

Page 14: How to live with agile - Aware in BugDay Bangkok 2012

Agile Development Process with Scrum

Page 15: How to live with agile - Aware in BugDay Bangkok 2012

Burn down Chart

A burn down chart is a graphical representation of work left to do versus time. The outstanding work (or backlog) is often on the vertical axis, with time along the horizontal.

Page 16: How to live with agile - Aware in BugDay Bangkok 2012

1.Team Spirit 2.Communication 3.Commitment 4.Problem Solving 5.Transparency

The pre-requisite soft skills for a Scrum Team

Team can deliver high value software features in a short time period “

Page 17: How to live with agile - Aware in BugDay Bangkok 2012

Sprint Planning

Page 18: How to live with agile - Aware in BugDay Bangkok 2012

Estimating Size with Story Points

• Story Points Are Relative

– Raw value not important but Relative is.

– Two common ways to get started

Pick the smallest story then assign 1 point

Pick the medium-size story then assign 5 points

1 2 3

Page 19: How to live with agile - Aware in BugDay Bangkok 2012

• Velocity – A team’s rate of progress.

– Total story points completed during the iteration.

– Size = 100 points & Velocity = 10 & 1-Week Iteration, we need 10 iterations, which equals 10 weeks on the calendar.

3 5 3 2 IT1

Velocity = 13

1 week

3 5 3 2 IT2

Velocity = 8

1 week

completed

not finished

not started

Estimating Size with Story Points

Page 20: How to live with agile - Aware in BugDay Bangkok 2012

Scrum meeting board

Total Transparency At any time the status of the project is visible for everybody

Page 21: How to live with agile - Aware in BugDay Bangkok 2012

Dinning table

Multi disciplinary teams are located on one “Dinning table” (PM/BAs/QAs/DEVs)

Page 22: How to live with agile - Aware in BugDay Bangkok 2012

Daily Standup Meeting

Page 23: How to live with agile - Aware in BugDay Bangkok 2012

Iteration 1

F1 F2 F3

ST ET RT AT

Re-prioritization for Iteration 2

F4 F5 F6

Iteration 2

F4 F5 F6

ST ET RT AT

Iteration N

Different Types of Testing for Each Iteration

F – Feature

D- Defect

ST – System Testing

ET – Exploratory Testing

RT – Regression Testing

AT- Acceptance Testing

F F F F Defects

Product Backlog

Defects

Defects

Defects

Defects

F7 F8 F9 Defects

Re-prioritization for Iteration N

F7 F8 F9

Sprint Planning and defect fixing

Page 24: How to live with agile - Aware in BugDay Bangkok 2012

Project Status

Total Transparency At any time the status of the project is visible for everybody

Page 25: How to live with agile - Aware in BugDay Bangkok 2012

Tools

Open source Tools Commercial Tools

Agile Tools

Page 26: How to live with agile - Aware in BugDay Bangkok 2012

Case Study

Page 27: How to live with agile - Aware in BugDay Bangkok 2012

Plan placeholder for ST/SIT/UAT in each sprint

Page 28: How to live with agile - Aware in BugDay Bangkok 2012

Benefits of Agile

Page 29: How to live with agile - Aware in BugDay Bangkok 2012

Agile Conclusion

Credit : CA Technologies

Page 30: How to live with agile - Aware in BugDay Bangkok 2012
Page 31: How to live with agile - Aware in BugDay Bangkok 2012