Are we as successful as we could be? That's most probably always the question that the managers ask themselves when they look into their figures of last year. And is that actually the right question? Questions about the result (did we make enough money? Is this a good product?) are of course valid questions. But I wonder. Questions about how we came to that results (like: did we develop this the right way? ) are more out of the ordinary (at least in my opinion), isn’t it? Does anyone care? As long as the functionality is there, isn’t that enough?
We find that ISV solutions are successful domestically .. when implemented by the ISV itself, acting like its own VAR. But when the product is taken out away from the people who developed and originally implemented it .. doing successful projects becomes suddenly increasingly difficult.
So, in general, we must be doing something wrong, right? And it has to do something with the design of the product, right?
Furthermore, there is a lot around the corner. The ERP world is changing dramatically:
· NAV opens up to the .Net community
· Cloud-based computing (we're all in .. but in what, exactly?)
· App-like functionality
· Volume deals become more and more important (and definitely a focus)
Is NAV ready for this brave new world?
Is "Navision" becoming NAV's legacy system - and should everyone be warned for this?
These are concerns that we have tried to put into a context .. and which we will try to guide people in the right direction for in the future.
Who are we?
From left to right: Gary Winter (agiles), Eric ‘waldo’ Wauters (iFacto) and Mark Brummel (BrummelDS).
If you might wonder .. we're definitely not different than you. We're just people that happen to be in the NAV channel for a very long time .. that most probably made more "mistakes" than any of you did. But working with lots of developers and implementers, made us realize that "thinking in another way" might be useful to the channel.
What does PRS mean?
Well, "Partner Ready Software" is not a company .. so it's not competition in any way :-). It's just an initiative, an attitude, an approach, a concept .. a series of guidelines if you will.
But about what?
Well .. a product is not created by doing "development" only. We're looking at:
· Project implementation
"Partner Ready Software" (PRS) is about every single one of these steps, bringing closer together, to form some kind of coherence between these steps.
And to avoid any confusion: it's not that we claim to have all the answers! It's not a ready-made set of tools. It's NOT a dogma!
What are our goals?
We just want to make your life more profitable by trying to have you create software instead of solutions. We want to establish a professional industrial production process to turn your NAV verticals into volume-deal enabled software (something that Microsoft sure wants to see happen).
But that's quite high-level, isn't it? May be a bit more understandable. We would like to bring fresh ideas and concepts to the NAV architecture and coding.. . We would like to establish re-engineering strategies to make NAV verticals and the core product more app-like and we would like to show ways of establishing coherence and consistency in the complete process from business case to coding.
What do you mean, app-like?
We realize that many of us are building big "mountains" of solutions. What we would like to do is break those "mountains" down to small and big "stones" (which are actually pieces of functionality/software that act more independantly .. more app-like :-)).
The partner as a customer
Bottom line .. we would like you to see your partner (who is actually going to sell your software) as a customer. It's your partner that is going to have to be able to sell your product. It's the partner who is going to have to expand it .. enhance it .. upgrade it .. . So, the ease of implementation is going to be very important. It's in fact what is going to sell your product to your customer, the partner.
What have you been doing?
Well, until now, we have formed our scope: what do we want to do, and what do we want to achieve. More into detail, we did a session about PRS on NAVTechDays (of which you will be able to download the slides very soon). We went more into detail on the architecture and development part, and we noticed that these "fresh ideas" were much appreciated. So let's keep the flow flowing .. you'll here from us! As a guest columnist, I (waldo) will be posting parts of PRS to this column.
In the meantime, here are some referrals:
· Website: www.partner-ready-software.com
· Follow us on Twitter: prsNAV
· Like us on facebook: Partner Ready Software
· LinkedIn: under construction
· Waldo’s Blog: www.waldo.be
· Mark’s Blog: www.brummelds.com
· Gary’s Blog: under construction
Hope you're going to tune in, and follow us where ever we'll go :-).
Great story. These are very often questions in development. I am sure that PRS is possibly. I just prepare something like this and I will share my experiences.