การทำซอฟท์แวร์ภายใน 30 วัน

BUILDING SOFTWARE IN

“30”

DAYS

by THAILAND Thursday, August 22, 13

AGENDA

About Speakers 5 minutes

Case Study 10 minutes

Problem from Define Process Control 10 minutes

Solution from Empurical Process Control 10 minutes

Q and A 5 minutes

Thursday, August 22, 13

KULAWAT WONGSAROJ

Agile Coach and CEO, Proteus-Agility

Founder of Agile66

Organizer of Agile Thailand and Agile Tour


TWIN PANICHSOMBAT

Agile Practitioner, Programmer, Odd-e (Thailand)

Administrator of Agile66

Organizer of Agile Thailand


PREDICTIVE: THE WRONG PROCESS PRODUCES THE

WRONG RESULT


TRADITIONAL IS RISKY !!!!


CASE STUDY


BAAC

Start in 2004 with THB 1,200M

Target in 2006 (2 year)

Thai Equipment Research proposed phased traditional software development

In 2007, Change Software Vendor from Temenos to OSI

source ฐานเศรฐกิจ, ผูจัดการ, เวบ baac.or.th


BAAC

In 2009, Cancel contract! (5 years) Paid THB 900M (300M Hardware)

In 2010. BAAC reports Impairment of Assets (การด้อยค่าของสินทรัพย์) THB 750M

source ฐานเศรฐกิจ, ผูจัดการ, เวบ baac.or.th


PREDICTIVE PROCESS

Release take longer and longer

Release schedules slip

Stabilization at end of the release takes longer

Planing takes too long and doesn’t get it right

Changes are hard to introduce mid-release

Quality is deteriorating

Death marches are hurting morale


PROJECT FAILURE

illusion

Requirement not change

Technology working without any problems

People being as predictable and relaiable as machine


PREDICTIVE PROCESSES


FBI’S SENTINEL PROJECT

Start by 2006 with $451M

Target December 2009

Lockhead Martin proposed 4 phases with traditional software development

!!!!!



http://www.agileconference.org/wp-content/uploads/2012/10/Agile-Success-at-the-FBI-Brian-Wernham.pdf

By 2009 spent $405M

Deliver 50%

DOOM!!!!!






Restart in 2009

Co-locate team

Down size team from 400 to 45

“Deliver funtionalities every 30 days”




EMPIRICAL: THE RIGHT PROCESS PRODUCES THE

RIGHT RESULT


3 LEGS OF EMPIRICAL

Inspect Adapt

Transparency


EMPIRICAL KEYWORDS

Iteration

Frequency

Increment

Transparency

Iterative Incremental


RESOLVE PREDICTIVE PROCESS

Release take longer and longer

Release schedules slip

Stabilization at end of the release takes longer

Planing takes too long and doesn’t get it right

Changes are hard to introduce mid-release

Quality is deteriorating

Death marches are hurting morale


PEOPLE PRACTICES IN EMPIRICSM

Respect for individual worker

Built-in instability

Subtle control

Self-organizing project


PEOPLE PRACTICES IN EMPIRICSM

Overlapping development phases

Cross-fertilization

Transfer of learning


AGILITY

