The hybris community is still in its infancy – young and hungry for knowledge, but daring to succeed. At present, the hybris company has a large volume of partners and customers, who benefit from the various versions of the hybris software Omni-channel Suite.
Globalization of languages and data, complex Customer touch-points and Organizational transformations put forward new demands on the realization of e-business programs, where complexity goes beyond the regular software project. Today, even a trivial e-commerce project becomes a challenge, when using an evolved highly customizable platform such as the hybris Suite.
And the complexity does not come from the direct business requirements. It often stems from the assumed project commodities, which every project should (ideally) possess, like: a “careful sales process”, a “right level of consulting”, “correct project setup”, “knowledge of the hybris platform”, “awareness of e-Commerce practices”, “understanding the organizational changes when embracing a PIM solution”, and so on.
After analyzing regular hybris projects one can discover a good number of reoccurring project deficiencies. My objective is to offer suitable solutions to each of them – like patterns. The current post sets the start of a series of articles regarding a Pattern approach towards hybris projects.
Challenges and Solutions
Nowadays, Technology does not pose a real challenge in constructing a software product, because the maturity of the current technologies allows us to achieve great results and innovate constantly. In the comming articles you will find little about technical topics, because solutions to them are normally found in the best practices documentation of hybris. In addition, every hybris-savvy company has a good bunch of practices, which master the technology.
The true challenges, in hybris projects, are from organizational, methodological and soft-skills nature.
As with any other complex software platform, the hybris suite compels a certain level of expertise in order to be suitably presented, understood and adopted. It is for this very reason that a hybris project requires a hybris skillset for every project role – an exclusive expertise, which allows the coverage of all solution aspects and extracts the highest value for the client.
The project success, to a large extend, depends on the skills of the partners in delivering high-quality solutions, the maturity of the development teams and the adopted common practices.
It is a fact, that hybris partners face a steep learning curve in implementing hybris solutions. As a result, one can observe the development of questionable in-house project practices, ad-hoc solutions and even, consulting anti-patterns. Companies encounter those challenges in different phases of the project life cycle – in various steps and magnitudes.
Projects require structured assistance and a methodology. Hence, it is my belief that an effective project strategy should not only be User-, or Requirements-centric – it should be, first of all, Human-centric. It should enable transparency, trust and value. Because, only with those, a true progress with measurable results can be observed.
The follow up articles refer to well-known methodologies and common consulting practices. However, the goal is not to invent new or redefine existing methodologies, but rather to utilize their valuable elements, consolidate them and identify possible solutions for the prominent difficulties we face.
It is my intention to share experience and knowledge about hybris projects by using a format, which is easy to grasp and follow. This post begins a voyage where Business Client, Partner and hybris form an ultimate alliance towards successful implementation projects and renovated business models.
In this voyage, the Quality of Consulting is at the center.
Follow our next article to learn more about what hybris patterns are ...