The Open Group Architecture Forum
Show/Hide Plato Messages   You are here:  > Architecture Forum > Documents > TOGAF® Series Guide - Applying the TOGAF® ADM using Agile Sprints
Register Here

Submit a Presentation
Title: TOGAF® Series Guide - Applying the TOGAF® ADM using Agile Sprints
Version: None

The review will officially commence on April 16 and end on May 14, 2020. For your convenience, 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: The purpose of this document is to show how Scrum sprints can be used to:

· Collaboratively apply Enterprise Architecture and the TOGAF Architecture Development Method (ADM) following an Agile approach

· Create an architecture tuned for use together with Agile practices

· Support and collaborate with Agile teams for a given product

· Enable Enterprise Architects to leverage an Agile practice to assure that the Agile delivery of a product is in alignment with strategic objectives and takes into account the existing landscape

This document illustrates how you can use a pattern for situational engagement with all the stakeholders of a product in varying Agile states. When we create great products, we combine analysis and synthesis from system thinking with innovation and intuition from design thinking. We allow the stakeholders (internal, external customers, business, architecture, and solution teams) to together become the designers. This is sometimes referred to as the “Third Generation of Design”.

Proposed Timeline:
April 2 Announce Company Review 
April 2 - May 14 Document Review period 
May 15 -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 are open to (mis)interpretation. 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 02-Apr-20
   |   Legal Notices & Terms of Use   |   Privacy Statement   |   Top of Page   Return to Top of Page
  PHPlato: 2.0 (466) [p]