Home / About Portfolio Manager

About Portfolio Manager

From the team that brought you the worlds best selling extensions for Sparx Systems Enterprise Architect, eaDocX and Model Expert. Developed by EA users for EA users, Portfolio Manager makes single model version control easy.

Why did we write Portfolio Manager?

Portfolio Manager was created to answer the question, “why can’t I see what other projects are doing?”

Our experience of working in environments where there are typically between 40 and 60 projects in flight at the same time, and those projects often delivering change in the same area of the business, it is impossible for everyone to work in a controlled way in the same model. As a result we have to take copies, work separately, and then merge once the work is finished – only then to discover that the baseline has changed and we need to rework.

Frustrated by this waste of time and effort, and after working with many other clients facing the same problem, we realised thre had to be a better way. A way for every project to work with copies of the baseline in their own dedicated area, but see what other projects are doing and who is working on the same parts of the model. With that knowledge available early in the process, modellers and projects can discover how to work with each other instead of competing or contradicting. And to have a simple way to take each element through it’s lifecycle, integrated with the project lifecycle.

So that’s what Portfolio Manager does:

  • Checks who else is working in the same part of the model,
  • Flags where there are potential problems and
  • Provides you with detailed information about the issues at element, project and portfolio level

So modellers and project teams can have the conversations they need with the other projects.

And Gives model managers visibility of element roadmaps and planned changes to the model baseline.

We have always said that EA should be the single version of the truth for organisations.

Now that many projects can all be modelled in a single repository, that day comes one step closer.

Meet the team

Ian Mitchell

Business Analyst & Portfolio Manager Developer

I graduated in 1983 from Oxford with a degree in Engineering, which means I could start from Schrödinger’s Wave Equation and prove a wheelbarrow, but couldn’t actually engineer anything.

I started out with IBM – first in their development lab in the UK. As some of the people I worked for were almost 40, this was clearly a job for old people, so I moved over to customer-facing roles building what were then called client-server systems, that were obviously going to take over the world. It’s here that I got interested in how software got built, especially Object Oriented software, which was in its early stages of commercial use.

On one project, I managed a team of 20 Smalltalk programmers – in the days when Smalltalk was cool, and was definitely going to take over the world – and co-wrote a CASE (Computer Aided Software Engineering) tool (ironically) called GOOSE – Graphical Object Oriented Solution to Everything. For this, me and my co-authors shared an IBM “Outstanding Innovation Award”, due to the huge amount of money which the project saved by using the tool. It would be great to say that the tool was then adopted by IBM, and we all went on to become rich and famous, but it didn’t, and we didn’t. It got lost in the internecine wars that are IBM product development, and we all wandered off to do other things. Sigh.

The experience did, however, give me a life-long interest in how engineering-style approaches can be used to create better business applications. Yes – I really am interested in this. (Don’t tell my children though – they already think I’m sad.)

After that I worked for a few years as a consultant and mentor for QA Training, then the UK’s largest – and best – IT training company. I looked after, and was part of, a team of trainers who went out to customer sites to give advice on adopting OO techniques. During this period I worked with dozens of customer projects - Airlines, Insurance, Banking and Government - and saw how the use of a few hours from an independent ‘expert’ could make a big difference to a project. This is why I’m a real fan of the idea of project mentors, who can stop projects from re-inventing ideas which already exist, and giving them a sounding-board for new plans.

At the end of this period, QA produced the first ever UML (Unified Modelling Language) course, and for a while this was the focus of my mentoring work, using a variety of other CASE tools. It’s at this point I started to call myself a Business Analyst. That was 10 or so years ago.

Since then, I’ve been an independent consultant, working as a BA for telecoms companies mostly in the UK, and doing occasional teaching – I wrote a UML course for a client, which I’m still adding-to and using.

It was during one of these projects that I first came across Enterprise Architect. I was the UML-specialist in a small team of BAs, who were writing the Use Cases for a telecoms system. EA was then – and still is – a fraction of the price of competing tools,. It really should take over the world.

Our project also wrote its own document generator, to take the information from our EA model and produce all the documents for the project. Like many EA users have done before, this was a series of Word macros, which needed a programmer to make changes, but which showed me the difference which a document generator can make to an EA project.

So, in a gap between projects, I totally re-wrote the initial generator to be an EA add-in, and eaDocX was finally born. That was in 2012, and we're still selling eaDocX today.

