1. An Alternative Software
Development Methodology
Twin Panichsombat
Thursday, May 9, 13

2. Twin Panichsombat
Agile Practitioner
Odd-e(Global)
Thursday, May 9, 13

3. Thursday, May 9, 13

4. Thursday, May 9, 13

5. About Me
Thursday, May 9, 13

6. About Me
Thursday, May 9, 13

7. 2001?
Thursday, May 9, 13

8. Thursday, May 9, 13

9. Thursday, May 9, 13

10. Thursday, May 9, 13

11. Software Development
in my perspective
(before)
http://www.flickr.com/photos/eleaf/2536358399/in/photostream/
Thursday, May 9, 13

12. Construction
Architect
Engineering
Labor Work
Thursday, May 9, 13

13. Construction
Software Architect
Software Engineering
Software Worker (programmer)
Thursday, May 9, 13

14. We were forced to
believe in that.
Thursday, May 9, 13

15. How many ways can we
construct the building?
http://www.flickr.com/photos/danslegrandbleu/4365319943/
Thursday, May 9, 13

16. How many ways can we
construct software?
http://www.flickr.com/photos/joedsilva/4698703312/
Thursday, May 9, 13

17. Software is about business
http://www.flickr.com/photos/standhere/462675095/
Business never stop
Software must “SOFT”
Thursday, May 9, 13

18. Craftsmanship
credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/
Thursday, May 9, 13

19. !Craftsmanship.isEqualTo( Cowboy)
Thursday, May 9, 13

20. “Methodology”
Thursday, May 9, 13

21. Methodology
Thursday, May 9, 13

22. Methodology
Team Structure
Thursday, May 9, 13

23. Methodology
Team Structure
Team Discipline
Thursday, May 9, 13

24. Methodology
Team Structure
Team Discipline
Individual Discipline
Thursday, May 9, 13

25. The greatest traditional
http://www.flickr.com/photos/38019504@N04/5101530474/
Thursday, May 9, 13

26. http://leadinganswers.typepad.com/leading_answers/files/original_waterfall_paper_winston_royce.pdf
Thursday, May 9, 13

27. Team Structure
- Silo
- Clearly responsibility
credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/
Thursday, May 9, 13

28. 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

29. 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

30. Traditional is About
Anticipation Over
Adaptation
Thursday, May 9, 13

31. 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

32. http://www.flickr.com/photos/photorisma/7999730205
Thursday, May 9, 13

33. Agile
Thursday, May 9, 13

34. Thursday, May 9, 13

35. Thursday, May 9, 13

36. We follow these principles:
Our highest priority is to satisfy the customer
through early and continuous delivery
of 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

37. 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

38. Team Structure
One single team
Break the damn silo
Thursday, May 9, 13

39. Team Discipline
• User first with Good Experience
• Change is good
• Eliminate unchangeable modules
http://www.chrislabrooy.com/UX_design.html
Thursday, May 9, 13

40. 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

41. Agile is About
Adaptation OverAnticipation
http://www.flickr.com/photos/12463666@N03/7256710194/
Thursday, May 9, 13

42. Lean
Thursday, May 9, 13

43. 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

44. Start using agile
Start small
Solving problem one by one
http://www.flickr.com/photos/igal/7901479448/
Thursday, May 9, 13

45. Agile Methods
Extreme Programming
Kanban
Scrum
http://www.flickr.com/photos/capcase/4970062156
Thursday, May 9, 13

46. Whole Team?
• Same Mind set for the whole team
Thursday, May 9, 13

47. Thursday, May 9, 13

48. Synergy
Thursday, May 9, 13

49. Synergy
Satisfaction
Thursday, May 9, 13

50. Synergy
Satisfaction
Standard
Thursday, May 9, 13

51. Sustainable
Synergy
Satisfaction
Standard
Thursday, May 9, 13