Hybris Partner Conference Day Two

Hybris partner conference day two agenda
Hybris partner conference day two agenda – delivery stream

Today is the second day of the Hybris partner conference. Yesterday was about changes at a company level and the commercial roadmap for partners.

Today has been split into three streams – commercial, delivery and technical. I joined the delivery stream because a colleague is attending the commercial, and delivery is kind of in the middle of the other two streams.

Apologies for grammatical and spelling mistakes as I’m releasing this post as quickly as possible throughout the day:

Setting up for success

Hybris are often called in to problematic implementations (emergency help), which is affecting growth of Hybris because it requires significant Hybris professional services. One of the problems Hybris face is when they work on Agile projects, they ask for documentation to get started, and the implementation teams will say “We don’t have any documentation because we’re Agile”. This means it takes longer for Hybris to help with the project, and besides, Agile doesn’t mean no documentation!

5.1 Product Update

The latest version of Hybris includes a Chinese accelerator, which supports Chinese payment systems, social networks and provides a more culturally aligned front end design. This demonstrates how important China is to the organisation.

Search (supported by Solr) has a dynamic feature which lists results as the customer starts typing their keyword (like Google), and the results can be ordered, or ranked, by a number of factors. It also supports “hero products” where results can feature any number of products even if they don’t completely match the initial search. This also includes filtered, or categorised search results.

Hero products are administered by simply clicking a star, exactly the same as Twitter favourites.

Order Management Services updates include a unified User Interface (UI) for different back office administration views such as content, order management and sourcing.

The UI now uses Cockpit NG across more of the administrative applications.

The Subscription Billing Gateway has been extended to support publishing and Telco customers. It supports subscription products with multidimensional, complex offers.

Unsurprisingly some new 5.1 features includes support for Hana, also owned by SAP.

Hybris and Agile

Hybris gave a short presentation on the advantages of iterative development, especially Agile. They also recommended automated testing and continuous integration, techniques for reducing technical debt and improving quality through peer reviews. Release frequently rather than big bang releases.

We already do this at Endava and it always surprises me how many other companies don’t.

Best practices

Hybris have a reference implementation which includes best practice for ecommerce projects. This includes design patterns and documentation for partners to understand and emulate for our own projects.

Hybris gave a presentation about being ready to go live:

  1. Configuration and architectural review
  2. Monitoring is in place, both hardware, application (database, web server, etc.) and specifics, implementation monitoring
  3. Performance testing is considered mandatory, with real data, on an exact replication of the production environment.

Hybris went through some horror stories of real launch problems. A bigger problem is that a number of partners repeat those horror stories, so Hybris promoted a shared best practice across partners. Hybris already has a document listing these best practices. Clearly this document isn’t enough though, or partners wouldn’t be repeating the mistakes.

Performance Case Studies

The most common implementation issues are:

  1. Inadequate NFRs (Non-Functional Requirements)
  2. Testing too late. Not testing enough due to lack of automated testing and the inefficiency the business views manual testing.
  3. Partial testing, such as the customer view and not the administration side, or application testing without testing the production network and hardware
  4. Not using production data

Many of these issues apply to more general web implementations, not just ecommerce.

Finally, Hybris strongly recommend partners inform them of go live dates to have consultants ready. And even better, using some Hybris professional services in the implementation rather than waiting for the emergency call.

Toll Gates (consulting best practices)

In order for s successful ecommerce implementation, customers will need a level of commerce maturity.

Before implementation begins, it’s important to define the business strategy, identify key roles and responsibilities, priorities (high level business concepts rather than project deliverables) and a Plan B. All are obvious project management deliverables, but are often ignored and starts an implementation incorrectly.

Hybris showed a typical organisational structure for a new customer, with IT and business leads.

Hybris have a number of toll gates in an ecommerce implementation to avoid the common pitfalls and emergency calls later on.

Hybris recommend the partner and customer build a project on boarding process for new people coming into the project – both technical and business users. This also highlights the need for clients to step up, mature and defy their own processes.

After go live, the project needs a release management process, with Plan B and the other points listed above. Again, we do this at Endava, but I suspect many other partners don’t.

Measuring success is critical. “The difference between a good partner and a great partner is how the partner plans for and handles issues, at both a business level and technical”.

Red to Green

The reason for many clients calling Hybris is that something unexpected has occurred on a project and the partner didn’t have a plan to handle this anomaly. Hybris don’t just jump into the project and handle the current situation, they will do a complete project audit, from overall project management (roles and responsibilities, methodology) first. They will reaffirm success criteria, scope prioritisation and then do a complete (people, plan, tools, code) review on the target area(s).

In the event of an emergency call to Hybris, they create a rescue, or go forward plan. This doesn’t always have an optimistic outlook and may involve moving timelines and increased costs (more resources based on an artificially low quote to win the business).

This was all common sense, and is what gave me my grey hairs in my early days. For partners on the audience with a full head of non-grey hair, these tips were useful.

Partner Enablement

The new partner programme is multitiered, with Contractor partners and basic level (hyOn). New self-service training will ramp up the number of developers (and other functional roles) more quickly. There will also be a specific Busyness Analyst training course, and unusually for a product company, they will provide a train-the-trainer course for larger SI’s (with over 100 developers to train) such as Endava.

CMS Integration

Hybris already has some CMS capabilities, however some clients still need to use an external CMS (Content Management System) to handle complex workflow, personalised content paths including multiple languages, job roles, authentication and approvals, and promotional microsites. Best of breed, modern CMS products (e.g. Adobe CQ5 and Sitecore) can still handle content more efficiently than ecommerce platforms.

To integrate Hybris with a CMS, you need to consider:

  1. The product taxonomy, and where the content will be entered
  2. Where customer user data will be stored, for both the checkout process and marketing purposes.

As a generalisation, data that changes frequently (more regularly than every few minutes) and is time sensitive needs to be stored in Hybris.

6 thoughts on “Hybris Partner Conference Day Two

  1. Hi Bradley,

    Thanks for this very informative Blog, hybris information is so hard to come by on an open source basis. I had a couple of questions for you, hopefully there are open source answers.

    1. hybris deployment strategy – while the hybris wiki talks through a traditional waterfall model, the ideal would probably be a mixed waterfall-agile model. Do you think hybris would prefer the agile approach going forward?

    2. hybris integration with external CMS is talked about and well publicized. However, what is less known is integration with Knowledge Management solutions for the hybris Customer Service area. Do you know if there is a preferred vendor like eGain?


  2. Hi “Somdev”

    I have some experience on hybris.

    1) typical development approach with hybris is Scrum Agile. Obviously the methodology is often dictated more by the clients business, maturity of development environment, time to market, clarity of requirements and additional vendor considerations, than the hybris software.

    2) hybris Customer Service Cockpit (CSC) does have a range of issue tracking which can form a basic KB solution. Depending on how comprehensive the solution needs to be hybris can be extended as hybris is built on the Java Spring framework and can be integrated with a wide range of other KB offerings.

    For further information hybris does have a variety of information in the public domain or available from their sales teams. Registered customers and partners can use the hybris wiki for more indepth guidelines around general approaches and reference implementations.

    Or you can ping me any general questions and Im happy to point you in the right direction.

    Hope that helps.

Leave a Reply

Your email address will not be published.