... for Project Managers

So the analysts and designers want to use EA and eaDocX. But what's in it for you - the Project Manager? Sounds like just another tool to get in the way of getting things done.

What you need to know is "are we making progress?" and "what can I tell my stakeholders?" "Can I get early visibility of progress on deliverable documents?" And "will they help monitor the quality of what's being done?"

With EA and eaDocX, you can get answers to all these questions and more.


  • Monitoring Progress.

A great way to see progress is to produce an eaDocX report each week listing all the 'things' your team should be defining: could be Use Cases or Components, Classes or Requirements. Then you can see how their numbers increase over time. It's a safe bet that if the numbers are still on an upward slope, we're probably not done, no matter what you're being told. 

  • Supporting Stakeholders.

With eaDocX you can create documents and reports that include any of the information held in EA, and select exactly where the documents should focus. So, for example you could produce a document for a single stakeholder which includes everything that person is linked to. Or produce a summary report for senior stakeholders with  key information automatically highlighted, or detailed documents for team meetings.

  • Managing meetings

Whether you need management reporting for regular progress meetings, milestone reviews or meetings for one-off issue resolution, you can quickly generate documents from EA containing exactly (and only) the information you need. eaDocX has lots of document structures and formatting options to give you exactly what you need.

  • Early Document Versions. 

Historically, this has been hard work. It's bad enough that BAs have to produce a final document, without you demanding interim ones as well.
But with eaDocX, as soon as the final document structure has been designed, you can pull out a 'where are we today' version as often as you like, and actually see how near to complete the document is. And your team don't need to break off to do it. You can even send it yo yourstakeholders, to show them what progress you are making.

  • Quality Checking.

This is a real challenge for any analysis/design project. How can we define what 'quality' is? Mostly it will be about the quality of the content, and here again letting eaDocX pull out regular versions of documents, and tailoring documents for different stakeholder groups will let them see what's going on.
eaDocX can also help by adding cross-references within documents, so it's clear, for example, which Requirements don't have an owner, or which Use Cases aren't implemented by a Process.

  • Risk and Issue Management.

​Capturing Risks in your EA model and linking them to all their related elements allows clarity for impact assessment as well as the stakeholders involved. Export your Risks from EA into an Excel spreadsheet - update it in the meeting then import it back into EA. Then you can keep everything in one place

  • Business Benefits Delivery.

Traceability of designed features back to the business case can become challenging and it's easy to lose focus when down in the detail. eaDocX can provide clear visibility to senior stakeholders to help them understand the significance of individual requirements and the solutions that will deliver them - giving you more tools to get the support you need to focus on delivering the project priorities.

So not only will your team be happy to be using the best tools available, but it's also going to improve your ability to understand what's happening in your project and then focus on getting it delivered.

Lets be clear, you won't use it for cost and schedule control. But you can use it for pretty much everything else.