Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-12185

Productization: transfer ownership of containers to the product teams

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Done
    • Major
    • fuse-7.x-GA
    • None
    • Build
    • None
    • % %
    • ?

    Description

      Over the releases many issues could have been prevented if the productization of the containers were a responsibility of the product teams.

      Centralizing the productization of the containers on the productization team causes the following problems:

      1. It reduces the quality of the delivered container because the productization engineers are not directly involved with the project and are unable - due to the workload - to keep track of all the changes happening on the project. They cannot make informed decisions about the best way to build and package it because certain decisions about the images actually require an in-depth knowledge about how the product should work.
      2. It prevent productization activities to be thought upfront, leading to situations where the products relies on artifacts not productized by Red Hat. This, in turn, causes several other problems that increase the risk for Red Hat and our customers.
      3. It creates a delivery bottleneck delaying the releases, because the container maintenance is focused on only a few engineers and is not shared among the larger team.
      4. It does not follow the productization practices already in place in most of the teams, where the product engineers are responsible for maintaining the containers for their own products.
      5. It should also help sizing the scope of the projects. By thinking upfront about the design and technical choices, a more informed evaluation of the productization impacts can be made and the schedule can be planned better.
      6. It also leads to longer times to resolve the issues as, sometimes, they involve knowledge related to specific tools or technologies related to the products. The operators and front-end applications are particularly affected by this because of the large ecosystem used to support them.

      For the purpose of exemplifying the impact of this, I would like to use a list of issues I worked with in the last release and that could be easily prevented. The numbers may be similar for other productization engineers:

      21 out of 29 issues productization issues I worked on the last 3 releases could be prevented by this.

      Naturally, it does not mean we wouldn't have any issues, but we can probably reduce the rework and impact on all engineering areas, including QE, with this.

      Attachments

        Activity

          People

            Unassigned Unassigned
            opiske Otavio Piske
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: