- Rate of increase in Technological Complexity should be less than rate of increase in Business Complexity
- Continual siloed Changes
- Conservation of familiarity for technical and business persons
- Feedback based continuous learning and un-learning
- Trap business and technical event and then take action
- Be disruptive as whole but not in incremental fashion.
- Adhere to Standards for benefits not for sake of adherence
2. Design Operators of “Modular” SOA
- Splitting: Services can be made independent
- Substituting: Services can be substitutes and interchanges
- Excluding: Existing services can be removed to build a usable solution
- Augmenting: New Services can be added to create new Composite services and/or processes
- Inverting: Hierarchical and composition dependencies among services can be rearranged ( most difficult)
- Porting: Called Service is independent of calling service.
3. Lean SOATM
- Eliminate Waste: Spend time and resources only what add real customer value
- Amplify Leaning: Tougher the problem, increasing the feedback
- Decide as Late as Possible: Keep options open as long as practical (not possible)
- Fail early, fail frequent: Use increment development & deployment
- Deliver as fast as possible: Deliver value to customer as soon as customer asks
- Empower the team: People are intelligent, encourage them to contribute
- Build Integrity: Most of the time, shortest route is not the best route
- See the Whole: Beware of the temptation to optimize parts at the expense of whole.
No comments:
Post a Comment