intranet - How do you handle internal systems development? -


We regularly consider the values ​​of a good quality intranet and systems to our customers, but such a thing within my organization We do not think we are "eating their dogfood"

We actually have fewer intranet systems - a faster SharePoint has been installed together that does not really handle any. An extra leftover-legacy intranet system with which it was loaded into the frame and pulled "in" the sharepad.

The general view is that senior developers are "very valuable" to ruin internal development, so its responsibilities come to the people at least qualified, work experience people, etc. At least as long as they do not get much more attractive and are sent to a customer, the fly-cohesive nature of our systems is therefore dispatched.

The mechanic is a matter of running a poor car.

How do you handle it? How can I accept management to spend the effort on my internal system?

Is it really within a tech company that it is not worth it? Do non-technical users only need high-quality systems?

Do you agree with customers as well? Show the business value of the investment If this can not be done then it will be a waste of resources.


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -