Book a Demo

This webinar has completed, the recording will be posted shortly.


Digital transformation, new business models and the rapid pace of change have had a profound impact on the modern enterprise. Agile approaches can lead to faster feedback cycles, improved stakeholder engagement, reduced waste, improved transparency, predictable delivery and better business outcomes.

The Sparx Systems tool suite supports enterprise agility through better collaboration, strategic management, capability modeling, Kanban diagrams, user stories, integrated communication tools, project management features, traceability and much more.

In this webinar, we'll show you how to:


Don't miss this opportunity to learn more about Enterprise Architect

Session 1

Melbourne Fri 29 Mar 08:00 am
New York Thu 28 Mar 17:00 pm
Los Angeles Thu 28 Mar 14:00 pm
London Thu 28 Mar 21:00 pm
Auckland Fri 29 Mar 10:00 am

Session 2


Scott HebbardCommunications Manager
Sparx Systems
Chris ArmstrongSparx Services North America

Explore the webinar resources

Webinar Part 2 ‐ Strategy and Enterprise Architecture, presented by Chris : webinar-demo1.mp4 Download links
Webinar Part 3 ‐ Delivering An Agile Enterprise, presented by Scott: webinar-demo2.mp4 Download links
Download Christ's Presentation Slides: ssna-delivering-enterprise-agility.pdf Download links

Questions & Answers


Enterprise Architect 14,1, Build 1428.

For more information, see the Sparx Services North America website, email [email protected], or call Toll-Free: +1 (800) 882-6051.

Yes, they are available on this page under Webinar Demonstrations and Resources.

Yes, images for element stereotypes can be created in two ways:

  • Alternate images.
  • Shape Scripts.

You can use alternative images to represent UML Stereotype or model element. For details, see the Help topics on Alternate Images and the Image Manager.

UML elements and connectors each have a standard appearance, in terms of shape, color and labeling. It is possible to change the appearance of a type of element or connector in a number of ways, using a Shape Script to define the exact feature you want to impose on the default - or main - shape. For details on creating your own Shape Script, see the Help topic Getting Started With Shape Scripts or the webinar on Extending Enterprise Architect.

Delivering an Agile Enterprise

The webinar discussed a variety of models to represent business or enterprise architecture, including UML, BIZBOK® , ArchiMate® Specification, TOGAF® Standard, BPMN and many more.

For a comprehensive discussion of Enterprise Architecture, see the Agile Enterprise Architecture web page.

A Guide to the Business Architecture Body of Knowledge® (BIZBOK® Guide) provides an industry standard framework for business architecture practitioners who wish to use business architecture to address business challenges.

The BIZBOK® Guide was used in the airport model to describe everything from corporate strategy and Capability Maps through to Value Maps and stakeholder value.

SCRUM is an agile framework for managing knowledge work and software development. Part of the webinar examined tools like Burndown Charts and Kanban diagrams that can be used to manage aspects of sprints, daily stand-up meetings and general resource management. Other topics were not covered in detail due to time constraints.

We also looked at User Stories and building documentation from reverse engineering. Chris also spoke about achieving business agility through understanding business motivations, modeling factors that drive business and building a coherent strategic plan.

Tools from Sparx Systems - Enterprise Architect and Prolaborate provide the ability for users to adapt the tool to any development methodology. Enterprise Architect allows custom profile definitions and there are a number of Agile based profiles available in the community. Sparx Systems Prolaborate facilitates dashboard creation to keep track of the user stories, sprints, burndowns, backlogs and test cases. Thus a combination of Enterprise Architect plus Prolaborate could be a good fit to bridge the gap between Agile tools and modeling tools.

For details, see the Help topic Scrum and Support for Agile Methods.

WebEA and Pro Cloud Server

Yes. You can view past webinars from our Webinar Library. Some popular webinars on the Pro Cloud Server include Setting Up Pro Cloud Server for Enterprise Architect and 6 Steps to Socialize Enterprise Architect Models.

Depending on which type of database is used for the model repository, you can use the Visibility Levels feature to restrict or hide parts of the model.
For more information on Visibility Levels, see the Help topic Visibility Levels.

Users can edit the model with WebEA by creating Packages and elements and updating their properties, but editing of diagrams is not currently supported by WebEA. For details, see the Help topic WebEA Quick Start Guide.

When you drag one diagram onto another, Enterprise Architect automatically prompts you to drop the diagram as a standard text hyperlink. One of the options includes a Navigation Cell. Using a Navigation Cell is ideal for models viewed in WebEA, as it makes it easy to navigate your model on a Tablet, mobile device or web page.

For details on how to create a Navigation Cell, see the Help topic Add Diagram Links To Diagrams.

The Pro Cloud Server family now includes a new modular integration capability that is tightly connected with Enterprise Architect.

A variety of integration plugins are currently available that include:

  • Application Lifecycle Management
  • Autodesk
  • Bugzilla
  • Dropbox
  • Jira
  • Jazz
  • Share Point
  • Service Now
  • Team Foundation Server
  • Wrike

For more details, see the Help topic Integrate Data from External Providers.

Architecture, ROI and User Story

One simple, but tactical, way to frame the ROI in actual dollars saved is to frame the financial and risk benefits of being able to do rapid impact analysis with high levels of confidence. In many organizations, when there are major initiatives, a whole bunch of people get together for a several day offsite meeting to go over what the impact is expected to be based on all stakeholders' perspectives. So, if there are an average of 10 people involved in such efforts and this occurs 20 times per year, one could calculate the cost of just doing impact analysis as such:

10 people x 3 days x 8 hours/day/person x $50/person/hour x 20 times/year = $240,000/year spent just on impact analysis.

Then when you couple that with the uncertainty about the confidence of the planning efforts, it's not unusual to find that we still miss things, which surprise us late in the lifecycle and at that stage are often expensive risks to resolve and result in additional rework.

A more strategic perspective is to consider the risk of not doing Business Architecture and the historical evidence you can point to where, if effective Business Architecture had been in place, you might have been able to deliver better outcomes (better solution, less money, less time, lower risk, etc).

If we think of this the way many people manage (or do not manage) their retirement portfolio, sometimes you get lucky making uninformed decisions, but usually you do not. You consult professionals with specialized skills, training, and experience that empirically evaluate your portfolio and provide recommendations based on your strategy. Why would we want to not manage our transformation investments in a similar fashion? Again, maybe you'll get lucky, but anecdotal evidence suggests that is a pretty capricious risk management philosophy for delivering strategic initiatives.

Another way to frame it is not so much about the ROI of Business Architecture, but what is its value proposition? From the BIZBOK&#reg; Guide v7.5:

'The value of business architecture is to provide an abstract representation of an enterprise and the business ecosystem in which it operates. By doing so, business architecture delivers value as an effective communication and analytical framework for translating strategy into actionable initiatives. The framework also enhances the enterprise's capacity to enact transformational change, navigate complexity, reduce risk, make more informed decisions, align diverse stakeholders to a shared vision of the future, and leverage technology more effectively.'
For more details, see the Help topics on Types of Architecture and the Characteristics of Good Architecture.

You can use the multi-stage Kanban diagram pattern for assigning User Stories first to a Product Backlog and then promote them to a Sprint Backlog to assign them to a specific sprint. For details, see the Help topic MDG Technology for Kanban.

You can break User Stories into Tasks by either:

  1. Create Task elements as child elements for each User Story element. For more information, see the Help Topic on the Maintenance Diagram.
  2. Create Task elements as elements in their own package, possibly one package per sprint, and trace the Tasks to the User Stories using Relationship Matrices. For details, see the Help Topic Relationship Matrix.
  3. Use the Construct view to define tasks and allocate them to individuals. For details, see the Help Topic Task Management.
  4. Use the Maintenance views to define tasks.

You can manually add a 'Points' Tagged Values to a User Story. SSNA has implemented an extension to the built-in Kanban diagrams for Agile development teams that includes this and other features. Please contact SSNA at [email protected] if you're interested in more details.

share this page share by email share on linkedin share on X share on facebook