"Issue reported to our bugs team."

[QUOTE=bartho;]Hello,

Issue reported to our bugs team.

regards,
Bernhard Bernsmann[/QUOTE]

Is this phrase meant to softly close a thread, or will we ever hear back about the status? I think that the translation is actually “Go away. If I pretend somebody cares about your problem then maybe you will stop posting”. Sorry Bernhard, I mean no offense saying this, I know you are trying to be helpful.

What happened to Thomas in the past two weeks? He was giving us really good status information, reproducing problems, offering suggestions, communicating to the development team and then the bugs got fixed. It looks like customer support is spiraling back down to its state 3 months ago. Its a shame.

Most of the customers of NetMake are in exactly the same business as NetMake is: We design, develop, market, sell and support software to paying customers.

One big difference between NetMake and customers like myself is probably best summed up by my company’s policy on Customer Service: [B]

We listen to our customers. They use our software every day in the real world, so they know the good and bad of it. Customers give us valuable feedback at no cost to us. They are not only our lifeblood, but valued members of our Design Team.[/B]

I need to give my customers better customer support and quicker response than they can get from my competitors, otherwise they will go someplace else. Maybe not today, because my product is the superior product today, but my competitors are working hard to have the superior software product. Being in the software business is much more than simply having a software product. Companies differentiate themselves in other ways. I could never, ever tell my customers “Issue reported to our bugs team.” and expect them to accept that as the last thing they ever hear about the problem. I would be creating an unhappy customer that will leave as soon as a viable alternative exists.

Put very simply:


good customer support = customer loyalty;
customer loyalty = more sales;

When a software product is initially being developed, it evolves as the brainchild of the developers. They know what it is that they have envisioned, and they set about creating that product. However, post-release development, enhancements, feature evolution, etc. are all driven by the market. That is the purpose of the existence of Product Managers. They keep their fingers on the pulse of the marketplace, compare features to the competition, encourage feedback from their major and most experienced customers and using all of this information, they create a roadmap for the future of the product. This cannot be done in a vacuum. Letting developers establish the roadmap of a product based upon what they “feel like working on” is a major mistake. They are employees, they are not paying customers. Prioritization of the product roadmap must include customer feedback, otherwise you end up with a “really cool” widget that nobody wants to buy.

I would really love to see a chart of ScriptCase sales over the past few years. I would bet a month’s pay that somebody is concerned about increasing the level of sales at this point. Is it such a big secret that customer satisfaction drives sales?

Aducom spent time and energy setting up a Mantis site to track the status of bugs (in English). Nobody from NetMake participates. This forum also has very little participation from NetMake.

I really have to ask, does senior management at NetMake have any idea of the serious level of customer dissatisfaction and the potential backlash? I cannot believe that senior management is totally incompetent, so I must conclude that they are simply unaware of the customer dissatisfaction.

In closing let me say that I think that ScriptCase is potentially a stellar product. I also think that NetMake has the potential to be a stellar company. The only thing needed for these two things to achieve their potential is a change of priorities by someone who cares.

Sorry if I have rambled on, but I depend on Scriptcase. Just as I would be upset if the performance of my electricity supplier was less than adequate. I depend on them as well, not just for my company’s success, but the success of all of my employees. Keep in mind, NetMake, that your actions affect the lives of many thousands of people in far-flung countries.

Dave

Well said Dave. I could not explain the concept better. I think that many here are in complete agreement with you.

I have to agree too. God only knows how much time I invested in moving SC into the right direction… And I will continue to do so.

We all appreciate your efforts, Albert. I hope that nobody takes my post the wrong way - I love Scriptcase, and I have no intention to give up on it or NetMake. Sometimes I just need to vent my frustration. :slight_smile:

Dave

That’s good … but if it helps? We will see, but only very small steps …

Excellent speach. :slight_smile:
+1

jsb

I agree.
Seems that nobody from Scritpcase read the forum …

I agree. Our post are for SC every day be much better. We Love SC. +1

‘’ Issue reported to our bugs team. ‘’

Hello,

I was busy in recent times, so I could not give attention to the forum, sorry everyone.

Now I will return to my activity and try to help everyone possible.

Thanks for understanding and encouragement to create a better tool every day.

Thank you!

I was a customer of SC a few versions ago (I believe either v5 or v6) and the issues were the same then… so much that after a few months I got a refund. I check back because the product is nice and was able to develop quickly, but responses and support weren’t far from good… guess much hasn’t changed seeing all the bugs and sporadic support.

