The Open Group Architecture Forum
Show/Hide Plato Messages   You are here:  > Architecture Forum > Documents > TOGAF® Series Guide Business Capabilities, Version 2
Register Here

Submit a Presentation
Title: TOGAF® Series Guide Business Capabilities, Version 2
Version: None

The review will officially commence on July 1, 2020, and end on July 29, 2020. The document is currently posted and ready to receive your comments early. 

I hereby assert that this submission satisfies the Standards Adoption Criteria.
+ The commenting but not balloting review group will be all Forums, Work Groups, and interested parties within The Open Group membership.
+ The change request review group will be The Open Group Architecture Forum.
+ The balloting group will be The Open Group Architecture Forum. The Ballot will be over the proposed resolutions put forward by the sponsor

Summary: Many organizations struggle with managing the complexity of their business. They want to answer questions about their progress toward realizing their strategic aims. Are their strategic investments targeted appropriately? Are there areas of redundancy or duplication that are suitable for rationalization? Does the business have what is necessary, or too much to succeed?

As the discipline and practice of Business Architecture continues to grow and mature, the concept of the “business capability” has emerged to become a fundamental component in the development of a Business Architecture. The business capability map represents one of the four core elements of Business Architecture, along with the value stream map, information map, and organization map. 

Business capabilities provide an abstraction of the business reality in a way that helps to simplify conversations between interested stakeholders. Defining a business capability’s supporting components (people, processes, information, and tangible resources) provides a business context for those supporting components. In addition, creating a business capability map for the enterprise promotes more of a common understanding of the business.

Defining business capabilities and a capability map is a means to an end. Understanding a business’s capabilities provides architects and planners with a foundation for making better business decisions. This insight is gained through mapping the business capabilities to different business perspectives and viewpoints. The mapping allows for a more coherent view of the business to emerge.

This document looks to answer some important questions about what a business capability is, and how it is used to enhance business analysis and planning:

  • What exactly do we mean by the term “business capability”?
  • Why are business capabilities such an integral part of Business Architecture and Enterprise Architecture, and the architecture development process?
  • How do we describe business capabilities?
  • How (and why) should we construct a business capability map?
  • How do business capabilities map to other business perspectives

Proposed Timeline :

June 17 Announce Company Review 
June 17 - July 29 Document Review period 
July 30th -TBD  Sponsors to address change requests 
TBD - Ballot period 

How to Participate: Members are requested to review the draft Standard/Certification document and submit Change Requests (CRs) that they consider will make the document acceptable or otherwise improve it. CRs shall be submitted using the online review system and must be received by the closing date. 

You will be asked to supply your username and password to access the review materials. In case you need a reminder on your username and/or password.
+ Click on the tag where you want to add your Change Request
+ Fill in all areas (click on HELP if additional information is necessary)
+ When viewing the HTML/tagged file, there are links at the top of the page that you should be aware of: “Help with Document Review” – provides detailed instructions on entering and editing CRs. “Comments” – provides a table with the existing comments from all reviewers.  

Procedure: 
1. All requests for modifications must be submitted via The Open Group Review System in the form of formal change requests. 
2. The CRs will be adjudicated by the sponsoring forum.
3. The proposed resolutions will be circulated to the sponsoring forum along with the Ballot table. 
4. All members entitled to vote shall submit their vote by email for EACH submitted proposal within the agreed period. The ballot results will be circulated after the end of the ballot period.
5. Further discussion of the unresolved change requests during an agreed period may occur for an agreed limited period to seek a clear majority decision. Eventually, only changes that achieve 75% approval will be accepted.

Change Requests: To ensure completeness, please submit change requests via the Plato Review System in the following standard format:
+ Title: Short title describing the request
+ Qualifier: Nature and severity of the change request:

  • Severity: Minor, Major, Critical

  • Nature: Editorial, Technical

+ Rationale: Reason the change is needed
+ Change: Identify the precise text/diagram to be changed (added, deleted, or modified), and specify the exact changes proposed. Changes lacking specific editing instructions may be rejected. If necessary, the change can be included in an attachment. There is an additional COMPANY IDENTIFIER field (eg CorpCom-001), to be filled in. This field helps us identify the member organization that made the change request in order to support the resolution process.

If there are any questions concerning this review, please contact forum-support@opengroup.org.

Created by: k.cannon on 17-Jun-20
   |   Legal Notices & Terms of Use   |   Privacy Statement   |   Top of Page   Return to Top of Page
  PHPlato: 2.0 (466) [p]