2. This work is based on study with Jay Sahib and related to enterprise architecture and business management. During discussing any reference to any person or organization, which resembling to real persons or organization, living or dead, is purely miracle. Disclaimer This work is based on study with Jay Sahib and related to enterprise architecture and business management. During discussing any reference to any person or organization, which resembling to real persons or organization, living or dead, is purely coincidental.
3.
4. Living in Context We are living in a context and define things with relative understanding. Seeing is believing, not always true. Context is our strength.
5. Castle – our strength or weakness We live in a castle. We think Castle is our strength. We feel safe. We are also isolated from reality.
6. We view with our context Context is our strength and is also the biggest weakness.
7. Are we living in a castle ??? Optimize the castle Change Management to change the castle from inside.
14. Big Bang approach Detect big bang approach, when you hear thing like this ERP CRM Logistic application. Cloud computing. Unified communication. Single Sign on. Business process engineering. Enterprise architecture.
15. Big bang approach They are like silver bullet. Well. We have issue because we don’t have a CRM system We have issues managing the customers, I can’t achieve my quota. Let have one. No excuses next time. We will look into it after 2 years once it is implemented.
16. Why it is attractive. Offered as silver bullet. Management knows that team has got limitation, if they start looking at the process and define the requirements, it will take time. Risk transference, no one will be fired selecting the SAP or Cisco, because they are best in the market. Offered so called best practices. He has given me the certificate, he claims it is genuine. How do you know it is Diamond. Consultant
18. Gains and issues Provide strategic leap. Major Expenditures of Funds. Lower level employees are effected Very difficult to be incremental. Installation based. Requirements based. Requirements were wrong then whole thing is screwed. Fixed Goals (to be) Deliver value when they are complete. Bought from Supplier and often become obsolete with the time
27. Path based approach. We need to get out of our Castle. Organizations are fields which can grow what you want, so you can reap the crop every season based on market need and demand. No Baobabs Intelligent destruction.
28. Path based approach. Goal is important. Rather committing the path we commit the goal. This require flexibility in terms of Technology Process Approach.
30. Path based approach Incremental. Keep the parity. Technology evolves so does the systems. Project are small and pay back immediately. If it is failed it can be discarded, no status quo issue. Allow local experimentation. Require Less Planning. Encourage team and lower staff.
31. Path based approach Allow Adoption with less complexity. Allow Local changes. Allow Select sub systems to be select from different vendors. Architecture accepts the old legacy system. System become part of whole and changed as required. Principle Based rather of fixed decision.
32. Path based approach - How Focus is important. No one person can bring the change, democracy kills the innovation, dictatorial way disturb the organization. We all need to be part of it. We need a balance. We all need to create innovation. We all need to be innovative.
34. What we are doing. Defining the context. Simple goals. Make a task simple, which people can understand and do. We also contain failure to avoid error being spread out. Task is simple to control , monitor and optimized.
35. How ??? Let the team focus on problem and find the best solution. Every one set his room in order. We look to get into fine level of granularity. Avoid centralization and aggregation. Focus on simple business model and look at the work what we are doing. Focus on what is being done and how it can be better. Introduce technology to drive the change. Continuous improvement.
36. Birds eye view Problem with birds eye view is that They always look beautiful. Block your view to understand the details. Path based works on 2-D plane rather on 3-D
37. Can you sustain ??? No aggregation. No integration. No make up. Face the reality. Simple approach. 99% KPI is not important. 1% where we are failing is important. Projected Perception Reality
38. Organization converts into set of tools Driven by set of technology, need and innovation. Intelligent destruction.
39. Change the focus to right rather left side Focus what customer need What we can sold to our customer Vendor Customer Organization Retain the value and make yourself adaptable to market need.