After working with various clients, I realised that often the reason their generated documents often didn't look as they expected was that the source models were not consistent. Data was missing or put in different places, and connected in different ways. And that usually happened when there were large teams all adding to the model using their own favourite modelling standards. So I developed Model Expert, initially as a way to sense check and fix existing models, and then it expanded into providing help to stop those mistakes happening in the first place.

And now... Portfolio Manager, written to solve another of those long standing problems - how to manage multiple projects in a single EA repository. Whatever time is left I spend planting and chopping down trees on our 45 acre farm in the Black Mountains¹, and spend most days listening to BBC 6 Music. The former is proving a timely reminder of my skills as an OO programmer, and why I prefer being a business analyst.

Our hope for Portfolio Manager is that (1) every EA user will buy it and then (2) managing multiple projects in EA will become so much better - with real-time visibility of the whole modelling landscape for everyone.

...and (3) Portfolio Manager, Model Expert and eaDocX will take over the world, so I can go and get a real job making furniture, which is much more interesting than all of the above.

Oh, and somewhere in all that, I got married to Jackie (the eaDocX CTO, CMO, & CEO) who is a project manager and a real-life Rocket Scientist, and we have two daughters.

¹Yes- I know this adds-up to more than one job. Just look at the timestamps on my emails to see how this is done...

Jackie Mitchell

Team Rocket Scientist

I studied Physics (yes really) at Oxford University, before starting my career working in Space - first as a satellite design engineer, then project manager. I loved the technology, out of this world (!) problem solving, engineering design and manufacturing, all of this within a highly regulated and structured environment.

Being part of a multi-disciplinary team and achieving great things was hugely satisfying - even though to get our projects operational, we had to place them on a large complicated firework and light the blue touch paper, and sometimes that didn't go quite to plan...

On leaving the Space world I got an MBA from the University of Bath then set up and ran a management training and consulting company. I enjoyed the work, and helping people to improve their skills, but missed the technology and being part of a large team, so returned to project management with Airbus. There, I project managed an international team designing and building A380 wing structures and components. Again, a highly structured environment where delivery had to conform to rigorous change management and configuration control systems...

After Airbus I moved into telecoms and IT. In these industries I have managed IT and IVR systems developments, contact centre infrastructure changes, web platform upgrades, multi channel fulfilment (integrated ordering, contract management and delivery systems for phones via web, contact centres & in stores) and customer loyalty programmes. These have included not only implementing new technology but also introducing business and organisational changes.

You could say my career has been on a permanently downward trajectory, from Giotto (outside our Solar System) via weather satellites in earth orbit, via aircraft at 35,000 feet, to ground level with mobile phones.

But regardless of the altitude, in every case I have needed to understand the technology, the people, the processes, the politics, the business case, the risks, the operations and much more, just to deliver... and keep my stakeholders happy with the information they needed.

I was amazed, on entering IT, to discover how relatively un-structured and uncontrolled so much development was. Compared to my engineering experience, information was often incomplete and usually scattered through various departments, tools and peoples heads. Delivering projects was more an art than a science. Thinking was unstructured and solutions often had unexpected consequences, as they were developed and deployed in a vacuum (like Space, only different...) without reference to the rest of the business.

But then I discovered Enterprise Architect - and how much it could have helped.

Why did my BAs not tell me about this? A proper tool to do REAL SOFTWARE ENGINEERING. Now I feel much more at home. And with all the engineering data in one place, I can build my Project Management work on a firm foundation.

EA can hold and connect business and technical information, and with the addition of eaDocX, Model Expert and Portfolio Manager, EA modellers have the tools to really make EA a "Single Version of the Truth", with improved flow of information and improved delivery of projects and programmes.

I know what hard looks like. I am a rocket scientist! And wherever possible I want an easy life...

I think that EA combined with Portfolio Manager (and eaDocX and Model Expert) just might make that possible, and give me more time for Rugby (supporting Wales, of course), making music, and a million and one things I haven't quite got around to yet.

Ability Engineering

Portfolio Manager is sold by Ability Engineering Ltd, a UK based Company providing Training, Mentoring and Talent for Business Analysis and Management to the IT, mobile telecoms, finance and aerospace industries.

Portfolio Manager has been developed for use in these environments, to cope with changing requirements, multiple releases, complex international environments and demanding stakeholders.

We know the challenge of managing multiple projects in EA. Now we have the solution – Portfolio Manager.

Pricing and features

Find out what’s included…

Check out Pricing

Download Portfolio Manager

Take a free, no obligation, 30-day trial today. Discover for yourself the difference that Portfolio Manager real-time impact analysis will make to your EA modelling.

Download