First spit a slot to throw bricks, hope to be able to offer.
Because the state is not good today, more and more chaotic, so simply put my thoughts summarized in front of it,The content after dividing the line if you feel that there is no nourishment to ignore,Can be discussed only for this topic.
Subject: the existing contract project model of party B seriously restricts the economic benefits of software development activities and the success rate, resulting in double-loss or even multi-loss situation;Specific, the drawbacks of the existing model:
- short project cycle and slow software maturity process contradiction :
- Software development process has inherent laws; a little bonfire experience or the rural people should know that the ignition stage needs to use a small amount of flammable materials to ignite the flames, and then slowly add firewood, but also for its wind to avoid blowing out, And so on after the fire can add more firewood, thoroughly burned up after you can casually throw what wood, wet all can;
- But the project is often a relatively short period, often a come up to gets going, do not give you the opportunity to fire a lot of firewood thrown up, not to wait for all aspects of work to straighten out, the project is nearing the end;
- This project is inherently a waterfall model, do you want to play the iteration? First of all, the customer IT department of the various reviews will deal with the past.
- In addition, the project cycle is short, hasty, often the client side is not fully prepared, the need to cooperate with insufficient efforts to cause the demand is not clear, the problem is the most deadly;
- The contract leads to confrontation rather than cooperation : Software Enterprise marking stage at all costs , what all do not dare to agree, after getting contracts to start Jerry -building (cheap labor sucks); the other side because the scope of the project is often not clearly defined , The customer felt that the money spent out to value, ask for no restraint, request Chatty, flexible configurable, make a small mis want to let you send an OA ERP; this game finally did not win;
- Short-term interests and long-term interests of the contradiction: the project phase is generally not profitable, two phase three is the harvest period, do not make money to invest resources, and then do bad, and then did not then;
The result is that both parties are difficult to build trust and form long-term stability,Efficient partnerships, software companies complaining that customers are difficult to make the market,The customer complains that a large amount of IT investment has little effect and is cheated by us.
Why is it so hard to push?I think of the last thought of a conclusion-
enterprise IT project construction is unable to skip the business consulting process directly to the development team to do , Imagine if the business domain experts or industry consultants can work with the professional development team to play their respective professional advantages, then the above problem is not solved?
- First of all, consultants in the consultation project is actually in the ignition, they understand the customer business process for the follow-up cooperation to lay a good foundation-trust plus familiar,
- The results of the consulting project also provide the basis for the scope of the following development projects, and the scope will not be out of control.
- Consultants often also part-time pre-sales, and is a better pre- sales, marking success rate and project amount will be higher;
- At the same time, the development team can also make up for the impracticality of the pure Consulting project, even in the process of consulting projects to intervene in the development of prototypes, POC;
Of course, this idea is not something new,But I think that at present, the consulting and development sectors in our industry have not been cooperating very well,The basic is fighting each other-the former in the customer, the latter in dealing with customers,It is a reputation that is so defeated that some powerful companies can afford consulting and development teams,But as I observed several times close, they were just the same company name.Oh.
Now is the internet age, I wonder if I can cross the limits of the company, the region,Our IT workers and consulting golden collar formed a so-called "Free People's free association", a small entrepreneurial team in the form of mutual complementarity and cooperation,You call me to code, you collect money, I split the money,By the way, the reputation of the IT community has been saved.
One might ask what is the difference between this and the current company form,The difference is that the company is too big, and the best company is TW,Specific to a project also can not be level, the brand effect of large companies and halo early fade, eventually by a large number of ABC team,Replaced by XYZ Studio.
The conclusion part is these, a bit of confusion forgive Ah, throwing bricks, throwing bricks.
========================================================== the past 11 years, personally participated in, closely observed,There are also dozens of size items that you have seen.Deeply feel the software development this thing really is
success is accidental, and failure is almost impossible to avoid .。 I do not know how much the failure rate of software projects in the domestic industry today (is below 50%),But the success rate is very low from the projects I've been through, and there's probably only one project that's been successfully phased (1 years after development,Although slightly postponed but basically achieved the goal,And then once a month release constantly on the new feature repair defects, of course, project success and failure also have no unified standards, I think this project
Success is mainly seen from the results, in addition to the original project objectives, the projectParty A a number of personnel to get promotion, the project in the scope of the whole division of the company was rated as excellent project, we won the two-period, three-period contract, is still in continuous development and upgrade. ( My success criteria are not low, because there are a lot of successful projects to complete the project is actually no one in use)from the process to see, this project is still relatively chaotic, early team lack of experience, Management, communication, architecture, design, business and so do are not ideal, which also caused " success is only phased", because the accumulation of technical debt too fast, development efficiency and quality fell sharply (already unable to compensate by overtime), The project was repeatedly crisis, the high turnover rate further exacerbated the crisis. That 's what a pre-term can be called a successful project, and it's estimated that a year or two later will be removed from my list of successful projects. Moreover, the early success in fact also has external factors of help -there is a very wrist-party leader for the project to create a very good environment, to win a lot of resources, coordination of business units. So this success for us is in fact accidental, because you can not expect the future projects also have such a leadership of party a help, this No, just heard that the leader has left the client company.
I am a like to reflect on the people, so nothing to ponder over these experiences of the project, pondering the pattern is: if the original XXX, then now should be yyy it,more reflection I found that in fact, the project in the process of things (including technology, business , architecture, management, etc.) are relatively controllable, especially for this group of people, there are enough methods and tools to
do things right, to
Work in the right way, but on the other side--to do the right thing, there seems to be no way out. What is the right thing, I simply understand is to do the customer really need the valuable software. It's easy to say, but it's very difficult in the Enterprise software field , compared to the face of personal consumer software,difficult in several ways:
- First of all, management is complicated: it's not nonsense.
- Business is complicated: it's not nonsense.
- The technical complexity of enterprise application field: The most indispensable is the concept, big words and a variety of new technologies, as lively as the entertainment Circle, and a large number of legacy systems need to be integrated;
[email protected]
I'm fed up with this mode of operation in the enterprise software market.
