An Alternative Software Development Methodology

Twin PanichsombatThursday, May 9, 13

Twin PanichsombatAgile Practitioner

Odd-e(Global)

Thursday, May 9, 13

Thursday, May 9, 13

Thursday, May 9, 13

About Me

Thursday, May 9, 13

About Me

Thursday, May 9, 13

2001?

Thursday, May 9, 13

Thursday, May 9, 13

Thursday, May 9, 13

Thursday, May 9, 13

Software Development in my perspective

(before)

http://www.flickr.com/photos/eleaf/2536358399/in/photostream/

Thursday, May 9, 13

ConstructionArchitect Engineering

Labor Work

Thursday, May 9, 13

ConstructionSoftware Architect

Software Engineering Software Worker (programmer)

Thursday, May 9, 13

We were forced to believe in that.

Thursday, May 9, 13

How many ways can we construct the building?

http://www.flickr.com/photos/danslegrandbleu/4365319943/

Thursday, May 9, 13

How many ways can we construct software?

http://www.flickr.com/photos/joedsilva/4698703312/

Thursday, May 9, 13

Software is about business

http://www.flickr.com/photos/standhere/462675095/

Business never stop

Software must “SOFT”

Thursday, May 9, 13

Craftsmanship

credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/

Thursday, May 9, 13

!Craftsmanship.isEqualTo( Cowboy)

Thursday, May 9, 13

“Methodology”

Thursday, May 9, 13

Methodology

Thursday, May 9, 13

Methodology

Team Structure

Thursday, May 9, 13

Methodology

Team Structure

Team Discipline

Thursday, May 9, 13

Methodology

Team Structure

Team Discipline

Individual Discipline

Thursday, May 9, 13

The greatest traditional

http://www.flickr.com/photos/38019504@N04/5101530474/

Thursday, May 9, 13

http://leadinganswers.typepad.com/leading_answers/files/original_waterfall_paper_winston_royce.pdf

Thursday, May 9, 13

Team Structure

- Silo

- Clearly responsibility

credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/

Thursday, May 9, 13

Team Discipline

• Document Oriented

• Timeline is king

• Each step has clearly definition of document standard

credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/

Thursday, May 9, 13

Individual Discipline

• Mostly make something “done” but not “right”

• Mostly said “please don’t change it”

• Mostly make it for last, not for change

http://www.flickr.com/photos/paul-w-locke/3529691660/in/photostream/

Thursday, May 9, 13

Traditional is About

Anticipation OverAdaptation

Thursday, May 9, 13

Finally

Poor Quality

Unpredictable

Lost In Translation

Burn out

Sad, Bad, ..... ?http://intothetopcorner.files.wordpress.com/2012/05/ucl-final-25.jpg

Thursday, May 9, 13

http://www.flickr.com/photos/photorisma/7999730205

Thursday, May 9, 13

AgileThursday, May 9, 13

Thursday, May 9, 13

Thursday, May 9, 13

We follow these principles:Our highest priority is to satisfy the customer

through early and continuous deliveryof valuable software.

Continuous attention to technical excellence and good design enhances agility.

Simplicity--the art of maximizing the amount of work not done--is essential.The best architectures, requirements, and

designs emerge from self-organizing teams.

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts

its behavior accordingly.

Thursday, May 9, 13

Welcome changing requirements, even late in development. Agile processes harness change for

the customer's competitive advantage.

Deliver working software frequently, from a couple of weeks to a couple of months, with a

preference to the shorter timescale.

Business people and developers must work together daily throughout the project.

Build projects around motivated individuals. Give them the environment and support they need,

and trust them to get the job done.

The most efficient and effective method of conveying information to and within a development

team is face-to-face conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development. The sponsors, developers, and users should be able

to maintain a constant pace indefinitely.

Thursday, May 9, 13

Team Structure

One single team

Break the damn silo

Thursday, May 9, 13

Team Discipline

• User first with Good Experience

• Change is good

• Eliminate unchangeable moduleshttp://www.chrislabrooy.com/UX_design.html

Thursday, May 9, 13

Individual Discipline

• Super Clear and have to follow, Make it “RIGHT”

• Test : Code : Refactor

http://www.flickr.com/photos/amberdebruin/5657750874/

Thursday, May 9, 13

Agile is About

Adaptation Over Anticipation

http://www.flickr.com/photos/12463666@N03/7256710194/

Thursday, May 9, 13

Lean

Thursday, May 9, 13

Eliminate waste

Amplify learning

Decide as late as possible

Deliver as fast as possible

Empower the team

Build integrity in

See the whole

Thursday, May 9, 13

Start using agile

Start small

Solving problem one by onehttp://www.flickr.com/photos/igal/7901479448/

Thursday, May 9, 13

Agile Methods

Extreme Programming

Kanban

Scrum

http://www.flickr.com/photos/capcase/4970062156

Thursday, May 9, 13

Whole Team?

• Same Mind set for the whole team

Thursday, May 9, 13

Thursday, May 9, 13

Synergy

Thursday, May 9, 13

Synergy

Satisfaction

Thursday, May 9, 13

Synergy

Satisfaction

Standard

Thursday, May 9, 13

Sustainable

Synergy

Satisfaction

Standard

Thursday, May 9, 13