 So, great that you already are here at the end of the conference, so welcome to our little session about our daily life and work and the challenges we face together and yeah, I'm just, yeah, I'm really happy. So this is our topic but basically we're talking about how we survive our daily work life and how we manage this together and let me give you a quick overview what we're going to talk about. It's basically what we do and who we are, how we actually started to work together and our application, how we manage development teams, our workflows, stakeholder alignment and quality assurance and a little bit of wrap up and questions at the end of course. So let's start. Who we are and what we do. Can you all guess what kind of drop we have with seeing this picture? It's like having a lot of arms, a lot of, yeah, our hands everywhere movements, right? So let me tell you a little bit about myself. So I'm Kerstin, I'm a project manager and I work for Transcomi and my role is to connect the business side and our stakeholders and all their requirements and one ex-internet, the agency we're working with and yeah, together we build like, or we build already like a very nice distribution and before we start diving deep in, let me tell you a little bit about Transcomi as this is also important. So the Transcomi group is Europe's second largest cash and carry supplier business. We have like three 31,000 employees around and 2.7 million customers. The headquarters is based in Basel and we belong to the core group that is based in Switzerland. So this is basically my company and now I'm switching over to my partner in crime, Karin. Also welcome from my side. Hi, I'm Karin, I'm project manager at 1x internet. Yeah, what I'm doing, I'm taking responsibility for planning, for coordinating, for communicating, connecting, like all this together doing day by day and these kinds of the value I'm doing every day. What is 1x internet? I guess everyone maybe knows already because we have also both downstairs and yeah, you might have seen, we are an international team. We have 58 employers and also headquarters in Frankfurt, Berlin, Reykjavik and Konil. But if you would like to hear more about the company, feel free to come again and we can connect. So how it started 1x internet and Transcomi. Okay, so Transcomi and 1x internet met first in 2018 and our requirements were back then that we had different CMS systems with different teams who are managing all over the company and it was like a little mess. So we tried to find a way to unify all websites that we have in a different way and also have a new design and something that is sustainable for all of our brands and also that it fits our B2B customers. So in the end we decided to build a Drupal distribution and that's what we did then. Yeah, we built a solution. So we standardized all websites. We started of course with one but we are growing now to 19 websites. 19 websites are live right now. In the last months we went live with Zagros Romania and Zagros Poland. Yeah, also we have like a new design with customers able front end and different for the different brands. Yeah, also the solution was like to have a smooth interaction with the customer and to be more focused for the project than like acting in background so many times for the POs. All right, just to give you some numbers what we had like done in 2023 already. So just imagine we have 5,417 work hours. This contains like only the maintenance projects. Of course also with tracking and everything what belongs to. Then we have for my person I had like more or less 1898 meeting hours. It's me of course. Then the 19 websites what we already said 480 issues features and flaws which we first created in GitLab and then switched to Azure. So this was also a transition this year in a midline in March I guess where we had a transition from GitLab to Azure. So more or less five project teams are currently working on the project. That's called distro Apollo Chronos app and product but more and deeper to that I will tell you later. Currently we're working with 60 people on the project and with eight different nationalities. Let's talk about our Drupal application. So here you can see basically the base of all of our websites. Well below our distribution there's the IRP the integration with e-commerce tools in our API client of course and then we built in the last year's two design systems. One for the red websites and one for the blue websites. You will see soon why I call it like this and each of this website has a shop integration and all our websites are hosted also on Pantheon and now I want to give you a quick demo and I hope this will work with our tabs. Is this working? All right so here you can see the Transco Mail website and it's form in a not locked in state. So when you click on the right top and a window will open a JavaScript window. I don't know if you're able to in the next just want to share to have a quick look at the front and side. So how difficult. Yes first then the sign in so this is a JavaScript layer that will open when you try to log in and then next one would be great if you click that we see already the locked in version. No it's not working sorry. Try to log in. Yeah I'm trying to. Where's my mouth? In German we call it the forfeure effect. I don't know how to translate it into English but I mean we can also skip it and go to the next slide. Can anyone see my mouth? I don't worry let's just switch. Wow okay that's a you have another button to click otherwise the audience will just see. It's like the date you can select before you actually change to the shop and see all the products. So this is now finally the shop for the user it doesn't make any difference but behind all of this another agency for you and your customer is developing our shops but for the end user it's not visible at all and also we have a functionality in the menu that each time you can like select in the CMS if you want to have a menu item displayed or not. So this is actually very very useful and can be easily managed by any content editor and also the search when you search directly now logged in in the shop you get both contents like products that are fitting your search or other yeah content that is regarding to your search. So what Kerstin mentioned already before we when we were not logged in you can't see the sortiment so when you go to log in then you it's only like the sortiment gets displayed also with some other menu points here as goodbye and cease and mark shops. So there are possibilities to like display or like not display maybe shortly just search as Kerstin is working from this maybe not live demos but basically also what we want to show here the search you can display also the content from the website and the sortiment is displayed. Yeah let's switch to another website to Frische Paradies. So this was the red one now comes the blue one. We have the same system here the same shop integration just with another design system basically the same the difference here is that the menu is a little bit more let's say designy so when you hover over Angerbote please if you if you are able to yeah yes you see a menu which is a little bit more artsy and easy for the user so you see some differences between the classic transcomil design system and a little bit more playful Frische Paradies design system here and also in the shop let's see if this is working yeah yeah the same also a JavaScript layer that comes and then hopefully magic the shop also appears I'm getting better yeah I see that you learn fast as usual okay great yeah so now you can see the full potential and Karin when you could click on the first menu item would be great so here you can see the shop with the header and all the products that are sorted in the category of fish okay cool I think and the same behavior as I showed you with the search also for Frische Paradies that you have the content from the website and also the products from the shop let's continue back to the presentation perfect all right so our next slide is a little bit of an overview what is happening like an hour shop so the unique monthly visitors are around 250 000 which is not that much if you may think but it's just for collected for our B2B business so and our shops are generating an annual revenue around one billion so that you also have an overview about what is happening on our side great and for that we switch to the next topic yep which will be about our development teams and you can probably relate to all of that but that's yeah yeah that's not a topic what we would like to talk about what we would like to talk about is the overview to give you an overview about the project structure maybe I would take that yeah sure all right so on top you see Trans-Gourmet Group so this is the client also you see Zerkross Trans-Gourmet Frische Paradies and Ligman these are the POs so the brands of Trans-Gourmet Group so it's only displayed here four of them but these not all so guess had something someone a number of brands in your head like could you give me a number what do you think how many brands Trans-Gourmet has so we're talking about more or less 20 so it was quite near me so before I was responsible to talk to every PO like day by day to check their needs the business requirements and yeah to see what we are doing next and fixing stuff take care but then also Kerstin joined the team of Trans-Gourmet and now she's like responsible to take like like the leadership for the POs collecting yes everything together so this was a really good help and right now she's collecting for every PO so this turns from PO side to stakeholder side because right now Kerstin is my new PO on my side because the other ones are reporting to her and not to me anymore so as you can see there is one ex-internet so that's more or less my person also the team behind and for you and your customer what Kerstin mentioned there's another agency also working for Trans-Gourmet as you can see here we have Trupal CMS the design system shop app and product so these are all teams teams which are we manage together so they are all connecting to each other so Trupal CMS is doing together with the design system and app and shop so they are all in relation damn I already mentioned Kerstin consolidate everything from a business side so everything what she gots reported to her from CMS shop IT and compliance she collects and then there is a information communication between her and me all the time I'm collecting all the stuff putting into features and also we have meetings but more or less we are putting everything I'm putting together with the team everything together that with the project teams can then focus and work on their like issues and daily business this is what I said that our team can focus by creating focus the team can concentrate and important issues and also the knowledge could be shared so this is very very important in this big volume of projects and PO stakeholders from business side from client side all together all right I can also say something you don't thank you so yeah let's let's talk about our workflow and as we mentioned before we had a one of the huge biggest challenges we both faced this year was a switch from one tool to add to the other we had a really nice workflow in GitLab and then the client like our our side had the idea to combine all the teams in one tool so we can work easily together and that's actually true it's a good thing but for us it was like one of the hardest really hardest things to adapt to a tool which we never worked before and also create a new workflow that fits us actually and one or two tiers were falling actually in this process which yeah I'm happy that we actually managed to have now an Azure DevOps aboard which all the sections with a product for the product owners or stakeholders which I'm managing so this is like my playground this board I'm yeah receiving all the requests from all the stakeholders sorting them in discussing with them sending them into refinements getting them back letting them approve before it goes into the sprint and yeah this is mostly basically my my work oh yeah this was happening actually before and one excited still in GitLab but now we're like sharing everything um so this is like the feature board is like my my responsibility and the sprint board is Cariens so yeah so we have like feature boards feature boards we have also templates that the PO or stakeholders can provide all the information without asking again like could you share a link could you pass this in so I think everyone knows about this situation we create a template as Kasten already mentioned we have six stakeholders in the project of CMS here they have business requirements they have maybe ideas what they want to have on the side and also Kasten is then collecting everything and check if there are similarities so we have also a site all so to oversee all the business needs yeah so to say yeah as you mentioned this is your playground my playground is more on the sprint board we have a for sprint week cycle a structured workflow and we're having user stories in and flaws so and of course with a robust workflow and collaboration I know or everyone knows there are meetings meetings meetings meetings meetings all day long we have dailies we have refinements we have reviews retros plannings like this is for the whole team that they have to participate but also me as project manager I have also meetings like product team team team daily where all the stakeholders are sitting in and talking about specific topics what comes next then we have the product planning meeting alignment meeting and so on so and also for communication we have not only features we have where we communicate we have slack channels for each stakeholder and for each team where we can like share maybe topics which are not good working or working quite well we have the feature communication asset and also emails and also we internally communicate with teams it's always like a struggle to also get into teams calls right we have that a lot that Karin writes me like it's taking too long why I can't go in so this is like in between so I'm actually happy with like so for me you could do it just was like and then yeah I want to talk about the topic also about the stakeholder alignment and something that we actually developed almost a year ago we came up with the regular table for all stakeholders in German it's called stammtisch so and yeah it's actually I hosting I'm hosting it once a month regularly in the last week of the sprint so we can still discuss open topics or something that is very crucial and this meeting is also there to align with everyone in the team that has ideas or requests I'm I'm seeing all of their requests before in the planning weeks we have and here we discuss does it make sense for your group or does it make sense also for yours so I'm collecting the ideas and also their wishes and present them this can we do as a team and it goes easier through the development if we actually send stuff like these requirements or this new feature or new paragraph as a team and when it's not only one single thing and this meeting is there to yeah to to align with everyone and I think since I'm doing this everyone is happy and doesn't feel left out from the client side because for before it was very much someone talked here someone talked there and no one was really yeah happy with this process so I'm really proud of this that is actually working very well and of course everyone has their their bad points here and there so they can also complain about the agency a little bit which I'm also discussing then later with Karin of course but yeah this is the appointment where they can also like yeah stick why is this back appearing again or usually stuff like this and then the next topic we have on our agenda is a little bit about quality assurance and this is a little bit of a mixture because both our teams are working together so it starts by when a developer is developing its task is testing it then reviewed by another developer and finally checked from the project manager before it goes to client side like to us and on our side we have a testing team which is actually doing the same testing the user stories or bugs or whatever does reports and also when everything is approved creating a review note for the next review meetings so everything is already there as we need a single point of truth for all our stakeholders that they know okay I can look look into this page and I know okay exactly this will be deployed for my project on this day this is very very much helpful that we came up with this process and yeah the final goal for the goal life to production is given by the stakeholder by the the owner of the website this is not me it's not Karin it's like directly them that the last test before we deploy is from from our side from client side yeah and what is really really cool about this process that the stakeholders know exactly when we deploy it's always Thursday so they can prepare their testing they know when they have to to do their job that all the flaws of course can be checked before on test all the dependencies that we have between shops and websites which can be a lot sometimes can be managed before and also manage from them and yeah it's also very effective to have this kind of collaboration communication with all of them okay so I think we're nearly the end right this was faster than expected so let's start with a little wrap up so just a short summary because we talked about workflows structure focus and so on so we said like this is the most important topic for us it's the structure that we have in the meetings on the board in documentation and like also with knowledge sharing is quite the most important part here but also focus is very important and the structure belongs to the that everyone can focus so when there is no structure that can be also less focus yeah and also the passion that we were talking about that the project has so much like growing important potential exactly so that every person has yeah which is working on the project has like new ideas like not only from client side also from our side and it's incredible to see how this project is growing and growing and we are now with 19 websites live and also with shop and app and yeah so and I also must say me as a client being part of this team it doesn't really feel like it that I'm the client for me I'm it's like my team I really like all of my team members and I really cherish their ideas and we develop really good together and every day I'm in the daily and it's it's it's a pleasure really I wanted to say that and that's why it's very nice to hear and that's why our next slide as you can see all the team and yeah we're definitely nothing without you and the Drupal community to to do this this project and and everything and it's it's absolutely for me it's a very nice experience to be yeah to have this this this team team ship with you Karin also the spirit to to grow as you can also see in the next slide it's we're having very much fun with working and we really think I like and this they are also hard times it's not always good yes I want to say that but we have good times usually yes don't don't get sick again for three weeks Karin this was very hard replacing you but I managed even if I'm not on one exit the other side directly I managed with the team because everyone was there so this was really great and yeah now we're at the end and it's time yeah almost and it's time for you if you have any questions please now so first of all thank you so much for the presentation it was really insightful and really interesting I wanted to ask something not that much related to the process itself I know how challenging it can be for like first of all you have a big team right and you still have to dedicate time for people that they can do self-development I don't know like research or some courses or any sort of like ways of getting new knowledge how do you guys manage that do you dedicate like some knowledge sharing sessions or some time time within the entire workflow dedicated specifically for these courses internally it's a good question sometimes I'm asking also myself how I'm managing this but at least we said we would like to do this session together and we also investigated some hours like on the side not like always in the time but yeah I think we're coming to this situation that we that from my perspective I have more time to investigate also in like growing also and go on a session make like this topics yeah also the devs yeah true of course hello thank you for the presentation was really good and also have a question I think it's mainly for Karin so as far as I understand a 1x is using like git lag for project management tool and also transfer met before but then you change the Azure internally you are having two to the two tools at the same time or are you using completely asia for everything with this like how you manage for example time tracking from the developers if internally you are using another tool now me also like the team is using Azure there's also good lab on our side but we're not using it with this project so this is connected with our self-development tool I guess tracking Diego help me out yeah time tracking so this is connected and everyone can track his time like on the issue directly question is how did you design the workflow basically I remember starting with the board with the feature board which has no structure which was just rows and ideas we have how to structure but this was every time I looked at this board it was killing me it was just a huge huge carpet of things and was not really structured so we really needed to to think about something and as we grew with to use this tool we figured out how to actually separate it in different lines and then sort it new so we could actually have a structure which is like each each website has its own row and then we could start also creating the different state here a feature is in so for example we start with feature new then each stakeholder is taking their feature and drawing it into the po request column when I have the plannings with all of them I discuss each feature with them if it makes sense or send it back or if we have to consult maybe one of the developers before and then if this is approved I will move everything into refinement it will be refined so everyone and it's estimated of course very important estimated so we can work with this and yeah after refinement I will ping all my stakeholders to check the refined features if this is really what they actually want when this is the case everyone moves their features into the into approved column and when everything is there and everyone did their job I will start again and plan it for the next sprint the sprint after or the sprint after it also depends if another team is involved if we have to do a design or if the shop team has to develop something that's always like you never know even when you start in one sprint it could take like two to actually finish so it's always always a thing so but yeah that we had also keep in mind to actually create a workflow which works for us so I hope that answered more or less the question with multiple agency is one elite or is it just a partner a joint partnership how do you deal with conflicts if both are working on the same code base at the same time so first of all it's a joint partnership so we have this a product team meeting so they are also not a product like not stakeholder how to say I mean from the agency from for union customer what I showed their management board or yes a mixed management board yeah exactly so they are also responsible responsible and we're just sharing this and how do you deal with the conflicts in both are working on the same code that's not the problem because we're not working on the same code as I say and then what e-commerce so the question is what e-commerce you use and how do you integrate it with Drupal this is a question I would like to raise in the audience for someone who is involved in the development it's commerce tools yes but there wasn't there's I just can't say commerce tools that's basically all yeah please hi it was at me but I like the question we don't talk much about e-commerce in the convention I think you use commerce tools as a as a solution and my question is there is Drupal commerce why do you use it yeah this is a good question this was decided before we both joined the project actually so you got us more or less on guard but you don't have the answer someone comes to our rescue hello everybody I'm Ruben I've been the solutions architect for Tromsky for the last four years and it was indeed a big challenge right so Tromsky has many of those S&P high perspectives and ARP systems and it was obvious that it cannot integrate each single one with site so we had to create this layer where we abstract all commerce processes together with commerce tools now we have this unified layer and we actually do this individual integration but it's a standard interface for all the sites feel free to like come to the booth we can have a little bit of conversation around that if you like okay thank you very much for your help and then there's another question is more communication happening in meetings or in tickets how do you keep documentation up to date for new product managers or developers oh yeah very good question actually and it's still a challenge we are facing I mean the communication is a lot in our user stories so we also keep it there to not have yeah for the documentation so not have stings and slack or in what else emails when I will not be using emails it's just me and Karin yeah but there is a lot of documentation in the old tool and the new tool but we still are building this documentation now in the Azure DevOps wiki so it's it's work in progress now because since we switched and I see there's a lot of needs that we have proper documentation also for all the content editors that's more basically also my my job to provide proper documentation for everyone who works with the CMS but yeah it's still work in progress it can get definitely better boy would be boring if we have already managed everything right so definitely we're going to save the slides okay question is do you have different features or only different design systems on the website yeah we definitely have different design system as castan also said and we have different features yes more or less I mean when a PO or stakeholders requesting a new feature then mostly we're also sharing this with the other websites so it's mostly everyone has the same features then thank you all