Agile
Upcoming SlideShare
Loading in...5
×
 

Agile

on

  • 912 views

 

Statistics

Views

Total Views
912
Views on SlideShare
912
Embed Views
0

Actions

Likes
1
Downloads
35
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile Agile Presentation Transcript

  • An Alternative SoftwareDevelopment MethodologyTwin PanichsombatThursday, May 9, 13
  • Twin PanichsombatAgile PractitionerOdd-e(Global)Thursday, May 9, 13
  • Thursday, May 9, 13
  • Thursday, May 9, 13
  • About MeThursday, May 9, 13
  • About MeThursday, May 9, 13
  • 2001?Thursday, May 9, 13
  • Thursday, May 9, 13
  • Thursday, May 9, 13
  • Thursday, May 9, 13
  • Software Developmentin my perspective(before)http://www.flickr.com/photos/eleaf/2536358399/in/photostream/Thursday, May 9, 13
  • ConstructionArchitectEngineeringLabor WorkThursday, May 9, 13
  • ConstructionSoftware ArchitectSoftware EngineeringSoftware Worker (programmer)Thursday, May 9, 13
  • We were forced tobelieve in that.Thursday, May 9, 13
  • How many ways can weconstruct the building?http://www.flickr.com/photos/danslegrandbleu/4365319943/Thursday, May 9, 13
  • How many ways can weconstruct software?http://www.flickr.com/photos/joedsilva/4698703312/Thursday, May 9, 13
  • Software is about businesshttp://www.flickr.com/photos/standhere/462675095/Business never stopSoftware must “SOFT”Thursday, May 9, 13
  • Craftsmanshipcredit-http://www.flickr.com/photos/stevensnodgrass/6117660537/Thursday, May 9, 13
  • !Craftsmanship.isEqualTo( Cowboy)Thursday, May 9, 13
  • “Methodology”Thursday, May 9, 13
  • MethodologyThursday, May 9, 13
  • MethodologyTeam StructureThursday, May 9, 13
  • MethodologyTeam StructureTeam DisciplineThursday, May 9, 13
  • MethodologyTeam StructureTeam DisciplineIndividual DisciplineThursday, May 9, 13
  • The greatest traditionalhttp://www.flickr.com/photos/38019504@N04/5101530474/Thursday, May 9, 13
  • http://leadinganswers.typepad.com/leading_answers/files/original_waterfall_paper_winston_royce.pdfThursday, May 9, 13
  • Team Structure- Silo- Clearly responsibilitycredit-http://www.flickr.com/photos/stevensnodgrass/6117660537/Thursday, May 9, 13
  • Team Discipline• Document Oriented• Timeline is king• Each step has clearly definition of documentstandardcredit-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 changehttp://www.flickr.com/photos/paul-w-locke/3529691660/in/photostream/Thursday, May 9, 13
  • Traditional is AboutAnticipation OverAdaptationThursday, May 9, 13
  • FinallyPoor QualityUnpredictableLost In TranslationBurn outSad, Bad, ..... ?http://intothetopcorner.files.wordpress.com/2012/05/ucl-final-25.jpgThursday, May 9, 13
  • http://www.flickr.com/photos/photorisma/7999730205Thursday, 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 customerthrough early and continuous deliveryof valuable software.Continuous attention to technical excellenceand good design enhances agility.Simplicity--the art of maximizing the amountof work not done--is essential.The best architectures, requirements, anddesignsemerge from self-organizing teams.At regular intervals, the team reflects on howto become more effective, then tunes and adjustsits behavior accordingly.Thursday, May 9, 13
  • Welcome changing requirements, even late indevelopment. Agile processes harness change forthe customers competitive advantage.Deliver working software frequently, from acouple of weeks to a couple of months, with apreference to the shorter timescale.Business people and developers must worktogether 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 ofconveying information to and within a developmentteam is face-to-face conversation.Working software is the primary measure of progressAgile processes promote sustainable development.The sponsors, developers, and users should be ableto maintain a constant pace indefinitely.Thursday, May 9, 13
  • Team StructureOne single teamBreak the damn siloThursday, May 9, 13
  • Team Discipline• User first with Good Experience• Change is good• Eliminate unchangeable moduleshttp://www.chrislabrooy.com/UX_design.htmlThursday, May 9, 13
  • Individual Discipline• Super Clear and have to follow, Make it “RIGHT”• Test : Code : Refactorhttp://www.flickr.com/photos/amberdebruin/5657750874/Thursday, May 9, 13
  • Agile is AboutAdaptation OverAnticipationhttp://www.flickr.com/photos/12463666@N03/7256710194/Thursday, May 9, 13
  • LeanThursday, May 9, 13
  • Eliminate wasteAmplify learningDecide as late as possibleDeliver as fast as possibleEmpower the teamBuild integrity inSee the wholeThursday, May 9, 13
  • Start using agileStart smallSolving problem one by onehttp://www.flickr.com/photos/igal/7901479448/Thursday, May 9, 13
  • Agile MethodsExtreme ProgrammingKanbanScrumhttp://www.flickr.com/photos/capcase/4970062156Thursday, May 9, 13
  • Whole Team?• Same Mind set for the whole teamThursday, May 9, 13
  • Thursday, May 9, 13
  • SynergyThursday, May 9, 13
  • SynergySatisfactionThursday, May 9, 13
  • SynergySatisfactionStandardThursday, May 9, 13
  • SustainableSynergySatisfactionStandardThursday, May 9, 13