Book Image

Realize Enterprise Architecture with AWS and SAFe

By : Rajnish Harjika
Book Image

Realize Enterprise Architecture with AWS and SAFe

By: Rajnish Harjika

Overview of this book

Agile implementation of enterprise architecture (EA) in the cloud is a powerful organizational tool, but it is challenging, particularly for architects who are used to on-premises environments. This in-depth guide will tell you all you need to know to reap the benefits of applying EA in your organization to achieve operational efficiency. Starting with an overview of the foundations of enterprise architecture, you'll see how it can be applied to AWS as well as explore the frameworks AWS provides for EA, such as the AWS Well-Architected Framework. That's not all – the book shows you how these frameworks align with The Open Group Architecture Framework (TOGAF) architecture development method (ADM) and the Zachman Framework so that you can choose the right fit for your organization. As you advance, you'll learn how to apply SAFe to make your organization agile as well as efficient. Once you've gotten to grips with the theory, you can explore use cases and take a quiz at the end of the book to test yourself and see how EA is applied in practice. By the end of this enterprise architecture book, you'll have the skills and knowledge required to apply EA in the cloud with AWS and drive your organization to become super-efficient and agile.
Table of Contents (17 chapters)
1
Part 1 – Enterprise Architecture Foundation and Implementation
5
Part 2 – Enterprise Architecture Frameworks
9
Part 3 – SAFe in EA and the Cloud
12
Part 4 – Setting Up an EA

Adopting an agile approach with epics

The concept of an epic refers to a large body of work that can be broken down into smaller stories, which Jira sometimes refers to as issues. Multiple teams can work together on multiple projects, and multiple boards can be used to track multiple epics at once. Usually, a set of sprints precedes an epic. The user stories of an epic will be added and removed as the team learns more about it through development and customer feedback. Essentially, agile epics adopt a flexible scope based on customer feedback and team cadence.

A good epic should provide all the resources a development team needs to succeed. As far as their work hierarchy is concerned, it is the top tier. While understanding how an epic fits into other agile structures is critical for directing the daily developer work, it also provides important context for evaluating epics.

The act of breaking down an epic into smaller pieces makes it easier to understand and maintain momentum...