WEBVTT 00:00.000 --> 00:07.000 OK, so thanks for joining. 00:07.000 --> 00:13.800 The next presentation, the next talk, will be open projects, a review of the latest features 00:13.800 --> 00:15.800 and innovation by Will and with Lidon Thal. 00:15.800 --> 00:17.800 Yeah, thank you. 00:17.800 --> 00:27.480 This morning, I saw you are doing the latest and greatest of the next cloud and that was 00:27.480 --> 00:28.480 really intimidating. 00:28.480 --> 00:35.560 So, bear with me today, this now has not the same level and quality of an ease and 00:35.560 --> 00:38.720 shownness of the presentation anyways. 00:38.720 --> 00:44.720 So thank you for letting me give you a little review of the latest features and innovations 00:44.720 --> 00:49.760 that we had in built and integrated into open project in the last year. 00:49.760 --> 00:56.520 So since the last first term, 2024, but made a quick introduction while it's open project 00:56.520 --> 01:03.520 is a collaborative project management environment that can do both classic project management 01:03.520 --> 01:10.200 as well as agile and combined the two into a hybrid solution. 01:10.200 --> 01:13.400 Hands up who does not know open project. 01:13.400 --> 01:17.400 OK, there's not so many of this cool. 01:17.400 --> 01:25.120 So then this is the right form because it actually just talks about what's new. 01:25.120 --> 01:28.920 Before we can talk about what's new at open project, we need a little bit to look at 01:28.920 --> 01:32.680 who's building open project and there's actually quite some news. 01:32.680 --> 01:39.960 Now in the last year alone, we added 13 people to the team, brilliant people, but you 01:39.960 --> 01:45.320 know, like we come from this from a size of a company or organization where everyone 01:45.320 --> 01:51.960 was everyone, everyone knows who knows what and we needed to find a new, where new organization 01:51.960 --> 02:01.360 how we can distribute responsibilities, road maps and also like focus simply focus in the 02:01.360 --> 02:02.360 company. 02:02.360 --> 02:07.080 So we introduced something that is called streams. 02:07.080 --> 02:12.440 So basically it means like instead of having one big chunk of people, we said there's 02:12.440 --> 02:19.840 a team for this team for that, every stream is in charge of a strategic goal, a strategic 02:19.840 --> 02:26.360 idea of open project and then everyone can have his own road, little road map, a smaller 02:26.360 --> 02:31.680 one that is controllable, that is more easier to understand, we can better prioritize what 02:31.680 --> 02:36.440 is important in every single, in every single smaller road map. 02:36.440 --> 02:41.240 So we have a road map here for that stream, another road map. 02:41.240 --> 02:47.480 And these streams, they work on these streams work on features and they built and have a feature 02:47.560 --> 02:49.720 ready when it's ready. 02:49.720 --> 02:55.720 In the years before we had like four bigger releases in year, so we had to wait until all 02:55.720 --> 02:59.960 the features are ready so that we can prepare that only thing, that baby that we are 02:59.960 --> 03:05.680 giving birth to, and we changed that now completely because there are too many events popping 03:05.680 --> 03:08.440 up in every stream like this, features ready, this feature is ready. 03:08.440 --> 03:13.280 So what we simply do is now every month release. 03:13.280 --> 03:19.440 And that's every month, a baby, based on something like that, interesting, was the good 03:19.440 --> 03:20.440 side of that? 03:20.440 --> 03:24.560 Well, the bad side is pretty stressful, all the QA and all that stuff. 03:24.560 --> 03:29.240 The good side of this is people can simply develop in these streams and they're ready 03:29.240 --> 03:33.360 when they're ready and it will be released at that moment. 03:33.360 --> 03:39.440 The good thing is also that with these quicker and earlier releases, you get more feedback 03:39.440 --> 03:45.200 in and you can drop the little tiny roadmiss that I was talking about faster. 03:45.200 --> 03:52.400 So the feedback comes in and we adopt our roadmap in every stream, according to it, 03:52.400 --> 03:55.960 and of course people wait less for the new stuff to arrive. 03:55.960 --> 04:01.240 What was also very important in 2024 is it's not a small thing, it's actually a pretty 04:01.240 --> 04:08.080 big thing, that was the release of Open Desk and Open Desk for those that don't know 04:08.160 --> 04:18.640 is a initiative by the German Federal Ministry of the Interior, providing a sovereign workplace. 04:18.640 --> 04:26.920 Alternative to Office 365, where actually known software opens also up and has worked together 04:26.920 --> 04:34.520 to provide one alternative, and we're pretty involved there, and that you can imagine 04:34.520 --> 04:44.760 if you integrate with next cloud or with elements or X-Liki, then you're busy with designing 04:44.760 --> 04:49.160 and thinking about those integrations to get them going. 04:49.160 --> 04:55.520 So there was a huge last year and it still is. 04:55.520 --> 05:01.080 So my presentation will go a little bit long, those streams, the development streams that we 05:01.080 --> 05:04.360 have and show a little bit of things. 05:04.360 --> 05:11.640 The one thing that we came up actually was induced by one of our bigger partners in clients 05:11.640 --> 05:19.880 the city of Kalon, they have 5,000 projects at the same time, it's like that is a lot. 05:19.880 --> 05:25.960 And of course if you're a user of such an environment, you want to mark those that 05:25.960 --> 05:31.360 important to you, just to mark them favorite, so we got that in and it's much easier now 05:31.360 --> 05:35.120 to navigate the project list for them. 05:35.120 --> 05:42.240 But they also are hungry for more, so as I said, like 5,000 projects, how do you manage 05:42.240 --> 05:43.240 that? 05:43.240 --> 05:48.360 It's like, you know, before that we were managing projects, the task, the project plans, 05:48.360 --> 05:53.840 inside of our project, and now suddenly we need to manage sets of projects. 05:53.840 --> 05:59.440 So the requirements they brought to us were like, yeah, we need to track who's the 05:59.440 --> 06:03.840 product, a project owner, we need to know when it's the start and the end, we need to know 06:03.840 --> 06:09.960 the risk, so all sorts of other attributes that they need to attach to a project in order 06:09.960 --> 06:14.960 to make it manageable, for example, is that a new kindergarten or bridge that new project 06:14.960 --> 06:17.800 is that an energy saving project. 06:17.800 --> 06:24.160 So we made open project now, yeah, you could configure it, have attributes that you can 06:24.160 --> 06:29.360 see it here on the right-hand side, whatever you need, you can put there as a attribute 06:29.360 --> 06:36.160 of a project, and then later, of course, you can also filter on them, save that filter, 06:36.160 --> 06:41.920 that query, give it a name, make it a query for yourself, make it a query for everyone 06:41.920 --> 06:44.560 or just shared with individuals. 06:44.560 --> 06:50.320 So that makes it easier to control a whole set of projects and to know what you need to 06:50.320 --> 06:54.120 find out. 06:54.440 --> 07:02.200 We will continue to go ahead, things that will come will be more like portfolio management, 07:02.200 --> 07:08.840 also like a canvas where you can see access, and by prioritizing projects against each other, 07:08.840 --> 07:15.160 recording to whatever value you choose, and yeah, the end game would be really like resource 07:15.160 --> 07:22.600 management and people assignment, but that's stuff that needs to come step by step. 07:25.080 --> 07:29.960 Another stream would be, which is a bit more known here at the first time I've been talking 07:29.960 --> 07:37.640 about this in the last two years here, it's like the document workflows, formerly known 07:37.640 --> 07:43.560 also as the next cloud integration team, and yeah, basically from the next cloud integration, 07:43.560 --> 07:49.000 where we have, we link workpacks and tasks and open projects, two files and folders in 07:49.000 --> 07:58.040 next cloud, and where we also do more stuff like we provide special project folders in next cloud 07:58.040 --> 08:05.800 that are accessible, we manage the access directly via memberships and open project, or having 08:07.320 --> 08:13.000 project templates with template tasks linked to template files in next cloud. 08:13.320 --> 08:21.160 Yeah, we basically took that thing and were asked by a client, I can tell the name because 08:21.160 --> 08:28.760 it's a happy sponge, a Deutsche Bahn, to adopt that to SharePoint. Without okay, that could be 08:28.760 --> 08:37.240 interesting, the SharePoint is the big player of fire management, and maybe it would open 08:37.240 --> 08:44.600 us doors to get, you know, like the barrier down to get, you know, the rear of the first, 08:44.600 --> 08:48.280 let's say open source application in the environment that can still use this stuff, they don't 08:48.280 --> 08:55.320 need to change the whole thing at the same time. There was the idea, and the, you know, 08:55.960 --> 09:01.320 in the hindsight, not the same buzz, you know, it was much cooler to integrate with next cloud, 09:01.640 --> 09:12.680 the values are more aligned, and yeah, afterwards we were cleverer, but it was a huge project, 09:12.680 --> 09:18.920 and there's a huge nice piece of code, my, my people did a great job there, but yeah, 09:18.920 --> 09:26.040 anyways, let's move forward to something that is really having energy. In, yeah, in, that are them, 09:26.120 --> 09:31.960 when you're having meetings, or when you think of meeting agendas, like let's think about this 09:31.960 --> 09:38.840 for a second, are you prepared? Do you bring relevant stuff? When do you know what to bring? 09:40.120 --> 09:47.160 So for example, an open project where you have a plan, or you organize work, and you come across 09:47.160 --> 09:53.160 a question at some point, and then this, this point, and time, you say, I should bring it to 09:53.160 --> 09:58.600 the next meeting. We should discuss it there, right? And we build something, the meetings module, 09:58.600 --> 10:03.800 we can simply say you can see here an epic, which is an work package. It can simply 10:05.240 --> 10:10.200 take that work package to the next meeting, by choosing what meeting you want to, to bring it on 10:10.200 --> 10:14.440 the agenda. So it's out of your head, you know, it's there, you will talk about it, fine, you can 10:14.440 --> 10:21.240 leave a comment cool. But then this iteration one, then the iteration two comes in, like, yeah, 10:21.240 --> 10:26.760 but the agenda is not yet created. So annoying to create the agenda first, and then going back to 10:26.760 --> 10:32.600 the work package and adding it. So we implanted something, it's called recurring meetings, 10:32.600 --> 10:40.520 or meeting serious. So you simply say, have a weekly, have a terrific, and these meetings come 10:40.520 --> 10:44.440 again and again. I don't need to think about them. I can simply pick them again. The next time 10:44.440 --> 10:50.600 I'm at the work package, it's super easy to fill those meetings that are often empty, 10:50.680 --> 11:00.040 have empty agendas, suddenly have worth interesting and really topics that have a question. 11:00.040 --> 11:04.200 And when you're in the meeting, then you also see that there's a work package. 11:04.200 --> 11:08.040 Oh, that's the context, the question is about everyone can, in the meantime, 11:08.040 --> 11:12.920 why they're bored and looking into the screen, they can click, click around, find out what 11:12.920 --> 11:17.240 it's actually going on. What was discussed, discussed before. So it's everything meetings, 11:18.200 --> 11:26.920 and tasks, and plans are integrated. And there's something that has keeping continue, 11:27.480 --> 11:34.360 we keep updating and proving with every release. That's a really powerful thing we use ourselves. 11:35.240 --> 11:44.280 This one is like, what is it like? Is it an IT crowd? Excuse me, are you from the past? 11:46.520 --> 11:51.560 The planning and reporting, of course we have an open project there, but always had the 11:51.560 --> 11:56.680 opportunity to break down work packages and to support packages and so on. And you could also 11:56.680 --> 12:02.920 say how much work something was, but the calculations to sum it up, you know, to sum the whole 12:03.000 --> 12:13.320 tree of a work was flawed, head bugs. And it was never really prioritized enough because it 12:13.320 --> 12:21.240 is complex to fix. So we spent 2024 quite an extensive time in the planning reporting stream 12:21.240 --> 12:26.600 to fix it. I was pretty tough now, but now you can say, okay, this thing takes that much time, 12:26.600 --> 12:34.920 we already did that much and it accumulates all upwards to meaningful numbers. And yeah, 12:34.920 --> 12:40.200 we're proud that we can finally afford it, you know, like the company has that side to fix 12:40.200 --> 12:49.640 all stuff that has been around for so long. And another one that was asked from the community a lot 12:49.720 --> 12:57.080 is okay, adding to work package relationships, like a follower and proceeds, you sometimes 12:57.080 --> 13:05.240 don't want them to be directly following, let's say you build a basement of a house with concrete, 13:05.240 --> 13:11.400 it needs to dry right before you can put up the walls. So that time distance, that's called lag. 13:12.120 --> 13:19.480 Now our relationships, much relationship model allows that to model that into into your project plan, 13:20.360 --> 13:28.440 and again, visitor from the past, people asked us so often, could we please export gunshots 13:28.440 --> 13:36.680 as PDF so that we can print them? Why it's that? We can put them into some meeting materials, 13:36.680 --> 13:42.680 we have put the link. Whatever, there's a thousand of reasons they finally got the PDF export 13:42.680 --> 13:49.720 for the gunshots. I don't know what they do with it, but they got it. That one is really nice, 13:49.720 --> 13:58.680 that's the thing that is basically coming out of my hands. You know, in our team, people use 13:58.680 --> 14:06.360 element for chatting, for exchanging real-time messages, and that was always wondering why are 14:06.360 --> 14:11.480 they doing this, you know, like they're talking about work, they don't have the context of the work, 14:11.560 --> 14:18.040 like, what is the task that they're working on? What does it belong to? And what happens actually 14:18.040 --> 14:27.480 to the discussion the next day? I don't know. I don't find stuff in messages. Maybe I'm not 14:27.480 --> 14:35.080 skilled enough, maybe I'm from the past, but I don't find information there. So discussions are 14:35.080 --> 14:39.400 going, which is also good and nice feature times, that you can, you know, things are volatile, 14:39.400 --> 14:44.360 and fly off. We said, okay, let's turn that around. Let's take the open project, 14:44.360 --> 14:53.160 notifications, and then make it a little bit more messenger-like. So with one more, it's 14:54.440 --> 15:03.000 15, oh, I think. We changed it so that you have more, like, something like a GitHub pull request, 15:03.960 --> 15:09.880 a formal style of KV, that the changes in a work package, combined with a feeling of a chat, 15:09.880 --> 15:16.760 so you type something and it moves up, and also when somebody else writes something, it comes in 15:16.760 --> 15:25.240 automatically. Or what is faster to respond to a good comment than just giving a thumbs up? 15:25.240 --> 15:31.000 I've read it, I've understood it, and I agree. Just a thumbs up. We didn't have it, we simply had 15:31.000 --> 15:36.680 it simple text form back before that, and I had to fight a lot of fights internally and externally 15:36.680 --> 15:44.040 to get this into open project, because people were scared that it would lose the contractual 15:44.040 --> 15:52.120 way of commenting on work packages. The formality. Yeah, but then you go to the messenger 15:53.560 --> 16:00.200 to have not be formal, right? So yeah, so we worked on that, and we will continue working this 16:00.200 --> 16:06.920 next thing should be, like, reply functions and threats and so on. And then still, we will need 16:06.920 --> 16:12.920 to have the messengers, and we will still need to have these rooms where you can say, hey, 16:12.920 --> 16:22.360 today am I childish sick, I need to stay at home. Another one, convenious feature is a very simple, 16:23.800 --> 16:27.400 you know, just you need to remember something, and you don't want it to this actively, 16:27.480 --> 16:33.800 you don't want to put it into a can, and just set an alarm, and then you will get an notification 16:33.800 --> 16:40.680 once it's there. There's actually also a sponsor by the city of Kalon. 16:43.880 --> 16:49.880 Also, community in a contribution, at least in the beginning, there's the GitLab integration, 16:49.880 --> 16:56.520 so the idea is to, you have the project management environment or working project, where you can 16:57.240 --> 17:03.880 support the whole organization, and then you have the software development part, 17:04.520 --> 17:08.600 which is just one aspect of the whole organization, let's say you're marketing, 17:08.600 --> 17:14.200 you wouldn't have marketing in GitLab, right? But in GitLab is optimized for code management, 17:14.200 --> 17:21.080 you're working on code, I don't need to tell you, but with that integration, you can simply link 17:21.160 --> 17:26.920 merch requests with work packages, so that you know, okay, if that work package is an epic, 17:26.920 --> 17:32.040 a feature, a bug, you can know in what merch request it is built on, and what is the status of 17:32.040 --> 17:38.840 that merch request? Is it already, I don't know, how did the pipelines run, is PCI green, and so on? 17:38.840 --> 17:46.680 That's really, really nice feature. As you might have noticed, open credit change a little bit 17:46.680 --> 17:53.080 and they look in fear lately, in the last two years, and the reason is we adopted the GitHub's 17:53.080 --> 18:01.320 open source design system called Primer, and GitHub also, and the same as GitLab is Ruby 18:01.320 --> 18:09.400 and Rails application, so as we are, and by adopting to their front, and it was easy also to adopt 18:09.480 --> 18:16.680 to their accessibility features. One of them is that you can easily have a high contrast mode, 18:16.680 --> 18:23.000 and that came actually through that Primer approach, and the good thing about that is also, 18:24.440 --> 18:31.560 we could finally get a dark mode. Yeah, that was nice. Thank you, Henrietta. 18:31.640 --> 18:42.440 That turns out more features that we implemented in 2024. One more thing that's worth noting 18:42.440 --> 18:47.320 is a custom field. You know, custom fields are these fields that you can add to work package, 18:47.320 --> 18:52.440 and store some additional data. We already have like, I don't know, strings, numbers, lists, 18:53.240 --> 19:00.280 what was missing was a hierarchy, a tree, and so you can have like a department structure. 19:00.360 --> 19:06.200 You know, every organization has a department structure, or a skill structure, or a building, 19:06.200 --> 19:11.960 or a place structure, okay, this office in the town, and this building, and that floor, that room. 19:13.320 --> 19:16.600 All these things that you can now do with custom field of type hierarchy. 19:19.080 --> 19:22.200 Yeah, anyways, what is up in 2025? 19:23.160 --> 19:32.680 Cliffinger. We are working on a mobile app, and it's already internally in alpha version. 19:32.680 --> 19:40.120 It's not yet in that shape that we want to present it to the outside world, but we're working on 19:40.120 --> 19:46.200 it, and we also fighting internally about what is actually the best use case for it, so if you 19:46.840 --> 19:54.760 have strong opinions about it, please come to me. And if you're a flutter developer, please come to 19:54.760 --> 20:09.320 me as well. We need help there. That's another baby of mine. For 2025, we just had this discussion 20:09.320 --> 20:15.080 here about integrations, and I talked about the technical fundamentals that need to be solved in order 20:15.080 --> 20:23.000 to make integrations between rich applications that have users easier. And I really, really, 20:23.640 --> 20:29.640 promote that we stick to a couple of standards when it comes to integrating applications, 20:29.640 --> 20:35.720 and especially users, because it's incredibly hard. It's incredibly expensive, and it blocks 20:35.720 --> 20:39.960 all the good initiatives, the all the great ideas that we have, and it's okay, it would be cool to have 20:39.960 --> 20:44.440 that application plus that application, the one plus one equals three thingy. 20:45.080 --> 20:52.120 Yes, but having the fundamentals, not there, makes it really, really hard and expensive to get going. 20:52.120 --> 21:00.280 And you do shortcuts that are not fun, that are not good. You leave security, you don't do the 21:00.280 --> 21:09.320 right thing. So what I promote here and what we're actually doing is building a couple of 21:10.040 --> 21:19.240 implementing a couple of open standards. Let's say OIDC, job tokens, token exchange, 21:19.240 --> 21:26.840 the OAuth token exchange, and for user provisioning, this can protocol. If we have those things, 21:26.840 --> 21:35.720 then we can basically orchestrate when is a user available by provisioning. And it can be in a moment 21:35.720 --> 21:43.560 where in someone creates a user, a guest user, a user that I won't plan to work with in the 21:43.560 --> 21:48.200 future, and that user doesn't know it yet, but I already assigned tasks to that person. 21:50.040 --> 21:55.640 And I already need to prepare that the full is accessible in next cloud. We also need to solve 21:55.640 --> 22:02.120 that once that person boards on and does the first login, it doesn't want. It doesn't need to 22:02.120 --> 22:07.800 think about open project or next cloud or whatever, because it's too much in the first day of 22:07.800 --> 22:14.280 work, what did the application MIA and I don't care. I'm in open desk, open desk. Yeah, what is 22:14.280 --> 22:20.680 next level is open, probably you can hardly see. So we need to solve that. And fortunately, 22:20.680 --> 22:27.480 we're working together with next cloud and with open desk and other vendors to at least in this 22:28.440 --> 22:33.960 group of people to establish these standards here. That's something that is for me very, very 22:34.840 --> 22:41.160 from the heart, because last year we struggled a lot. We're making it to make it really 22:41.160 --> 22:49.960 user-friendly at the end. Then of course, further integrations, we want to integrate with Exleaky 22:50.280 --> 23:00.680 to take a little bit the adlation monopoly of Confluence and Jura. So yeah, Exleaky is the 23:00.680 --> 23:05.880 Confluence and open project is the Jura. In that case, I'll expect something to come in 2025. 23:07.560 --> 23:11.320 And remember, integrated with stronger. Thank you. 23:20.360 --> 23:24.680 Thank you, Villand. We have two minutes for questions. Any question? 23:28.840 --> 23:32.200 Wow, no question. It was crystal clear. 23:34.360 --> 23:34.760 Yes. 23:40.920 --> 23:46.360 Hi, I have a question about the mobile app. Is it designed for smartphone only or for tablets too? 23:46.360 --> 23:50.360 Because I think it's an interesting use case to use such tool on tablet. 23:51.320 --> 23:55.320 Yeah, I agree. It is actually designed to also work on desktop. 23:57.960 --> 24:03.560 But yeah, let's take it step by step. So first thing would be mobile. Many people have 24:03.560 --> 24:09.000 mobile but don't have a desktop computer and teams work distributed on a mobile setting. 24:09.160 --> 24:17.160 And we would start there. I know it is exactly what you are talking about. For example, 24:17.160 --> 24:23.160 from a construction site, you usually have tablets because you want to see plans and so on. But 24:23.160 --> 24:30.200 then you have the simple workers that just need to get a task. It depends a little bit on what is 24:30.200 --> 24:40.520 of first use case. And it's probably the communicator part. It's just getting messages resolved 24:40.520 --> 24:51.320 and out of your inbox. The interesting thing to hear your use case later, we can talk. 24:51.320 --> 25:00.360 Yeah. In my company where we are a engineering firm, we are using extensively open project 25:00.360 --> 25:07.880 for organizing our work flows. It was really useful for the review process. That the task goes 25:07.880 --> 25:16.520 from a project, from a designer to a reviewer. And we use the custom actions with buttons to 25:16.600 --> 25:22.920 approve or reject. And it was really useful. So thank you for this jewel. 25:22.920 --> 25:31.480 And I am interested in what you say about the new features, about the planning of the resources 25:31.480 --> 25:43.400 and assignment to people. That will be useful for the management to know how much a single person 25:43.400 --> 25:55.960 is doing what it's planned to do. Yeah. The question here is, what are our plans for resource management 25:55.960 --> 26:03.000 now? And there is, we are not yet there. We do first do with a portfolio management. They can 26:03.000 --> 26:09.800 break it down and you need to assign resources later to projects or to phases of a project. 26:09.880 --> 26:18.680 Probably not on a work package level. So the idea would be to help people to get an idea 26:18.680 --> 26:27.240 how do they have enough people? Are they overworked? Are they overbooked? That is the kind of 26:27.240 --> 26:31.800 question that we would like to solve there. But we are not yet in that position. 26:31.960 --> 26:40.200 Thanks for some match we learned. Well, we don't have any more time for questions. So I think 26:40.200 --> 26:45.560 that if you have any other questions, you can ask in directly in the whole way. Thank you very much.