I started using SC 6 and I have to disagree. There has absolutely been made progress. But it doesn’t mean that things are 100%, and there is still a lot to be improved.

Yes, indeed a lot changed from version 6, as a software that keeps being changed and updated its very unlikely that it’ll be 100% anytime soon.
We’re always seeking to make a better tool and keep it updated with new technologies and with the needs of our costumers.

Sometimes we’re too busy to leave a reply, but we do read the forums, but even the simplest things needs some bureaucracy.
We need to keep tracking of all things: old bugs, new bugs, improvements, suggestion and stuffs and you all help us improve this tool.

Well, the major issue is communication and quality control. I agree that every tool will have bugs, but it’s completely uncertain which issues are acknowledged as bugs, which are (being) solved and old bugs regularly re-appear, which makes me suspicious that the csv system (check-in/out) is not working properly. You still lack a beta test team. And I think that a lot of issues should have been discovered at your quality control in stead of the community/customers. Before deployment you simply need to create a test script to check if all is still working well… Especially obvious functionality like this. When I say you made progress then I mean the latest decision of scriptcase to stop developing new functionality, but work on fixing bugs only. But these fixes have caused a lot of new bugs, see the forum.

There are a lot of “bugs” that are actually new features or a change of the actual implementation. But when a costumer reports something we note it down (when its not a bug) and check later if it fits the software, if adding it to the tool will make it better.
We are achieving a whole new level of maturity in the testing area. Unfortunatelly the team is small. We know that. But we’re working on this. I’m sure you notice some improvement on the test / release area.

About a beta test team or closed beta for costumers are being discussed, but I can’t say nothing for sure.

Regards

There are a lot of “bugs” that are actually new features or a change of the actual implementation.

That’s dramatical imho as it will break current code. Since there’s no documentation what-so-ever, users find these issues and report them as bugs. Please provide a list of known issues to be indicated as new functionality and not bugs. I’m very curious about that.

If the policy of scriptcase is that it can change features anyway they like and at the time they like, so that I cannot be sure that my applications running at my customers are stable, then I need to pray that nothing gets broken on each and every new update of scriptcase. I haven’t run into issues like that, but if I do then I promise I will quit using SC immediately and stop my work here. SC will be out of business in no-time. Guaranteed.

But I trust that SC management is wiser than that.

This problem with NetMake is a well known issue that has plagued our industry from the beginnings. You can read about it at http://en.wikipedia.org/wiki/Peter_Principle

A developer/programmer/engineer gets better and better thru the years. He gets promoted - junior programmer, programmer, senior programmer, etc. Then the worst thing happens. He gets promoted to Team Leader, or Software Manager. Now he is in a job that requires a totally different skill set than the one that he has developed, and he is not equipped to make business decisions. He was a really great programmer, but becomes a terrible business manager because he does not have the proper skills for that.

In the worst case, the successful programmer gets into senior management, and does not understand that business decisions are very different from programming skills. Customer support suffers, strategic product management suffers. But on the bright side, all the programmers are having a good time as long as they ignore the customers.

Just my opinion based on 35 years of experience in software development, and seeing this happen repeatedly.

Dave

mmm we say that people get promoted until the level of disfunction. But what can I say. I am one of the old people started in assembler and am working in a management layer currently. I can only hope that I’m one of the people who can combine development and management :wink:

I’ve had a lot of discussions regarding the quality and management issues. So far I did not manage to reach the real management level of Scriptcase. It is said that they speak Portuguese only… Duh…

Don’t worry, when I said this:

There are a lot of “bugs” that are actually new features or a change of the actual implementation.

I meant that a lot of users report bugs that aren’t bugs. Don’t mean those changes will be made or even go live.
But still we have to filter those issues and this takes time.
Changes like this that modifies the actual behavior of the tool are taken very seriously. We study it carefully.
Discuss the upside and downside any change.

AND the most important concern we have is: “Will it break the current costumers and sc versions on the market?

So I might state that you don’t need to worry about changing the features anyway we want / like, because thats one of the top tier concerns of our CEO and any changes like this go through him.

Besides, we love the dedication of all our resellers / partners. We love the effort our costumers and partners do to improve our tools and you guys are mostly the ones we want to please.

Good speech Dave !!!

I hope that bugs team will take it positifly !!!