He mentioned development cycle, whether it is software company owner, or programmers, or users have an awful headache. It seems to be difficult to break a curse: the software development cycle is always longer than the expected time, it will always be postponed. The company makes software programmers and more helpless boss is: we do not slow down, ah, we have been in non-stop forward in time ah ......
Problem in the end Where is it?
1, professional people did not do professional things, lead to inefficiencies.
Professional people doing professional things, everyone knows this truth, but often in practice, always violated.
In the software development division of labor more and more clear today, so that the rear end of the front staff personnel rush job, to write web pages, style, efficiency can be high? Let people try to steal their jobs back end of DBA, do database optimization, efficiency can be high?
This may have occurred and the company's development process, organizational structure, personnel planning related; it may and task arrangements.
The early development of the company, could not afford a lot of professional people, may need "full stack" engineer, consequently grabbed; transition development of the company, a bit of money, but also to make someone aware of the professional thing to do, but who have not move together, and that is no way, do you have to part with all sorts of things. The company also developed to mature, if front-end, back-end, testing, architecture, DBA, network, server operation and maintenance, technical support, security, product, did not distinguish between these functions is good, it will have a significant impact on productivity. Also resulted everyone is busy, but the work is still not finish.
2, beginning not pay attention to code quality, post-rework, resulting in low efficiency.
Sometimes, that is, fast slow, for the early lack of experience or a bad habit of developers, developers, forced or they did not realize that the pursuit of progress, logic did not thoughtful, not doing self-test, even if the code is run up complete the task. But later in the project, the testing phase, the outbreak of large-scale problems, even to rework due to post-test, write from your own code, may be separated for some time, and some things they forgot, and then go back again "familiar" , low efficiency can not do? This also tends to make the project schedule becomes uncontrollable. Therefore, even if the tight schedule again, but also to withstand pressure, have to do the most basic test, and then proceed to the next task point.
3, communication costs increase, resulting in low efficiency.
Especially when multiple projects simultaneously expanded staff began to increase, the cost of communication began to be exposed.
For example, many companies have the habit of daily morning meeting, if there is a group of five people, open the morning reporting, reporting an average of one person for 2 minutes, then 10 minutes, now increased to a group of 10 people, one person reported two minutes, all to report 20 minutes to complete. Time so in the past.
In another case, for example, 30 days of work, given to two individuals do, it may take 15 days, but the same amount of work to do given to five people, six days to complete it? This could be a big question mark. why?
Because in the communication process, information may be "distorted", a person does not necessarily want to be able to 100% say it, others say it's not necessarily 100 percent understanding, and ability to understand each person's knowledge are not the same, to understand prone to bias, it is easy to generate bias wrong things.
But many people will say: how can there be so much time to communicate ah, work to put in there, no time ah!
4, the mode of communication to convey information not lead to distortion, and even rework.
Demand from users, but the actual demand is the presentation of R & D personnel, while in the above communication, there is no direct communication between developers and users, but through product manager and development manager double to convey, then we can imagine, research and development between the actual product and the needs of users who completed the final will cause deviation.
5, technical architecture too far behind, too complicated.
Advanced technology architecture, unified and efficient development standards, is the cornerstone of the system construction, will greatly improve productivity software, allowing developers to focus on achieving business, business logic, do more valuable, higher output of thing.
When you are still tangled page compatibility, tangled how to achieve this interface is required, and people through simple configuration tool, the interface automatically generated; when you're still tangled concurrent capacity, how to implement a distributed transaction when people messaging, two-phase commit fly has been used; when you are still entangled distributed systems, databases split, if you do cross-database queries when people ORM library automatic routing, data distribution mechanism has been used up; when pulled unclear, Road, unknown relationship between the various system calls, could not guess a single point of change sphere of influence, operation and maintenance of the enormous pressure when people came into service governance framework ...... all of this all, rely on advanced software architecture platform.
JEPaaS rapid development platform has a strong infrastructure and solutions that can help you quickly improve development efficiency, rapid development of all enterprise information management systems such as OA, CRM, ERP, HR, HIS, SaaS services, micro-channel docking, APP application, so that your develop even more powerful, more effective.
JEPaaS systems Home
JEPaaS comprehensive set of system functions page