Software project Management (CMMI Maturity) Practice--Decision Analysis (3)

"Software project management (CMMI Maturity) Practice--Decision Analysis (1)", "Software project management (CMMI Maturity) Practice--Decision Analysis (2)", PostScript.

The activities of the front-end development technology architecture decision-making analysis are over, it should not be so quick to write a summary, but, indeed, there has been a great change. So write about what happens next.

I am very happy that the project team developers after a long period of intense discussion, research, finally through the decision-making analysis method to choose to introduce Java EE Technology architecture, and put Cordys products in the background. I feel my pressure drop, the main reason is as follows:

(1) Restricted and restricted by Cordys products, greatly reduced;

(2) Procurement Cordys product manufacturers on-site technical support services to reduce the urgency, can avoid the company personnel transfer turbulence period;

(3) The procurement of partner personnel is relatively easy, because Java EE developers, the labor market a lot, and based on the Cordys platform is rarely seen;

(4) through the company's coordination, the new project team developers, not subject to technical constraints, can be quickly put into the work;

(5) Members of the project team have a much smoother communication.

Maybe it's too early to be happy.

Today, in tracking the progress of the project and planning process, feel that some people do not understand the needs of the comprehensive, there is a core top-level design is not clear problems, progress lag. As a result, the designer is urgently convened to discuss the meeting. The conclusions in the minutes of the meeting are summarized as follows:

(1) The design staff on the support process Visual rapid Development Office of the public capacity platform requirements, content, objectives and other basic information is clear, the details may need to communicate;

(2) System deployment, the scope of use for the provincial company + 13 city;

(3) Require the system to be loosely coupled design, support data adaptation, component, service-based;

(4) Require the system to provide maintenance support, such as: Service monitoring, interface monitoring, etc.;

(5) Require the system to manage the application cluster, Support Online deployment, start-stop application, a failure does not affect the overall situation, to ensure system stability.

......

Suddenly found that, based on the open source Java EE Technology Architecture, System operations, application cluster management and other platform capabilities, need to design and develop their own, this workload will be huge, there is a great deal of risk. If this content is not designed, then the system will be in a bare-Ben state, failure can only restart the service, is not controlled. This is not possible. These abilities are the native ability of Cordys products.

What to do?

Change the design, back to the Cordys platform (because there is no second feasible solution), plus the technical architecture of HTML.

Finally, the designers finally approved the 0.77 version of the technical solution at the end of last year (see the program prototype "cloud computing unified Office Platform service capability Design" and the 2013 blog "Thinking of upgrading existing applications using cloud technology").

This is a good thing to do, not to implement where we know the feasibility of the scheme, but this road, curved and long.

Summarize the following three reasons:

(1) I do not clear the need to preach, missing the focus, such as the 0.77 version of the scheme (more than 150 pages), there is a large space Cordys platform product characteristics are not clear, but for these features, users, customers understand. Also assume that designers are aware of;

(2) Lack of training, designers on the product, the relevant technical standards are not unified, such as the definition of the SaaS model (refer to the use of multi-tenant technology in IT systems to provide personnel cross-departmental and virtual team Solutions (draft)).

(3) The most critical point: the lack of a stable development team, especially in the rapid development of information technology today, loose, temporary formation of the team, lack of communication context, communication costs, time costs, the production of rework costs, is inevitable.

Unfortunately, how many people can realize this ah, perhaps still think I have to dig a hole for everyone. As everyone knows, I have just found that I also fell into the pit. Feeling depressed!

Project management, this is the case, each encounter is different.

Software project Management (CMMI Maturity) Practice--Decision Analysis (3)