Role Analysis and Evaluation Software for Education Management Nonprofit Organization
- Custom Software Development
- $200,000 to $999,999
- Nov. 2017 - Ongoing
- Quality
- 4.0
- Schedule
- 4.0
- Cost
- 5.0
- Willing to Refer
- 5.0
"I couldn't speak highly enough about them.”
- Education
- Hereford, England
- 1-10 Employees
- Phone Interview
- Verified
One Beyond (formerly DCSL GuideSmiths) developed a custom solution for a university consortium that facilitated more control over design and functionality than its previous third-party software.
Feedback from end-users was 99.9 percent positive, and internal staff were extremely happy with One Beyond's (formerly DCSL GuideSmiths') ability to translate goals into high-quality solutions. Their team established an effective workflow, offered streamlined management, and devised fresh ideas to strengthen the product.
A Clutch analyst personally interviewed this client over the phone. Below is an edited transcript.
BACKGROUND
Please describe your organization.
ECC is a slightly unusual company. It's really a consortium of different universities. We are owned and operated by members that are all universities or advanced education colleges, and each of those members pay a subscription. That's where our funding comes from, essentially. What we provide is a job evaluation system called either HERA [higher education role analysis] for universities, or FEDRA [further education role analysis], if it's for further education colleges. We also provide a range of consultancy services linked to pay and reward, and job evaluation.
What is your position and responsibilities?
I am one of the consultants, and I am the project leader for the changeover to new software, which is why we've been working with DCSL.
OPPORTUNITY / CHALLENGE
What business challenge were you trying to address with DCSL Software?
HERA has been around as a job evaluation scheme for around 15 years. It's factor specific, so it was designed for higher education institutions. We partnered up with another company that is a reward company, who also offered job evaluation, and our scheme used their software. They had millions of people worldwide who were also using this software.
It meant that we had no choice over how the software looked, how it operated, and what reports could be produced. We couldn't tailor it in any way or change it. We had an off the shelf product that supported our job evaluation scheme, and we were at the point where we realized that we needed to change that, and we needed something that we could change, own, and control. That was why we moved to finding a partner that could develop that sort of software for us.
SOLUTION
Please describe the scope of their involvement.
It was very much developing a system from scratch. That means they were responsible for helping us plan, design, develop, test, and launch. Going forward, they will be hosting the system for us and will be responsible for the upkeep, maintenance, and any further enhancements.
How did you come to work with DCSL Software?
The process started before I actually joined ECC. I joined in June 2013, and the tender process was underway already at that point. We had looked at around 20 companies, to get a sense of which companies were interested in tendering for this. We had in the area of 13 replies. At that point, we whittled it down to a list of about six, one of which was our existing supplier, but they were way out of range in terms of pricing. We very gently told them that we wouldn't be proceeding with them. That left us with five other companies from which to choose.
We did reference checks, we asked each of the companies to give us some other firms that they had worked with, and they had to complete a detailed questionnaire for us. We gave them a specification, and they told us how they would meet that specification in terms of what they could provide, and whether they thought that that would be something simple to provide or whether it was going to be a more complex piece of development, or whether it was something they would have to buy in expertise.
Then, another consultant and I checked the references that they provided. For each one, we did at least three reference calls, and then we came up with a kind of scoring process. That took us down to two companies, one of which was DCSL, and we had a final presentation day up in London in which we asked both companies to come and present. We asked them to put something together in terms of what you think this might look like going forward – give us some ideas of screens, and how you see it looking. DCSL had better ideas, they understood the brief more, and they were successful in being selected.
Could you provide a sense of the size of this initiative in financial terms?
We're around £450,000 [approximately $700,000] so far.
What is the status of this engagement?
We are continuing to work with DCSL Software. What we were looking for was a long-term partnership. It wasn't going to be just a case of them supplying the software and then walking away. We will continue to work with them, and they will host and maintain the software going into the future. We also plan to keep them involved in what we're doing, how we're developing our products, with them giving us some input into how we could develop the technical side of things to support that.
The most recent milestone completed with them was in June. All of our members had existing data on the old software platform, and part of the work that had to be done was quite an intense process of migrating that data onto the new software platform. There was a small team at DCSL that had worked with us on the development, which then also worked with us on the migration of the data. That was almost the final stage of the process.
At the moment, we've identified already, through members using the software, some system refinements. It's nothing actually that's not working. It's just things that we've looked at and determined there could be improvements. Now, it's little refinements and enhancements that they're doing. Some of them require a fair bit of coding, and that work will take us during the next few months.
In the meantime, the board of ECC are going to meet and put together an options paper for them, and we will decide which direction phase two of the project is going in. At the moment, we've got three options for what we might do next. It's up to the board to determine how we will proceed.
RESULTS & FEEDBACK
Could you share any statistics, benchmarks or user feedback from this engagement?
I can say end-user feedback is 99.9 percent positive. People just love the new system, and even if they can't work on it the exact way they used to, we've been able to show them different ways of doing things. Once they can see it's just a tweak to their process, not one of our 125 members has come back and said, "I don't like this." Everyone thinks it's great.
The project team and myself worked with DCSL Software the most, and I couldn't speak highly enough about them. They made an effort to understand what it was we were trying to achieve and what we needed the outcomes to be. We put in a lot of hours, but they put in just as many hours, specifically in terms of some of the work around the data migration, which was a fairly intensive process. They've engaged with us, they've communicated with us, they talked to us, and they always come back with solutions. They've never come back and said, 'No, we can't do that.' Occasionally they come back and say, 'Yes, we can do it but it's going to cost you a lot.' So far, there has not been anything that they haven't been able to deliver.
How did DCSL Software perform from a project management standpoint?
I think to start with, I was a bit disappointed with the quality of the project planning. What that came down to in the end was, we just needed some very frank communication. It takes some time and effort to establish an effective workflow. Once we'd had that very frank conversation, and we understood each other's point of view, then things dramatically improved. It also helped us to understand their processes and how things worked at their end. It was really about understanding each other's processes and how they impacted our timetables, and once we understood that on both sides, it was fine.
On our end, we were using GanttProject, which is a free tool. DCSL were using Microsoft Project and then converting it into a GanttProject format for us. Sometimes, we just put lists and things on spreadsheets so that we could track, so nothing overly formal. I think most importantly, we're just keeping email trails and then showing that we logged conversations.
What distinguishes DCSL Software from other providers?
We worked with a guy named Domingo [Lara], who was the project leader, and he was very responsive to us. They were very good at feeding in other ideas, and that was what we were looking for, because we didn't know what the technology could do. Quite often, they came up with better ways of doing things than we had originally planned.
I quite like the way that we worked with them, in that they built a kind of an incomplete but semi-functional prototype. We were able to see how the system would operate on a basic level, how it would look, and we used that then to build the specifications. It's been very much a hands-on, agile process. They build a bit, we test it, give them feedback but, in the meantime, they're already building the second bit. They build in the changes and then we test phase two, iteration two. That worked, it was a good approach.
Is there anything DCSL Software could have improved or done differently?
I think perhaps right at the start – from both sides now, not just DCSL – being able to understand each other's processes and setting up some realistic expectations. I think that had a huge impact. Once they understood where we were coming from and what we were trying to get to, and understood a little bit about job evaluation, it made life a lot easier for them. Once we understood how certain processes worked and how testing worked at DCSL, then it was easier from our perspective. Fortunately, you only need to go through that process once and then you're set. At this point, we are very much satisfied with them. That was a long time ago.
RATINGS
-
Quality
4.0Service & Deliverables
-
Schedule
4.0On time / deadlines
"we knew that the pilot was going to happen in February, actually the scheduling after that was two weeks ahead of deadline, so it was great. We were scheduled to finish at the end of June, and we finished mid-June, so I was happy with that."
-
Cost
5.0Value / within estimates
"The price was revised slightly about six months in but, again, that was due to us deciding to include more in phase one. As an amount, they've stuck to budget – absolutely – no problems whatsoever."
-
Willing to Refer
5.0NPS
"Absolutely no hesitation. They've been really good.