On the styles of implementing large ERP projects
This article is a response to the recent post of Joshua .
Initially, a separate comment was planned, but in the end I realized that it was too big.
I have worked for more than 6 years in a company that has been developing and implementing its own PDM system. This is a slightly different class of systems for other purposes, but the meaning and rake are the same: we have a large corporate system that allows you to automate / computerize something. At first, I myself was very amazed at the fact that was voiced in the article completely and completely, namely:
')
So I can explain from my belfry this article. Recently, I was at an open lesson in the Academy of National Economy with one well-known in narrow circles comrade - Ananin Vladimir Igorevich . And there it was told about different types of projects. The problems listed by Joshua are in fact features of a project of this type.
This article is a very brief extract of what he teaches in his studies. So let's say, a superficial glance at the existing problem. At the end of the article are links to sources.
In general, it does not matter whether they are large or not, and even IT or not. The principles are about the same in systems of different scales. Their features, depending on the scale and industry, are certainly present, but they can be ignored so as not to overload the article. Consider the basic principles.
There are 4 types of projects for the implementation of information systems:
• political;
• typical;
• professional;
• innovative.
Each of them has its own specific relationship, strategy of implementation, management, financial component, feature of contracts, etc.
Briefly for each of them
• Implementation strategy - “The system is being squeezed on an existing business”
• Requirements - customer's wishes (uncertain and changeable)
• A large amount of improvements
• Architecture - “Quilt” - a mirror of relationships
• One leader and everyone works on his direct orders
• Generalized planning and poor cost control
• Solid team of friends with a full load on the project, loyalty
• Informal personal communications and fragmentary documentation.
• Dictate customer
• The contract is simple and non-transparent (all on a personal relationship)
• Costs + ext. costs
• Focus on continuity of relationships and cash flow
Implementation is the optimization of a business by solving existing problems. The customer is the king. A lot of headache for performers. Individual approach to the customer. But the easiest option in terms of entering the market, the implementation of the first project, etc. All young companies go through this stage. This is the very thing with which the author of the previous article usually works. And I worked until I escaped :).
• Implementation strategy - Conveyor: standard settings and training
• Requirements predefined by the system.
• Detailed technology implementation
• Architecture - Standard boxed local business application
• Work on clear procedures
• Detailed planning and good cost control.
• Design group - machine, narrow specialization, part-time
• Formal communications, documentation is strictly formalized.
• Intense competition, the dictates of the customer
• The contract is a detailed work and supply plan.
• Fixed price and terms
• Extraction of profits from the flow of standard projects
Implementation is the solution of typical business problems. In principle, the customer does not care who the service provider will be, and the manufacturer will have to knock around among competitors. But if it gets to the body, then everything will be according to the standard, and screwing up additional women does not provide for in principle, even for a lot of money. Standard office applications with basic functionality.
• Implementation strategy - “The business is being put on the proposed system”
• Requirements are predetermined by “Best Practice” wired into the system.
• Implementation technology focused on the “Best Practice” model library
• Architecture - Strongly integrated large-scale business application.
• Coordination of highly qualified professionals
• Tight planning and good cost control.
• The project team is a team of professionals, broad specialization, complete
• employment, professional individualism
• Formal external and informal internal communications, documentation of results.
• Dictate contractor
• A contract is a hiring team or service.
• Payment of time specialists tariffs
• Profit extraction from the brand and qualifications of specialists
Implementation is an attempt to catch up with the leaders, to introduce the latest technologies. The executor is the king. A lot of headaches at the customer. A team of high-class professionals. But a lot of bureaucracy in an atypical situation - since everyone values ​​their reputation. A typical example is a certain company came to a consulting office and asks for help to optimize its activities. Sometimes it can reach insanity in the format "customers read the contract and cried a lot, but they could not do anything."
• Strategy - “Implementation of the system - the engine of business transformation”
• Requirements Management
• Implementation technology is focused on transformation and business results
• Architecture - Infrastructure for business transformation
• Search for technical and organizational solutions in tough conditions
• uncertainties
• Project planning in the context of a business strategy
• Project team pioneering team, universal qualification, full-time, team spirit
• Informal communications, documentation of results.
• Customer and contractor - equal partners
• The contract is a framework agreement with the series ext. agreements
• risk sharing
• Profit from the project as a joint venture
Implementation is an attempt to make a breakthrough, to become leaders, to gain unique competitive advantages. Neither the customer nor the performer may not know what to do. But they know exactly what needs to be decided, there is a clearly set goal. A typical example is any office that has made a breakthrough in its field. This is the most difficult and risky style to implement. But at the same time, a possible success can cover all risks by orders of magnitude.
This is a very brief and superficial presentation that simply gives an idea of ​​the real scenarios for the development of events. In fact, there may be a mixture of styles with all the consequences. In our practice, each of us comes into contact with all styles, both from the inside and the outside. Personally, I like the most innovative. Joshua , like I once worked on a project that "optimizes the business processes" of the customer. It’s not a fact that everything that is being done is actually necessary, but everyone is happy with everything, since even that small part that is actually needed greatly facilitates the work of other employees. Well, the rest of the headache is only a consequence of the type of project in which the work is carried out. In this case, it is most likely a project with a large share of political signs.
Sources:
mipt.ru/science/NIU/results/umm/uk/3/34/f_fy4m
www.pmi.ru/articles/files/20052008_Ananiin.pdf
bntu.org/articles/management/129-erp-style.html
www.itsmforum.ru/reference/publication/article_13
UPD. As advised in a personal, added a small mini-question.
Initially, a separate comment was planned, but in the end I realized that it was too big.
I have worked for more than 6 years in a company that has been developing and implementing its own PDM system. This is a slightly different class of systems for other purposes, but the meaning and rake are the same: we have a large corporate system that allows you to automate / computerize something. At first, I myself was very amazed at the fact that was voiced in the article completely and completely, namely:
')
So I can explain from my belfry this article. Recently, I was at an open lesson in the Academy of National Economy with one well-known in narrow circles comrade - Ananin Vladimir Igorevich . And there it was told about different types of projects. The problems listed by Joshua are in fact features of a project of this type.
This article is a very brief extract of what he teaches in his studies. So let's say, a superficial glance at the existing problem. At the end of the article are links to sources.
In general, it does not matter whether they are large or not, and even IT or not. The principles are about the same in systems of different scales. Their features, depending on the scale and industry, are certainly present, but they can be ignored so as not to overload the article. Consider the basic principles.
There are 4 types of projects for the implementation of information systems:
• political;
• typical;
• professional;
• innovative.
Each of them has its own specific relationship, strategy of implementation, management, financial component, feature of contracts, etc.
Briefly for each of them
Political project
Features of implementation
• Implementation strategy - “The system is being squeezed on an existing business”
• Requirements - customer's wishes (uncertain and changeable)
• A large amount of improvements
• Architecture - “Quilt” - a mirror of relationships
Organizational structure
• One leader and everyone works on his direct orders
• Generalized planning and poor cost control
• Solid team of friends with a full load on the project, loyalty
• Informal personal communications and fragmentary documentation.
Communications
• Dictate customer
• The contract is simple and non-transparent (all on a personal relationship)
• Costs + ext. costs
• Focus on continuity of relationships and cash flow
Brief summary
Implementation is the optimization of a business by solving existing problems. The customer is the king. A lot of headache for performers. Individual approach to the customer. But the easiest option in terms of entering the market, the implementation of the first project, etc. All young companies go through this stage. This is the very thing with which the author of the previous article usually works. And I worked until I escaped :).
Typical project
Features of implementation
• Implementation strategy - Conveyor: standard settings and training
• Requirements predefined by the system.
• Detailed technology implementation
• Architecture - Standard boxed local business application
Organizational structure
• Work on clear procedures
• Detailed planning and good cost control.
• Design group - machine, narrow specialization, part-time
• Formal communications, documentation is strictly formalized.
Communications
• Intense competition, the dictates of the customer
• The contract is a detailed work and supply plan.
• Fixed price and terms
• Extraction of profits from the flow of standard projects
Brief summary
Implementation is the solution of typical business problems. In principle, the customer does not care who the service provider will be, and the manufacturer will have to knock around among competitors. But if it gets to the body, then everything will be according to the standard, and screwing up additional women does not provide for in principle, even for a lot of money. Standard office applications with basic functionality.
Professional project
Features of implementation
• Implementation strategy - “The business is being put on the proposed system”
• Requirements are predetermined by “Best Practice” wired into the system.
• Implementation technology focused on the “Best Practice” model library
• Architecture - Strongly integrated large-scale business application.
Organizational structure
• Coordination of highly qualified professionals
• Tight planning and good cost control.
• The project team is a team of professionals, broad specialization, complete
• employment, professional individualism
• Formal external and informal internal communications, documentation of results.
Communications
• Dictate contractor
• A contract is a hiring team or service.
• Payment of time specialists tariffs
• Profit extraction from the brand and qualifications of specialists
Brief summary
Implementation is an attempt to catch up with the leaders, to introduce the latest technologies. The executor is the king. A lot of headaches at the customer. A team of high-class professionals. But a lot of bureaucracy in an atypical situation - since everyone values ​​their reputation. A typical example is a certain company came to a consulting office and asks for help to optimize its activities. Sometimes it can reach insanity in the format "customers read the contract and cried a lot, but they could not do anything."
Innovative project
Features of implementation
• Strategy - “Implementation of the system - the engine of business transformation”
• Requirements Management
• Implementation technology is focused on transformation and business results
• Architecture - Infrastructure for business transformation
Organizational structure
• Search for technical and organizational solutions in tough conditions
• uncertainties
• Project planning in the context of a business strategy
• Project team pioneering team, universal qualification, full-time, team spirit
Communications
• Informal communications, documentation of results.
• Customer and contractor - equal partners
• The contract is a framework agreement with the series ext. agreements
• risk sharing
• Profit from the project as a joint venture
Brief summary
Implementation is an attempt to make a breakthrough, to become leaders, to gain unique competitive advantages. Neither the customer nor the performer may not know what to do. But they know exactly what needs to be decided, there is a clearly set goal. A typical example is any office that has made a breakthrough in its field. This is the most difficult and risky style to implement. But at the same time, a possible success can cover all risks by orders of magnitude.
Summary Summary
This is a very brief and superficial presentation that simply gives an idea of ​​the real scenarios for the development of events. In fact, there may be a mixture of styles with all the consequences. In our practice, each of us comes into contact with all styles, both from the inside and the outside. Personally, I like the most innovative. Joshua , like I once worked on a project that "optimizes the business processes" of the customer. It’s not a fact that everything that is being done is actually necessary, but everyone is happy with everything, since even that small part that is actually needed greatly facilitates the work of other employees. Well, the rest of the headache is only a consequence of the type of project in which the work is carried out. In this case, it is most likely a project with a large share of political signs.
Sources:
mipt.ru/science/NIU/results/umm/uk/3/34/f_fy4m
www.pmi.ru/articles/files/20052008_Ananiin.pdf
bntu.org/articles/management/129-erp-style.html
www.itsmforum.ru/reference/publication/article_13
UPD. As advised in a personal, added a small mini-question.
Source: https://habr.com/ru/post/172083/
All Articles