38
An Alternative Software Development Methodology Twin Panichsombat Proficient Software Craftsman Opendream™ Saturday, September 22, 12
| Date post: | 15-May-2015 |
| Category: |
Technology |
| Upload: | - |
| View: | 1,379 times |
| Download: | 2 times |
An Alternative Software Development Methodology
Twin PanichsombatProficient Software Craftsman
Opendream™
Saturday, September 22, 12
Saturday, September 22, 12
Software Development ?
Saturday, September 22, 12
ConstructionArchitect Engineering
Labor Work
Saturday, September 22, 12
ConstructionSoftware Architect
Software Engineering Software Worker (programmer)
Saturday, September 22, 12
We were forced to believe in that.
Saturday, September 22, 12
How many ways can we construct the building?
Saturday, September 22, 12
How many ways can we construct software?
Saturday, September 22, 12
As long as, user can change , adjust software
to fit into their requirements.
Saturday, September 22, 12
Craftsmanship
credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/
Saturday, September 22, 12
!Craftsmanship.isEqualTo( Cowboy)
Saturday, September 22, 12
“Methodology”
Saturday, September 22, 12
Methodology
Saturday, September 22, 12
Methodology
Team Structure
Saturday, September 22, 12
Methodology
Team Structure
Team Discipline
Saturday, September 22, 12
Methodology
Team Structure
Team Discipline
Individual Discipline
Saturday, September 22, 12
The greatest traditional
Saturday, September 22, 12
The greatest traditional
Saturday, September 22, 12
Team Structure
- Silo
- Clearly responsibility
credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/
Saturday, September 22, 12
Team Discipline
• Document Oriented
• Timeline is king
• Each step has clearly definition of document standard
credit-http://www.flickr.com/photos/stevensnodgrass/6117660537/
Saturday, September 22, 12
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/
Saturday, September 22, 12
Traditional is About
Anticipation OverAdaptation
Saturday, September 22, 12
Finally
• Our software is same as building. Once it done you can’t change it.
• Lost In Translation
• Unable to predict
• Sad, Bad, ..... ?
Saturday, September 22, 12
We need change!
Saturday, September 22, 12
AgileSaturday, September 22, 12
Saturday, September 22, 12
Team Structure
One single team
Break the damn silo
Saturday, September 22, 12
Team Discipline
• User first with Good Experience
• Change is good
• Eliminate unchangeable moduleshttp://www.chrislabrooy.com/UX_design.html
Saturday, September 22, 12
Individual Discipline
• Super Clear and have to follow, Make it “RIGHT”
• Test : Code : Refactor
http://www.flickr.com/photos/amberdebruin/5657750874/
Saturday, September 22, 12
Agile is About
Adaptation Over Anticipation
http://www.flickr.com/photos/12463666@N03/7256710194/
Saturday, September 22, 12
Start using agile
Start small
Solving problem one by onehttp://www.flickr.com/photos/igal/7901479448/
Saturday, September 22, 12
Agile Methods
Extreme Programming
Kanban
Scrum
http://www.flickr.com/photos/capcase/4970062156
Saturday, September 22, 12
Whole Team?
• Same Mind set for the whole team
Saturday, September 22, 12
Saturday, September 22, 12
Synergy
Saturday, September 22, 12
Synergy
Satisfaction
Saturday, September 22, 12
Synergy
Satisfaction
Standard
Saturday, September 22, 12
Sustainable
Synergy
Satisfaction
Standard
Saturday, September 22, 12
