HUP Customer Scrumbles - Developing Together

Customer Scrumbles - join now

In the course of dynamic market changes, HUP has long been pursuing new, agile paths in software development - together with you: As a result, you can act faster than your competitors on the market and at the same time secure unique transparency over the development steps. With the agile Scrum method, all requirements that often arise late in the practical application can be incorporated as they arise. Your practical experience from day-to-day business, your ideas and wishes for an optimal end result flow directly into the product in HUP's new development concept.

Let's achieve more together.

Click here to go directly to the active customer scrumbles

HUP PS.Paradise #Subscription

HUP PS.Content

Customer Scrumble? Can you eat it? - Almost

Customer Scrumble is HUP's own word creation. The artificial word is made up of two terms: "SCRUM", stands for a process model in project and product management in agile software development, according to which we have been developing our products for several years.
The second part comes from the word "CRUMBLE", which literally means "crumbs" and in its true meaning describes a part of a dessert, namely the crumble.
Only together with all the other ingredients, the crumbles become a tasty dessert. Just as with our customer scrumbles, the magic only comes from working together.


It gets a little technical for a moment ...

Diagram of the process in the customer scrumble


Continuous deployment is a strategy for software releases in which each version that successfully passes the automated testing phase is automatically released for production deployment.

Continuous Delivery is a software development method in which code changes are automatically created, tested, and prepared for a production release.

Continuous Integration is a software development process in which developers regularly merge all code changes into a central repository (directory). These changes are then created and tested automatically.

Continuous Storytelling in which the user's daily routine is described in a true-to-life manner. Including all persons, roles, tasks and systems, so that he can easily find his way around.

Continuous Requirement (continuous requirements) is what we call the requirements that arise again and again in day-to-day business and then flow into the customer Scrumble and thus into the software solution via the participants.

Continuous documentation In a future step, the user stories and the resulting implementation will be continuously documented as one story, so that new employees can find their way around the application in the shortest possible time.

In summary

The meetings focus on the jointly developed user stories, which - in short - define the various use cases in an extremely practical manner. These should always benefit as many publishers as possible.

The proposals are discussed together, prioritized and finally implemented by the HUP developer team in the period between the participants' meetings.

At the follow-up meeting, the results are reviewed in the group, new user stories are written, and development is efficiently advanced.


Some stakeholders and process steps

The customer Scrumble team

22 Team Member

The user story

20 Story

The Productowner

03 Product Owner

Quality assurance

29 Quality Assurance


We always have new requirements. We remain modern.

We are never finished. We are getting better and better.


FAQ about our customer scrumbles

Who are the participants of the customer scrumbles?
The most important element is the participants from different publishers/companies, i.e. you. You don't need to know anything about technology or software. You should be proficient in your job and have ideas and creativity to think one step ahead as well. In addition, there is the "Product Owner" (PO) from HUP, who is responsible for the product, as well as Arno Nix, HUP Managing Director and Head of Development, and various HUP employees who contribute to the success of the event in technical or organizational terms. Add to that a hands-on designer who keeps an eye on the look and feel and user experience of the software.

How often and where do participants meet?
Ideally, the teams meet once a month - at least in the beginning. The meetings take place either at one of the HUP locations, at a central location that is easily accessible for most participants, or at a company headquarters of the participating publishers/companies. Currently, the appointments are held alternately as face-to-face and remote meetings.

Do I have to be present at every appointment?
Participation in the customer scrumbles is of course voluntary. If only because there are also unpredictable deadlines in day-to-day business. Nevertheless, in the interest of everyone and your goals, you should be present at as many meetings as possible to actively shape the process. This way we can achieve the optimal result together.

When can we expect to see what results?
The jointly developed further developments, additions and innovations are supplemented and made available at monthly intervals.

You would like to be there too? Then write to us!

    Bitte vergewisseren Sie sich sich unter Datenschutzeinstellungen, dass die Erlaubnis zur Verwendung von "Google reCaptcha" erteilt ist.

    Ihre Nachricht an HUP:

    Die Felder mit * sind Pflichtfelder. Vor dem Absenden bitte ausfüllen.
    Mit dem Absenden der Kontaktaufnahme bestätigen Sie die Kenntnisnahme unserer Datenschutzerklärung.

    +49 531-28181-0


    Am Alten Bahnhof 4B,
    D-38122 Braunschweig

    Contact us