![]() It’s likely that we’ll dive deeper into the relationship between SAFe and business architecture and provide more clarity of how the two disciples come together on a midterm horizon. ![]() Though when exploring the discipline of capability modeling, the nuance between the two definitions disappears, the terms in common usage may cause confusion early on. In a SAFe context, the delivery of a capability requires collaboration between more than one ART.Ĭapability, as defined in business architecture: An expression of what a business does and can do. Another potential source of capabilities is the Solution Context, where some aspect of the environment may require new solution functionality. In the context of this post, it’s important to understand the difference between how business architecture and SAFe use the word “capability.”Ĭapability, as defined by SAFe: Artifacts that may originate in the local context of the solution or occur as a result of splitting portfolio Epics that may cut across more than one value stream. The business architect is responsible for developing artifacts that help the organization operationalize strategy and assure the operational and technological enablement of core capabilities across value streams. The role of business architecture is to provide clarity of how an organization’s capabilities and infrastructure come together to deliver business outcomes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |