ALEG: Можно ли из "клиентского" решения сделать "тиражное"

[Blog bot]

Источник: http://blogs.technet.com/aleg/archiv...16/518015.aspx
==============
Вот как обычно создаются вертикальные «типовые» решения? Наверное, самый распространенный способ это взять решение, которое делалось для клиента, и попробовать продать его другому клиенту.
Все вроде логично, но есть маленькие тонкости:
1. Продуктовый подход.
2. Другая методология работы
3. Другой подход и организация команды.
В итоге при создании реально хорошего вертикального решения от «клиентского» остается только знание бизнеса клиента и его потребности. По сути сам продукт сильно преображается.
В принципе в MSFмногие вещи прописаны, такие как организация команды и т.д.

А если вы партнер MBSпо продуктам MicrosoftDynamicsNAVили MicrosoftDynamicsAX, то вы можете скачать подробный документ «Building a Vertical Business SuccessonMicrosoftDynamicsNAV» .

Извиняюсь, что не могу привести (или выложить) весь документ, так как он предназначен для партнеров, но выдержку приведу.
Product Thinking
Building a vertical solution requires a change in approach, from the normal customization activities that a
Microsoft Business Solutions partner would typically be involved in to a more product development focus. A
product development focus usually involves more discipline than ordinary one-off customizations at customer
implementations. The change in focus is in developing a product.
A team must be organized to focus on developing, packaging, and maintaining the product. Only you can judge
how much effort is needed to satisfy the needs of the vertical industry you have chosen.
The move to develop a vertical product may have spawned from an analysis of your existing customer base. If
you decide to build a vertical because you have been successful at selling to that vertical by making a one-off
customization, then you need to make a conscious effort to separate the individual needs of the customer to the
greater generic needs of the vertical.
Be careful not to include customer customizations in the product without proper analysis of the features needed
for all the customers in that particular industry. Do not take customizations directly from a customer site without
reengineering them to fit into the core of your vertical product. Additional customer customizations should be
built on top of your product so that you minimize the amount of unique customer specific customizations.

Successful Microsoft Dynamics NAV partners that have developed vertical solutions have a separate team
focused on developing the product and another team focused on implementation consulting. Having separate
teams enables each team to focus their energies on solving the different challenges required by product
development and implementation customization.




==============
Источник: http://blogs.technet.com/aleg/archiv...16/518015.aspx