Becoming a real application engineer thanks to OutSystems
Updated October 29, 2019
Becoming a real application engineer thanks to OutSystems
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with OutSystems
We've recently created a scrum team to create a new "client following system" using OutSystems. So for now it's just one department using OutSystems. Our old, legacy system does not serve our needs anymore and is not flexible at all. So with OutSystems we are building a new one from scratch. Two of us are new to OutSystems (and IT) and learned to use it in a few months. We hired three external experts to build and teach the juniors, so we could start building and delivering value immediately.
- Being low-code, even people without any experience can start building with OutSystems immediately.
- OutSystems has a great and very helpful community, giving advice and pre-build features to beginning engineers.
- OutSystems is very flexible and easy to use; it enables us to build something useful within minutes.
- Being relatively new in the IT world, I could use some kind of quick reference guide inside OutSystems (instead of going to the website or forum)
- Filtering aggregates could perhaps be done in an easier way. I struggle with them, sometimes.
- I'd like more pre-made layouts.
- OutSystems helps us becoming agile.
- With OutSystems we can deliver value every two weeks instead of having to wait months for a new update.
Easier to learn and use. More flexible.
Do you think OutSystems delivers good value for the price?
Yes
Are you happy with OutSystems's feature set?
Yes
Did OutSystems live up to sales and marketing promises?
Yes
Did implementation of OutSystems go as expected?
Yes
Would you buy OutSystems again?
Yes
OutSystems Feature Ratings
Using OutSystems
4 - Our company has a scrumteam, in which we have developers, testers, a scrum master and a product owner. We have four developers in our team; these are the persons using OutSystems. We have two senior developers and two junior developers, at the moment. The software we create using OutSystems is used by the entire company (about 90 people) and our client (a few thousand).
2 - Our team of developers consists of two external engineers and two full time in-house engineers. They need to know the OutSystems system (and preferably have an 'associate developer' or even 'professional developer' certificate) to be able to support OutSystems.
- Replacing our legacy software system
- Building new software to support our business processes
- Monitor our business processes
- We might use OutSystems to build more and other software
Evaluating OutSystems and Competitors
Yes - Before we started with OutSystems, we uses Microsoft Navision. We decided to replace this, because it became a not-so-flexible legacy software package, which we were not able to adjust ourselves. We needed a product which would offer us a way to develop new software to replace the old software, at a fast pace and with an ease of use. With OutSystems, even developers with little experience are able to build good, working software, which is highly flexible and easy to maintain.
- Product Features
- Product Usability
The most important factor to choose OutSystems was the fact that it's a Low-Code platform, so we could train in-house employees - without much software developing experience to use it and build with it. Besides, OutSystems is the perfect system to use in combination with an agile way of working. The scrum framework gives us the opportunity to deliver new working pieces of software every two weeks, making it possible to expand our new software over time while using the software at the same time.
We wouldn't.
OutSystems Implementation
- Implemented in-house
Change management was a minor issue with the implementation - It is very important to manage people's expectations. Employees expected a finished product straight away, while the OutSystems team was told to build a mvp at first. So when presenting the mvp software, there was some disappointment in the business. Also, we had some developers from our old software platform, who were not really giving OutSystems a chance. So with them, there should have been a better talk before making them OutSystems engineers.
- Expectations
- Unwillingness to change
OutSystems Support
| Pros | Cons |
|---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
There was one incident where we accidentally lost a part of our database. This was on a Friday afternoon. We had no real hopes things would be solved before the weekend, but we got a call back immediately after we sent in a support ticket. The OutSystems support helped us getting a backup of our missing date and guided us through getting it back in our live database. So before the weekend, everything was solved. Amazing.
Using OutSystems
| Pros | Cons |
|---|---|
Like to use Relatively simple Easy to use Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- Create websites
- Create (web) applications
- Debugging is sometimes troublesome
Yes - The mobile interface works great. OutSystems has prefab and custom mobile interfaces, all very easy in usage.