Sprint3 r agile101-introduction-18052556

Agile 101

Introduction to Agile สยามชํานาญกิจ พุทธศักราช ๒๕๕๖

version 2.1

Tuesday, May 21, 13

DisclaimerAll information in this presentation is based on

Agile manifesto + 12 principles of Agile software + speaker’s personal experience + reality (drama) that

he lives in ...

!สยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Tuesday, May 21, 13

What will you GET and NOT

สยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Tuesday, May 21, 13

Who am I?Prathan (Noom) Dansakulcharoenkit

Co-Founder/Practitioner/Coach/Transformer of Agile/ITIL/Software Testing @ SPRINT3R


Certified ScrumMaster (CSM), ScrumAlliance.org

email: [email protected]

twitter: @zyracuze

facebook: https://www.facebook.com/zyracuze

Tuesday, May 21, 13

What is your PAIN POINT of current development?


Question 1

Tuesday, May 21, 13

What is Agile?


Tuesday, May 21, 13

What is your AGILE look like?Please draw the picture


Question 2

Tuesday, May 21, 13

For us Agile is

SPRINT3R by สยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Tuesday, May 21, 13

Manifesto for Agile Software Development

Tuesday, May 21, 13

Manifesto for Agile

source from: www.agilemanifesto.org สยามชํานาญกิจ พุทธศักราช ๒๕๕๖

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following the plan

That is,while there is VALUE in the items on the RIGHT, we VALUE the items on the LEFT MORE.

James GrenningJim HighsmithAndrew HuntRon Jeffries

Jon KernBrian Marick

Robet C. MartinSteve MellorKen Schwaber

Jeff SutherlandDave Thomas

Kent BeckMike Beedle

Arie van BennekumAlistair CockburnWard Cunningham

Martin Fowler

Tuesday, May 21, 13

Manifesto in Thai

source from: www.agilemanifesto.org/iso/th สยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Tuesday, May 21, 13

http://www.agilemanifesto.org/iso/th

http://www.agilemanifesto.org/iso/th

Be Careful


Individuals and interactionsWorking software

Customer collaborationResponding to change

OVER , NOT “INSTEAD OF” !

over

processes and toolscomprehensive documentation

contract negotiationfollowing the plan

Tuesday, May 21, 13

Manifesto for Agile


Individuals and interactions over

processes and tools

Tuesday, May 21, 13

Manifesto for Agile


Working software over

comprehensive documentation

Tuesday, May 21, 13

Manifesto for Agile


Customer collaboration over

contract negotiation

Tuesday, May 21, 13

Manifesto for Agile


Responding to change over

following the plan

Tuesday, May 21, 13

Agile Manifesto Principles


Satisfy the Customer

WelcomeChange

DeliverFrequently

CollaborateDaily

Support & TrustMotivated Teams

PromoteFace-to-FaceConversation

Deliver WorkingSoftware

PromoteSustainable

Pace

PromoteTechnicalExcellence

MaximizeThroughSimplicity

HaveSelf-Organized

Teams

Reflect & AdjustRegularly

Tuesday, May 21, 13

Measure of Agile


Number of Books in Amazon.com

3731,6422,0642,9079,525Lean Software Development

Kanban

Extreme Programming

ScrumAgile

Search result as of May 2013

Tuesday, May 21, 13

Agile Myths


Tuesday, May 21, 13

Myths, How Come

Old habits

Previous experience

Where do myths come from?

Lack of knowledge

No hands on experience

Fear of change/responsibility/transparency

Curse of knowledge


Tuesday, May 21, 13

Agile is NEW


1943

Taiichi OhnoToyota Production SystemKanban

1950-1960

USAF & NASAX-15 hypersonic jetIteration IncrementalDelivery

1985

Hirotaka Takeuchi & Ikujiro NonakaThe New New Product Development Game

1990

Sutherland & SchwaberScrum Framework

1995

DSDN ConsortiumDynamic System Development Method

1997

Jeff de LucaFeature Driven Development

2000

Robert CharetteLean Development

1996

Beck Cunningham, JeffriesExtreme Programming

1998

Alistair CockburnCrystal Methodologies

2001

Agile Manifesto

Hardware Software

True or FalseXTuesday, May 21, 13

Agile is Quick Fix



Agile is Simple Switch



Agile is Fast



Agile is Easy



Agile is No Documentation



Agile is No Plan


True or FalseX

Product / ProjectWhat business objective will

this fulfill?

Vision/MissionGoals

ReleaseHow can we release value

incrementally?What subset of business objectives

will each release achieve?Which user(s) will the release serve?

What general capabilities will the release offer?

Release RoadmapRelease Plan

IterationWhat specifically will we build?How will this iteration move us toward release objectives?

Iteration PlanDevelopment Tasks

Backlog ItemWhat user or stakeholder need will the backlog item server?How will I know if it is done?

Backlog Item DetailAcceptance Tests

Tuesday, May 21, 13

Introduction to Methodology to be Agile


Tuesday, May 21, 13

Ready to use Methodology


Extreme Programming, Scrum and Kanban

Tuesday, May 21, 13

Extreme Programming


Tuesday, May 21, 13

Scrum


Tuesday, May 21, 13

Kanban


Tuesday, May 21, 13

Definition of Done


Tuesday, May 21, 13

Traditional vs Agile


