Ibm Managing And Governing Change For Enterprise ArchitecturePresentation Transcript
Managing and governing change for enterprise architecture Bill Duncan Federal, Aerospace & Defense Telelogic Brand Software
Enterprises are global and rapidly changing
Every organization must accommodate change, whether that change is due to:
Shifting marketplace demands
Dynamic competitive environments
State of the economy
Enterprise architecture—help turn change into a competitive advantage
Enterprise architecture (EA) and enterprise planning can help organizations intelligently prepare for change and pursue successful transitions in manageable, progressive phases
Identify our comprehensive current state
Create plans to support optimization and continued improvement
Help identify the impact that our changes will make to the organization
Exploit assets of the enterprise that should effectively guide solution development and project delivery
Communicate information , analyses and decisions in rapid, continuous cycles, helping to create a smarter, more efficient organization
EA change management and governance— the foundation for migrating to the future state
Enterprise architecture should never be considered “complete”
As the business grows and evolves, so should the architecture governing its systems and processes
Architecture must remain dynamic and able to change with the demands of the business environment
The objective of the EA discipline is to deliver knowledge, facilitate the voyage and help ensure that the proper path is followed
This “living” project brings forth challenges in maintaining data and modeling consistency that:
Follow standards that were previously approved
Incorporate new technical patterns and services, information, solutions and business processes
Evolve the future-state roadmaps to reflect changes in business strategy
Enterprise architecture governance touches a large team of decision makers Architectural Vision, Transition & Vitality Architecture Blueprint Technology Scans, Assessments, Labs, Metrics, Issues, on demand Architecture Implementation Architecture Leadership Sponsored issues & opportunities Executive Committees Special Task Forces Business Direction & Opportunities IT Direction & Opportunities Technology Briefings Business Units Service Levels, Issues & Escalations Architects Operations Architect Design Develop Test Implement Projects/Solutions Lifecycle Approvals & Resources Guidance, Standards & Direction
Building an enterprise architecture—the formal approval structure
Decides on which IT is best suited for the needs of the enterprise
Decides when a change in the architecture is needed
Office of the
Ensures that solution designs comply with the architecture
Maintains the architecture
Project design authorities
Use the architecture to best satisfy the project’s needs
Architecture board Office of the chief architect Project design authorities
Architecture governance—what is appropriate for your organization?
Striking the right balance is important
The manner in which enterprise architects engage with business, solution and IT architects must fit the enterprise’s management style
Too loose can lead to inaccurate contributions and circumventing of important standards and policies
Too structured can equal “ analysis paralysis ”
Which fits your wider cultural context? Which applies to your organization now? Which will be needed in the future?
Command and control “Do what I say, and I will ensure you do”
Guide and govern “Use the architecture, and we’ll discuss those areas where it does not make sense”
Publish and trust “I know you will do your best—go do it”
And whichever style you choose, a balance will be needed
The IBM solution—Telelogic System Architect and Telelogic Change integration
Offers organizations a formal method to help manage the complexity associated with deploying EA and business process analysis (BPA) that span business and IT
Helps manage changes of models and tasks through the ability to integrate Telelogic ® System Architect ® with Telelogic Change ™ solutions
In this release, the integration can deliver the following benefits:
Help establish governance and compliance in the EA process
Better manage lifecycle customization
Support project security
Track project progress through Change reporting
Help manage the following questions in EA deployment:
Who is responsible for this change?
Why was this changed?
What is the impact of this change?
System Architect and Change: how it works— the integrated workflow
Be up and running more quickly by leveraging proven integrated lifecycle management Assign Complete Task (IR) Created Assigned Resolved Concluded Task (Work on IR) Resolve Conclude IR Set "Default" IR Assigned Validated Concluded Validate Conclude Created Assigned Reviewed Approved Applied Assign RCR Send to Review Approved Apply (In DOORS) Work on RCR Complete RCR Set "Default" RCR
How does it apply to enterprise architecture— a sample scenario System Architect approved reference architecture model Change repository “ AS IS” System Architect work space for proposed changes “ TO BE” (3) A new workspace is created (or existing identified) for the proposed work … (2) Change request (CR) is assigned by CCM to an analyst (1) A change request is created Enterprise Architect
How does it apply to enterprise architecture— a sample scenario (continued) System Architect approved reference architecture model Change repository “ AS IS” System Architect work space for proposed changes “ TO BE” (4) Analyst links work area to change request, performs work, assigns work for reviewer Business Analyst, Architect (5) Identified changes are approved and assigned to analyst to “deliver” to approved area … Enterprise Architect (6) Analyst delivers work to approved area and closes the change request Business Analyst, Architect
A tightly integrated solution—the System Architect user’s perspective
A new toolbar is introduced in System Architect
Without leaving, view a list of change requests that can be filtered per the needs of the team member
A new change review form is introduced in System Architect
Track change history
View how changes have been modified, approved or rejected over time
When you click on the change request in System Architect:
The change request launches in the Telelogic Change intuitive Web Interface
Change request details are displayed
A tightly integrated solution—change management for the architecture board
IBM Corporation Software Group Route 100 Somers, NY 10589 U.S.A.
Produced in the United States of America October 2008 All Rights Reserved
IBM, the IBM logo, ibm.com, Rational, and Telelogic are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at ibm.com/legal/copytrade.shtml
Other company, product, or service names may be trademarks or service marks of others.
References in this publication to IBM products or services do not imply that IBM intends to make them available in all countries in which IBM operates.
The information contained in this document is provided for informational purposes only and provided “as is” without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. Without limiting the foregoing, all statements regarding IBM future direction or intent are subject to change or withdrawal without notice and represent goals and objectives only. Nothing contained in this documentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM (or its suppliers or licensors), or altering the terms and conditions of the applicable license agreement governing the use of IBM software.
IBM customers are responsible for ensuring their own compliance with legal requirements. It is the customer’s sole responsibility to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer's business and any actions the customer may need to take to comply with such laws.