Additional Information / Event Location
H4 Hotel München Messe
81829 München, DE
We have reserved an allocation of rooms for you. You can choose between two hotels: The H4 Hotel (venue for the conference) or the neighbouring H2 Hotel. The hotels are next to each other and both are connected to the conference facilities.
Here are the direct links for hotel reservations:
H4 Hotel (4* star)
H2 Hotel (3* star)
Should these two links to the room allocations not be working, please reserve your accommodation via the following tel. no.: +49 89 9400830, by fax: +49 89 9400831000 or by email at: email@example.com
Reference: REConf 2019
Booking code: AKRXX100319
You will find directions to the venue here: Directions
Alternative: Motel One München Messe
We have reserved an allocation of rooms for you in a nearby hotel. Bookings can be made directly with the hotel using the following booking form, by quoting the reference “REConf 2019”.
Please send your completed booking form by email or fax to Motel One München Messe.
Fax: +49 89 413 29 92 10
Tel: +49 89 413 29 92 0
Rooms booked individually can be cancelled free of charge up until 08.02.2019.
The allocation is bookable up until 08.02.2019. Please note that rooms for dates outside of the period stated can only be booked at the applicable daily rate directly with the hotel. Bookings at the special rate using the online booking form are not possible in this case.
Payment is made individually by each guest on arrival.
- As a speaker you are automatically registered as a "delegate" at REConf 2019.
- At the conference, please report to the registration desk to collect your name badge.
- On which days can we expect you? Please let us know in advance:
- 11 March 2019 - Ice Breaker / Open Space
- 12 March 2019 - Conference Day 1
- 12 March 2019 - Evening Event
- 13 March 2019 - Conference Day 2
- Although a submission may have several authors, only one main presenter and one co-presenter may attend REConf each day.
- A co-presenter only has free admission to the conference when she or he was named as co-presenter at the time of submitting the presentation.
- A co-presenter may not be named at a later date.
- Any additional co-presenters need to register for the conference as normal paying delegates.
Discount Code - to give to your colleagues:
- As a speaker, you will receive a discount code for REConf 2019 that you can pass on to colleagues and friends.
- Slides are most likely to be in 16:9 format
- Please let us have your presentation by 12:00 hrs on 1 March 2019. You will receive a special link for uploading and storing your presentation in mid-February 2019
- At the conference, your presentation will be shown using our conference notebook. It may be possible to use your own laptop in exceptional circumstances. In this case, please let us have details of your hardware by 12.00 hrs on 1 March 2019. Detailed information to follow.
- A short introduction (1 minute) to your presentation following the morning keynote address on 12 March and 13 March 2019. This is a valuable decision-making tool for delegates and gives you the opportunity to wet people's appetites for your own presentation.
- For this, please make sure that you are present for the keynote address and sit in the front row (labelled).
- You will receive further information, incl. a master slide for the Speed Presentation, shortly before REConf 2019.
Moderation of Your Presentation
- Your presentation will be moderated by a HOOD Consultant, who will introduce it to the audience.
- You will be contacted by us a few days before the conference to agree on the moderation.
The following standard equipment is available:
- Projector (with VGA & HDMI sockets)
- Wireless presenter incl. laser pointer
- 1 flip chart
Your Arrival & Accommodation
- Please arrange your own travel and accommodation.
- Information about accommodation in the conference hotel
- There is a limited allocation of rooms.
Submission of your Presentation - Call for Papers
- All those who have submitted a presentation will be notified at the end of October 2018 as to whether their presentation has been accepted by the programme committee.
Virtualisation and Simulation
Deployment of digital and virtual versions of products is becoming more and more common in development. Simulations and virtual and digital twins are becoming increasingly significant development stages. They support validation, verification during the development process; a vehicle for communication with stakeholders and other systems; and act as mock-ups or prototypes for eliciting requirements.
Models and Modelling
Requirements do not necessarily have to be captured in text. Getting away from mainly document-driven development and accepting models as a part of requirements specification in various areas of development: in which areas have you been successful in this? What were the obstacles that you had to overcome? What new type of cooperation between development disciplines is necessary in order to implement model-based systems engineering?
The Internet of Things (IoT), Industry 4.0 and Blockchain are buzzwords that are increasingly used in the workplace. What influence are these digital transformation issues having on development and production? What techniques do you use for dealing with requirements in this respect? What are the new aspects that need to be considered in organisation and interaction with people?
Innovation and elicitation of requirements are closely linked. How does your company deal with innovation? How is innovation encouraged within teams, in order to react to ever shorter development cycles? How do you integrate trial-and-error? What encourages a constructive way of dealing with mistakes? What role do parallel development, the development of alternatives and selection play in your organisation? How do you combine innovation and dealing with requirements?
Variant Management and Product Life Cycle
In complex products artefacts in mechanics, mechatronics, electronics and software must interact well. They are suitably linked through requirements engineering. RE links product strategy and advance development, project initialization, development and construction, commissioning and production, maintenance and operations; as well as associated project, configuration, version, variant and change management. RE is therefore a significant component for product life cycle management. We are looking for presentations that examine RE in the areas of PDM, PLM and ALM.
New Work and Organisation in Development
Value-based leadership, New Work, Management 3.0, Beyond Budgeting: innovative management approaches are changing the world of knowledge workers. What is required of our leaders to manage this transition? What support do requirements engineers, business analysts and product owners need from management and the organisation, in order to still be successful in a complex world? How does the manager need to change so that agile development is possible in the organisation? How does the manager's daily work change? What happens to the manager?
People and Technology
People are normally only considered explicitly through their "role" in development. Customers and stakeholders are also people. How can people with their special qualities be explicitly taken into account? What techniques in Design Thinking, UX etc. have you used successfully?
Autonomous and automatic sub-systems are playing an ever bigger role, both in our products and in our development and production areas. What prerequisites are necessary to be able to deploy autonomous systems effectively? Which automatic processes do you use to support development and production in your organisation? Which RE and RM tasks can be automated?
Advancing new ideas together with enthusiasm and curiosity.
An interest in developing new products or approaches arouses enthusiasm and passion.
People with a burning passion for designing new things, and meeting the challenges associated with new and further developments, do so in teams.
Creating trust through commitment, focus, courage, openness and respect.
Successful teams for innovative products and approaches need an environment of trust. This is established through a commitment to working together towards an agreed common goal in a focussed, consistent and persistent manner. It also requires having the courage to go in new directions, talking openly about any awkward issues and showing respect for the experience and views of all those involved.
Based on agile values, principles and practices, and a value-oriented approach to requirements, we work together with our customers to enhance the development of their innovative and complex systems.
HOOD has been helping large organisations to improve the way they deal with requirements for over 25 years.
Rather than sticking dogmatically to set approaches or preaching about process models, we agree development practices with our clients pragmatically according to the company's particular situation and market, and avoid unnecessary expenditure.
A change of approach is not normally a technical issue. We get those people affected by the change onboard by designing the change process with them together.
Our core competencies are in agile transition and requirements engineering, including its various interfaces with systems and software engineering. For this we are able to draw on many years' experience in agile coaching, and sound expertise in requirements management.