WBISCT Pty Ltd – Enterprise Architecture Consulting and Training

Exploring Commonalities Between TOGAF and Scrum

Enterprise Architecture and Agile methodologies often seem worlds apart, each with its own set of principles and frameworks. However, a closer examination reveals that TOGAF (The Open Group Architecture Framework) and Scrum share several commonalities that can be leveraged to enhance organisational effectiveness. Let’s delve into how these two frameworks intersect and complement each other.

Understanding TOGAF and Scrum

TOGAF EA (10th ed.) is a comprehensive framework for developing and managing enterprise architecture. It provides a high-level approach to design, planning, implementation, and governance of enterprise information architecture. The framework is divided into four domains: Business, Application, Data, and Technology, ensuring a holistic view of the organisation’s architecture encompassing, contextual EA capability building, trade off analysis, secure by design cyber security coverage etc.

Scrum, on the other hand, is an Agile framework primarily used for software development. It emphasises iterative progress through small, cross-functional teams working in time-boxed sprints. Scrum’s core elements include roles (Scrum Master, Product Owner, Development Team), artifacts (Product Backlog, Sprint Backlog, Increment), and events (Sprint Planning, Daily Standup, Sprint Review, Sprint Retrospective) .

Commonalities Between TOGAF and Scrum

Despite their different focal points, TOGAF and Scrum share several foundational concepts that can facilitate their integration:

  1. Iterative Development and Continuous Improvement
    Both TOGAF and Scrum advocate for iterative processes. In TOGAF, the Architecture Development Method (ADM) is cyclic, promoting continuous architecture development and refinement. Similarly, Scrum’s iterative sprints aim for incremental progress and continuous improvement through regular feedback loops .
  2. Focus on Stakeholder Engagement
    Effective stakeholder engagement is crucial in both frameworks. TOGAF emphasises understanding and addressing stakeholder needs throughout the architecture development process. In Scrum, stakeholder involvement is integral during sprint reviews and planning sessions, ensuring that the product aligns with business requirements and customer expectations.
  3. Emphasis on Collaboration and Communication
    Collaboration is a cornerstone of both TOGAF and Scrum. TOGAF encourages collaboration among various architectural domains and business units to create a cohesive architecture. Scrum fosters collaboration within the Scrum team and with stakeholders through daily stand ups, sprint reviews, and retrospectives, enhancing transparency and collective ownership .
  4. Alignment with Business Objectives
    Both frameworks aim to align IT initiatives with business goals. TOGAF’s ADM process ensures that architecture development is driven by business requirements, ensuring strategic alignment. Scrum’s iterative approach allows for regular reassessment of priorities, ensuring that the product development remains aligned with evolving business needs.
  5. Scalability and Flexibility
    TOGAF provides a scalable framework (ref to DPBoK) that can be adapted to different organisational sizes and complexities. Scrum, while originally designed for small teams, can be scaled using approaches like Scrum of Scrums or the Scaled Agile Framework (SAFe). This flexibility allows both TOGAF and Scrum to be tailored to the specific needs of the organisation, promoting scalability and adaptability .

Leveraging TOGAF and Scrum Together

Integrating TOGAF and Scrum can provide significant benefits, combining the strategic perspective of TOGAF with the agility and responsiveness of Scrum. Here are some ways to leverage both frameworks:

  • Agile Enterprise Architecture: Use TOGAF to establish a robust architectural foundation and apply Scrum principles to manage architectural work iteratively. This approach ensures that the architecture evolves in line with changing business needs and technological advancements.
  • Enhanced Communication: Facilitate better communication between enterprise architects and Agile development teams. Regular interactions can ensure that architectural guidelines are adhered to while allowing for flexibility in implementation.
  • Stakeholder Alignment: Employ TOGAF’s stakeholder management techniques alongside Scrum’s regular stakeholder engagements to ensure continuous alignment with business goals and stakeholder expectations.

Conclusion

TOGAF and Scrum, though distinct in their primary focus areas, share several common principles that make them complementary when integrated effectively. By leveraging the strengths of both frameworks, organisations can achieve a balanced approach that combines strategic architectural planning with agile execution, ultimately driving better alignment with business objectives and enhancing overall organisational agility.

For organisations looking to stay competitive in today’s fast-paced digital landscape, understanding and integrating the commonalities between TOGAF and Scrum can provide a powerful foundation for both stable and agile operations.