agile adoption story in lge (aps2010)
TRANSCRIPT
생산성연구원
심우곤 선임
@wgshim
1/46
2/46
Health Care
3/46
Health Care
4/46
Company Overview
• Vision: “Global Top 3 IT Company by 2010”
• Size: globally 84,000+ employee (2008 year)
– Domestic: 28,659– Oversea: 55,786
5/46
Development Characteristics
• End Products (HW + SW) – Stretched (fixed) schedule + fixed requirements
• Global launching• Defects after release, cause recall!!• Portion of SW is increasing more and more!
• Short development schedule• Bitter competition of market• Develop multiple models, concurrently• Reflect market/customer needs, rapidly
6/46
7/46
The key is
Professionalism!
9/46
10/46
The Boy Scout Rule!
“Leave the campground cleaner than you found it”
-- Robert C. Martin, “Clean Code”
TDD (Unit Test), Refactoring
At the first time,Bottom Up Approach!
Just Focuses onNew & Changed Features
14/46
15/46
Plan
• Select one team• Give 2 (full) day lecture• Select 2~3 developers (active & fresh)• 3+ month on-site coaching
16/46
Actual
• Ported UTF on our develop. environment.• Got a few “Unit Tested” features• Refactoring a key feature of a module
• Tried to apply mock without readiness of HW or 3rd party library• Gave some seminars (1 hr, 15 times) what they
frequently made mistakes.• Built some scripts and tools for them.
17/46
Lessons Learned
• Hard to work with developers (Busy!!)• Close relationship is important• Need to give some values to them
Everyday with Bad Code!!
22/46
ME
Select one whole modulefor showing as an example!
24/46
25/46
Plan
• Select a whole module + one developer– Ownership & Validation on target
• Give half day lecture• 1 month (6+ month: maintenance)
26/46
Actual
• Ported UTF on our develop. environment.• Made a Best Practice– Extract core logic from
UI and HW dependent code– 400+ automated unit test cases– 100% (statement) code coverage– All regression test takes < 1s– Used as a company-wide standard
27/46
Lessons Learned
• Easy to progress and achieve• Hard to spread it• A few people feel better for using this way
• TDD, Unit Testing is not easy!! (2 year experience)
• Still NAH syndrome!
Next Step: Combining with Scrum
29/46
Last Year
• Just support only volunteer team– Visibility and light-weight process : SCRUM!– Strong commitment, but bottom-up approach
• As simple as possible è on demand– Trust them!
• Share and Follow by themselves!
30/46
31/46
Current Status
• A few Scrum teams launch XP practices
• Unfortunately, top down approach!– Top manager doesn’t care what it is.
Journey of our team
33/46
2004 2006 2008 2010200920072005
김 창준(애자일 컨설팅 社)
“Agile, XP”
Software 6σSoftware 6σ
Agile, XPAgile, XP
34/46
2004 2006 2008 201020092007
James W. Grenning(Object Mentor 社)
“Extreme Programming Immersion for
Embedded Software Developers”
2005
Software 6σSoftware 6σ
Agile, XPAgile, XP
Embedded AgileEmbedded Agile
35/46
2004 2006 2008 201020092007
Bas Vodde(Odd-e 社)
“Certified ScrumMaster”
2005
Software 6σSoftware 6σ
Agile, XPAgile, XP
Embedded AgileEmbedded Agile
ScrumScrum
36/46
2004 2006 2008 2010200920072005
James W. Grenning(Renaissance Software Consulting 社)
“TDD in C”
Software 6σSoftware 6σ
Agile, XPAgile, XP
Embedded AgileEmbedded Agile
ScrumScrum
TDD in CTDD in C
37/46
2004 2006 2008 2010200920072005
James W. Grenning(Renaissance Software Consulting 社)
“Agile Embedded Design in C”
Software 6σSoftware 6σ
Agile, XPAgile, XP
Embedded AgileEmbedded Agile
ScrumScrum
TDD in CTDD in C Design Principles(embedded)
Design Principles(embedded)
38/46
2004 2006 2008 2010200920072005
Rebecca Wirfs-Brock(Wirfs-Brock Associates 社)
“Agile Development and Design:Principles and Best Practices”
Software 6σSoftware 6σ
Agile, XPAgile, XP
Embedded AgileEmbedded Agile
ScrumScrum
TDD in CTDD in C Design Principles (embedded)
Design Principles (embedded)
Design PrinciplesDesign Principles
39/46
2004 2006 2008 2010200920072005
Software 6σSoftware 6σ
Agile, XPAgile, XP
Embedded AgileEmbedded Agile
ScrumScrum
TDD in CTDD in C Design Principles (embedded)
Design Principles (embedded)
Design PrinciplesDesign Principles
Bas Vodde(Odd-e 社)
“Certified ScrumMaster”+
Agile and Lean for PM
40/46
2004 2006 2008 2010200920072005
2004 2006 2008 2010200920072005
41/46
2004 2006 2008 2010200920072005
2004 2006 2008 2010200920072005
42/46
2004 2006 2008 2010200920072005
2004 2006 2008 2010200920072005
43/46
2004 2006 2008 2010200920072005
2004 2006 2008 2010200920072005
Lean SigmaSix Sigma
6σLean
Waste EliminationWPPM
44/46
Thank You!
Q & A
Appendix
http://www.agilejournal.com/content/view/411/33/
The 5 Levels of Agility populated with Agile Practices and ConceptsAhmed Sidky
TDDPair Pgm.
Unit Test