Más contenido relacionado
Similar a Offshore Software Patterns. ALE Berlin (17)
Más de Mads Troels Hansen (8)
Offshore Software Patterns. ALE Berlin
- 1. Offshore Software Patterns
What system must be in place?
ALE 2011, September 2011
Mads Troels Hansen
Fujitsu Denmark
© 2009, 2010, 2011 Mads Troels Hansen Rev 07092011, ALE
- 2. Employees Customer
Shareholders
• Why patterns for offshore development?
– Avoid/limit common global problems
– Improve Thrust, Quality, Productivity and ROI
© 2009, 2010, 2011 Mads Troels Hansen 2
- 3. A pattern, simplistically put, is a
solution to a problem in a context.
A pattern language is the
sequence of patterns (graph) and the
patterns Drink
Often
Get Share
Water Water
Save
for later
http://www.hillside.net/patterns
http://www.scrumplop.org
• Main Patterns described using the form
– Problem. Therefore, Solution.
xxxxx
© 2009, 2010, 2011 Mads Troels Hansen 3
- 4. Balance
• 9 Main Patterns and 27 Related Patterns
• My own experience with Distributed Work (since 2004)
– Primarily Asia and Eastern Europe
© 2009, 2010, 2011 Mads Troels Hansen 4
- 6. ”Too many managers with
multiple directions and
bottlenecks”
• Main Pattern
Global
Management
System
© 2009, 2010, 2011 Mads Troels Hansen 6
- 7. Global
Management
System
• Patterns
Step back and Establish
Do Gemba
design ONE Fast Problem
Walks Offshore
global system Solving
© 2009, 2010, 2011 Mads Troels Hansen 7
- 8. ”Many offshore
<resources> and Mistrust”
• Main Pattern
Global
Structure
© 2009, 2010, 2011 Mads Troels Hansen 8
- 9. Global
Structure
Demand Throughput
• Patterns
Design
Establish Daily Balance Demand
Global Value
Transparency and Capacity
Streams
© 2009, 2010, 2011 Mads Troels Hansen 9
- 10. ”Deadlines not respected
and finding bugs late”
• Main Pattern
Global
Rhythm
© 2009, 2010, 2011 Mads Troels Hansen 10
- 11. Global
Rhythm
• Patterns
Implement Regular Fast
Incremental Sneak Feedback
and Iterative Previews Culture
© 2009, 2010, 2011 Mads Troels Hansen 11
- 12. ”Complex and labor-
intensive deployments”
• Main Pattern
Global
Technical
Infrastructure
© 2009, 2010, 2011 Mads Troels Hansen 12
- 13. Global
Technical
Infrastructure
• Patterns
Simplify then Baseline core Teach the
Automate standards infrastructure
© 2009, 2010, 2011 Mads Troels Hansen 13
- 14. ”Global Meetings are
painful and waste of time”
• Main Pattern
Global
Communication
Protocols
© 2009, 2010, 2011 Mads Troels Hansen 14
- 15. Global
Communication
Protocols
• Patterns
Establish Meeting
Daily Video
Communication purpose and
Meetings
Toolbox owners
© 2009, 2010, 2011 Mads Troels Hansen 15
- 16. “Problems with quality
code and DONE”
• Main Pattern
Global
Development
Practices
© 2009, 2010, 2011 Mads Troels Hansen 16
- 17. Global
Development
Practices
• Patterns
Global Code
Define Global Global Source
Review
DONE Control
Cadence
© 2009, 2010, 2011 Mads Troels Hansen 17
- 18. “Requirements are
misunderstood”
• Main Pattern
Global Req
Management
© 2009, 2010, 2011 Mads Troels Hansen 18
- 19. Global Req
Management
• Patterns
Do Slice and
Communicate
Requirement Iterate
the onion
Validation understanding
© 2009, 2010, 2011 Mads Troels Hansen 19
- 20. “Wrong Business
Understanding”
• Main Pattern
Global
Domain
Knowledge
© 2009, 2010, 2011 Mads Troels Hansen 20
- 21. Global
Domain
Knowledge
• Patterns
My background Tell stories
Build Shared
is not your about the
Domain models
background obvious
© 2009, 2010, 2011 Mads Troels Hansen 21
- 22. “We are not working
together and it is more us
and them!”
• Main Pattern
Cross cultural
understanding
© 2009, 2010, 2011 Mads Troels Hansen 22
- 23. Cross cultural
understanding
• Patterns
Rotate Find People Shared view on
People with a Global behaviors and
Frequently Mindset standards
© 2009, 2010, 2011 Mads Troels Hansen 23
- 24. Offshore Software Patterns
Global
Global Global
Development
Management Rhythm
Practices
System
Global
Global Technical
Structure Infrastructure Cross cultural
understanding
Global
Global Req.
Domain
Management
Knowledge
Global
Communication
Protocols
WHY to work Global HOW to work Global WHAT to Deliver Global
© 2009, 2010, 2011 Mads Troels Hansen
- 25. mth@lean-agile.dk
blog.lean-agile.dk
@madsth
Offshore Software Patterns
“Real solutions to common Offshore Software
problems that arise in different contexts”
© 2009, 2010, 2011 Mads Troels Hansen 25