Embed Size (px)
Citation preview
www.intelliware.com 2
The Story
•The problem•Our team’s solution•The process adjustments we made to make it work
•Next time …
www.intelliware.com 4
The Problem
We were asked to add …
•A new functional module; and• Integrate it with a new ESB
www.intelliware.com 6
The Problem
With some constraints …
•Minimize impact of change•Limited availability of developers with experience on the legacy system
•Maximize extensibility of new feature module
www.intelliware.com 8
Our Solution
Component Based Approach• Change to legacy system ↓• Coupling between systems ↓• Extensibility of new components ↑
www.intelliware.com 9
Our Solution
Bounded Context• “An operational definition of where a particular model is well-
defined and applicable” Eric Evans 2011
• Multiple models of a business entity• The model lives in its context• Separate artifacts, separate teams
www.intelliware.com 11
Our Solution
Component Sub-teams• Legacy system expertise ↓• Design ownership ↑• High level system understanding ↑• Integration & coordination ↑
www.intelliware.com 12
Process Adjustments
Stories for Clients• Same old …• Maybe a bit more fine grained
www.intelliware.com 13
Process Adjustments
Component Capabilities for the Team• High level design• Development estimate• Many to many – capabilities to stories
www.intelliware.com 15
Process Adjustments
Iteration Steering• Balancing of functional story and component capability
perspectives• Yesterday’s weather based on component capability velocity• Increased developer participation
www.intelliware.com 17
Next Time
• Explicit mapping of component capabilities to stories• Sub-team secondments• Get QA process input earlier• What do you folks suggest?