Tuesday, May 21, 13

Traditional vs Agile


Where the RISK lies

Tuesday, May 21, 13

Impediment to do Agile


Tuesday, May 21, 13

How about Quality in Agile


Tuesday, May 21, 13

Software QUALITY


Tuesday, May 21, 13

Quality Triangle


SpecificationRequirements

Software

Gap

Tuesday, May 21, 13

Quality Triangle

Requirements Specification

Software

It’s an IDEAL!!!


Tuesday, May 21, 13

How many figure of triangle can TRANSFORM?


Question 2

SpecificationRequirements

Software

Tuesday, May 21, 13

Quality Triangle

In the real WORLDSPRINT3R by สยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Software


Tuesday, May 21, 13

Quality Triangle


Software


Tuesday, May 21, 13

Quality Triangle


Requirements

Software

Specification

Tuesday, May 21, 13

Quality Triangle


Software


Tuesday, May 21, 13

Where Do Bug Come?

Requirements definition

System design

Implementation

Support systems

Lack of software testing skills

Evolution


Tuesday, May 21, 13

Some Facts of TestingALWAYS be a chance that software will have bugs

CANNOT prove software works by testing it

DOES NOT prove that software is bug-free

Testing after software has been created DOES NOT improve its quality

Cost of removing bugs rises DRAMATICALLY in the later phases of the software development process

QUALITY depends on 3 factors; People, Process and Tool


Tuesday, May 21, 13

Some Goals of TestingDetermine a product MEET business expectation

MINIMIZE the risk of error occurs

IS NOT the process to verify software work correct

Testing must be to DEMONSTRATE that software does have bug

Tester must find bug as EARLY as possible and make sure that they are fixed


Tuesday, May 21, 13

Some Facts in NASA

as the 120-tons space shuttle sits surrounded by almost 4 million pounds of rocket fuel..

...the last three versions of the program -- each 420,000 lines long-had just one error each. The last 11 versions of this software had a total of 17 errors...

Source: http://www.fastcompany.com/magazine/06/writestuff.htmlสยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Tuesday, May 21, 13

http://www.fastcompany.com/magazine/06/writestuff.html

http://www.fastcompany.com/magazine/06/writestuff.html

Some Facts in NASA


Tuesday, May 21, 13

Some Goals of TestingDetermine a product MEET business expectation

MINIMIZE the risk of error occurs

IS NOT the process to verify software work correct

Testing must be to DEMONSTRATE that software does have bug

Tester must find bug as EARLY as possible and make sure that they are fixed


Tuesday, May 21, 13

Test Case

inputs to test system and verify with expected outputs

Test Case = Test Rule + Test Data


Tuesday, May 21, 13

Test IterationsTest to Pass

Test to Failสยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Tuesday, May 21, 13

Team Organization

DomainExpert

Tester

Programmer

Traditional Organization


Tuesday, May 21, 13

SOMEONE

Who feel responsible for QUALITY in traditional development (Waterfall)?


Tuesday, May 21, 13

Team OrganizationAgile Organization

DomainExpert

Programmer

Tester


Tuesday, May 21, 13

WHOLE TEAM

Who feel responsible for QUALITY in alternative development (Agile)?


Tuesday, May 21, 13

Whole Team ApproachTeam commitment to quality

Team responsible for testing

Tester get support, training

Programmers do testing activities

Tester and programmer pair

Get the right person


Tuesday, May 21, 13

3Cs

Card

Conversation

Confirmation


Tuesday, May 21, 13

Self-Organizing Team

info

Guide

info info info

infoinfoinfo

Guide Guide Guide

GuideGuide

Guide


Tuesday, May 21, 13

Agile vs CI vs CD vs DevOps


Tuesday, May 21, 13

Conclusion


Tuesday, May 21, 13

Agile TeamDo same development waterfall team, but do it

very difference

Do same functions as the waterfall method; requirement-gathering, design, coding and testing

Test as you go, not at the end

Deliver product early and often, as only by demonstrating working software to customer

Document as you go, and only needed

Build cross-functional team to break down siloสยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Tuesday, May 21, 13

Starting use Agile

Start small and Solving problem one by oneสยามชํานาญกิจ พุทธศักราช ๒๕๕๖

Tuesday, May 21, 13

Are you ready to NUDE?

Transparency


Tuesday, May 21, 13

What is your AGILE look like?Please draw the picture

Question 3


Tuesday, May 21, 13

All you NEED is Coach


Tuesday, May 21, 13


สยามชํานาญกิจ = ชุมเกรียนส์

Tuesday, May 21, 13

SOURCESINSPIRATION

Web, Agilemanifesto.org

Book, The Elements of Scrum by Chris Sims and Hillary Louise Johnson

Book, An Agile Adoption and Transformation Survive by Michael Sahota

Book, Agile Retrospective by Esther Derby and Diana Larsen

Presentation, An Alternative Software Development Methodology, by @Roofimon

Presentation, Agile 101: What is Agile and What is Agile Not by Derek Huether

Presentation, Agile Myths by Dmistry Buzdin

Presentation, Agile Myth by Marc Loffler

IMAGE CREDIT

Flickr

Google


Tuesday, May 21, 13

Thanks Youกราบ (-/\-)


Tuesday, May 21, 13

Documents

Sprint3 r agile101-introduction-18052556