Thank you to all those who have taken the time to complete my survey.
I have now closed the survey (see my previous post) which was completed by nearly 20 people. To some extent the level of response is no surprise as anybody looking at the forums and blogs will tend to see the same interested people. I had hoped to get a few more to improve the statistical integrity but trust it will paint a useful, if rough picture. In this post when I’ve added my own comments I put them in italics, so hopefully they are clear.
I found the results have been very interesting and personally I was surprised to see how much use was made of EA other than want I tend to call the front end stuff – “requirements and modelling”. If we start by looking at the roles of the respondants, we do it is skewed towards the front end with no users who I would describe in the more downstream roles, although that may only be a reflection of their job name rather than their true role. I guess there are many “Jack of all trades”
Then we looked at use of EA within the organisation.
What we see is that it is usually more than a single person using EA and where used, its use is moderate. My interpretation is that in those organisations who have committed to use EA, we see some use beyond the team although this is not the case for all and it is purely just for the team.
When we look at the key deliverables, this started to surprise me as not only did it include those expected:
- Business and functional analysis
- Reporting – both HTML and Word
But some interesting items that implied serious technical use downstream
- Database design
- Desktop applications
- Embedded software
When we look at our level of EA expertise we see that it is higher than those within their teams and organisation. No surpise as I guess those reading the blogs and seeing this survery are those most interested EA.
Now the survey gets in a more specific. The next question related to learning EA and getting information.
The responses were interesting in that indicate that stuff is OK, but from the comments there is clearly scope for improvement. One problem I see is that EA is big, really big, and it’s potential use is so great it is a hard nut to crack. To gain valuable use of EA requires either true committment from one or more users in a team, or well designed training and guidance – or probably both. The comments also highlighted a lack of resources. I know if you look around the forums it is the same few individuals (probably you) who contribute (which I trust you enjoy doing!). In fact, EXploringEA probably wouldn’t exist if EA was well documented with tutorials, examples, and other readily available training material covering all topics of potential interest.
When we look at the most important features of EA we see that at the top of the list are the front end stuff reflecting the roles of the respondants.
Then if we look at allthe features that are used.
If we look at those areas that are only sometimes or never used we would start to take out:
- Team management tools
- Model simulation
- Execution analyser
Now if this was a true reflection of EA usage it would be a concern. The ability to have a single repository of information throughout the project, tracking from the requirements and design to the implementation and testing is highly desirable. Furthermore, having accurate information downstream to support ongoing maintenance is essential. I can only guess that a some stage of the project information is moved to other tools which are then used moving forward to support the product during it’s lifecycle – let’s hope!
What I can gather from comments is that there are some really useful features of EA. There were comments for most areas, especially those in the areas where there is not a high use. Here is a subset:
- Database – “Great for quick re-engineering “
- Automation – – “deploying and operating something in addition to EA is something they usually do not want.” Reflecting the challenge associated with using AddIns.
- Project management – “I think it can be a good alternative to never-updated projects created in Microsoft Project, but its UI is too technical for the minds of PMs, and therefore may never gain popularity”. No surpise that PM’s don’t want to change. I developed an EA addin for MS Project but found that project managers weren’t really interested in using EA, so a I then produced an addIn for MS Project that accesses EA but still not much interest. If I was in their shoes why would I change, what more am can I gain. One further point is that the project management capabilities within EA look great for managing say a development team but do not cater for the broader business project management, planning and reporting; nor should they!
- Team management – “I haven’t or hardly found any well-developed use case and user story scenarios models at my clients. Because of this, testing features are of no value for them, until they understand why an up-to-date model with detailed requirements and scenarios are important” Interesting in that I think a lack of real detailed examples really is a limiter. If there were real world examples which were well crafted and could be mapped to current working practices it would be great. I guess that the problem here is that this would be valuable intellectual property and hence nobody is able to provided… Anybody have ideas on what could be done?
- Maintenance – “Roadmapping works well. Trick is to have as-is and to be changes at the start end end of change dependency diagram.” It was great to see this comment as it really implies somebody is doing the right thing and managing the work from requirements to deployment and ongoing maintenance.
What is missing from EA?
The comments included:
- Better Excel support – I will start with this as I have a personal investment in eaXL and see that this can do a lot – perhaps we haven’t communicated enough detail (!), so let us know what is needed and you never known. And, now Sparx have their own Excel tools.
- Intergration with other tools – notably publishing tools to make information available to a wider audience. Although HTML is available organisations how their own preferred tools.
- “Stop changing the UI in every release”
- “A streamlined report/template editing facility, which enables manual editing, with a great UI, such as those you can find in visual query builders.”
I think I can summarise a sense of the feedback from one of the final comments:
“Great tool – but I think it tries to expand its scope too much”
Also in trying to do so much “some features need to be sharpened” – which apparently comes from a domain expert indicating that in adding some features they were not accurate in meeting the real need.
So there we have it. For me, I’ve had some interesting reading which has generated some ideas for furture exploring and posts. In the meantime, I’d like to thank those who took the time to contribute to the survey, and trust that you find this feedback useful.