Name: [Live Demo] All-in-one Project Management with BigPicture
Uploaded: 2025-02-26T15:16:13.571Z
Duration: 53 min 52 s
Description: [Live Demo] All-in-one Project Management with BigPicture

Transcript for "[Live Demo] All-in-one Project Management with BigPicture": Alright. Hello, and welcome. We're gonna get started here in about one minute. We're gonna give allow just about one more minute for everybody to, see if we can have more people join. So let's hang tight, and then, we'll we'll we'll give it a roll. Alright. Just a few more seconds. Welcome, everyone. Appreciate all of you joining today. Alright. Let's go ahead and get started. So hello, everyone. My name is Shane Garnett, and I'm a senior solutions advisor with Appfire. And, I'd like to get started with a little bit of housekeeping before we continue. So number one, we are here to look at, Appfire's portfolio management solution, big picture. This solution is installed in the Atlassian environment and in JIRA. So heads up, that's what we're talking about today. And a couple of more things. Joining us today, is, Yani and, Ran from Methoda. Would you, gentlemen, please introduce yourselves? Yeah. Hey, Shane. How are you? Hi, everybody. I'm Yaniv. I'm the CEO of Methoda. We have been a partner of Upfire for a long time and working the Atlassian ecosystem, providing PPM solution for a lot of long time now. So, I'm excited, to go through, our session today. Excellent. Hi. Hi, all. This is Ran Lavey from Metoda. I'm vice president at Metoda, responsible for, PPM solutions, passionate about, helping our customers with, those kinds of solutions. Oh, excellent. Thank you, Ed. If I forgot about, my colleague, Lukasz, Lukasz is on here as well. Wukash is going to be answering questions. That reminds me of the next piece of a queue of housekeeping. So what we want to do is that you'll notice that you have a chat and you have a Q and A. If you don't mind, as the, as the the webinar continues, place all your, answers over in Q and A and Wukash, Ren, Yani, they will be in there answering your questions. And then at the end of the webinar, we'll get to those questions as possible. Okay. Before we dive into big picture, one of the things that that I find very important is is foundations. Today, we're going to discuss resource management. Before we get to resource management, if you don't have that minimum effective dose set in your workflows to ensure that, as an example, that assignee is set, we're gonna have some mixed results as we're trying to plan out your portfolio. Yadeev, would you like to jump in on this one on this topic a little bit, please? Yeah. Of course. Of course. Yeah. We we see that a lot of people have the goal of managing resources, planning resources, but not necessarily have the data. You know, we need some infrastructure data to actually do that. We need a methodology in place to to think about how do we measure our task. Do we actually have estimation? Do we manage priorities? We need a lot of data to support, an effective resource management and, you know, and and that's something critical. Not everybody is doing it well. Yep. Excellent. Excellent. Thank you. And then one more piece of housekeeping, and we'll be done. One more piece of foundations. Again, we're looking at a portfolio management solution today. Well, it's one thing to go ahead and just throw it into a Gantt chart. It's another thing to have not prioritized your work before we throw it into that Gantt chart. Another element, Janne, I wanna throw this back to you right quick, and then we'll get started in the big picture. But walk us through a little bit about the the backlog prioritization, please. Yeah. Well, we, a lot of time we just, you know, we think of a Gantt or a timeline, and we just fill it with tasks, you know, going through some kind of a process. But we understand today that prioritizing your tasks, understanding what should be done as a highest priority, that's critical for planning. That's critical for understanding the way your resources will be, managed. Also, your timeline is gonna look like. And, you know, when working with Jira, we have backlogs. We're used to that. But a lot of times when we use GANs and timelines, we're missing that. Understanding that priority is part of the basic data for any backlog, whether it's a, you know, a sprint or a huge project. Right? So I think it's critical for us to understand that priority is a critical path step in our planning process. We have to prioritize everything. Yep. Excellent. Excellent. Thank you. Okay. So So let's get started. What are we looking at? Big picture again is, our portfolio and management solution. So, once installed, the first thing that we see here is a home directory. This home directory, serves as a summation, as an amalgamation of everything we're going to configure underneath this. Now we'll get to that. The one thing that I want you to notice here before we get started is that within our home directory and within every box that we're going to configure, notice that we have all of these modules. Now we'll cover quite a few of those today. Again, you'll have the ability to turn those on or off for each different thing that we configure. Usually not all of them are on. We usually will get our templates will automatically come preconfigured to handle that. So what are we looking at here? So on this left hand side here, you'll notice that we have program and agile and all of these different things. In big picture, we call these box types. So what does that mean? Big picture is a robust tool meant to meet your project no matter the project management methodology. So we want to meet you exactly where you are. And, again, we'll show you how configurable this is. So we have an agile template. It means that you're running sprints. That's all. We're going to configure a project, again, that has a scrum board. Right? Scaled Arc, Scaled Agile. Hybrid. To me, I know hybrid's a bit of a vague term. To me, Hybrid is you're not running sprints, but you're doing work in Kanban style, but it's absolutely in these buckets. Right? We have a beginning stage and an intermediate stage and then, maybe integration and then deployment. Portfolio, that's another thing that can be a little bit confusing. In our instance, portfolio means group. I want to group maybe like projects. Maybe I have projects that are all using time tracking or projects that are all using story points or what have you. We have the ability to group those. And then of course, I'm skipping a couple here, but, classic project, straight waterfall. We're running straight waterfall. Well, what does that look like? And I'll try not to get into the configuration too much, but want to highlight the the very important things. So if we select any of these boxes, we want to know what's in that box. So as we come down into our configuration, we will look over in task and scope definition. So we've created a box that matches a project management methodology. How do we want to populate that box? Well, we can add a project, a Jira project or projects. We can have a, scrum and or kanban board. You could populate it that way too, or you can create your own cool JQL filter. So however you want to put Jira issues into this box, we'll meet you there. Now, the only other aspect of of we'll touch maybe one other area of configuration, but the only other thing to to to point out is this. Big Picture is built on top of Jira permissions. If you can't do it in Jira, you can't do it in Big Picture. We have a couple of more areas of security to talk about. I'm going to pass this over to Yaniv and talk about the importance of governance here in a minute. But once you do configure a box, we can't leave it open for everybody to just come in and start pushing buttons in the side of this box. So we do add an additional area of security to state, release training engineer, what have you. Again, this is the beginnings of of governance and this is where Minnesota really comes in and shines and helps you. Yanivi, would you mind talking about this section a little bit? Of course. First of all, I wanna just mention, I mean, the the the initial views you presented where you can see multiple projects with multiple methodologies working together. It's this is a unique capability of Big Picture. No doubt. It's, you know, our customers are always looking for hybrid methodology kind of work. Some of them work in Agile, some not. And I think here's Big Picture Shines. It allows you to to work on different methodologies together as an organization and still look at a at a cross resource timeline, everything that you have together in one view. That's that's really unique for us as a as a consultant in this area. In terms of of the preparation here and and what's the right way to manage your permissions or, you know, the the the governance of of such an effort. So when you look at training tools, you look at PPM in this case, you have to decide, you know, who's responsible for creating time boxes, who's responsible for actually entering data into those time boxes, who's responsible for scheduling tasks, who's responsible for estimating it. You have a process that needs different people involved or, you know, some of them multiple roles. So defining the roles and responsibilities within a planning tool, this is critical. So everything will be neat and actually manageable, and I think Big Picture allows us to do that. Excellent. Thank you, Yaniv. Okay. So let's jump back into one of the best things that Big Picture does. So we're gonna look at resource management. But before we start on resource management, I do need some math. And the math is I need time tracking or I need story points. We need one or the other so that we can figure this out. So let's go in and take a peek. So there are two areas of resource, resource management. And the first one is that we'll look in our teams module and notice that we can create a team. We can have that team belong to a particular Jira, Scrum or Kanban board. But what's important is that I can capture a team member and say their their percent allocated on there. Because in big picture, we have the ability to roll up against an individual, we also have the ability to look at this again within a particular team. But we do need to know, you know, the percentage allocated. And, again, we've seen this use case from our customers again and again. Well, what if half the time they're allocated to a project that's running, time tracking? Then the other half of the time they're running, against somebody running story points. Absolutely. We can handle that use case. So that's area number one. Second area we need to do is that we need to go in our resources and define a workload plan. You know, are they working eight hours a day, five days a week? Are they working ten, four hour days? Are they part time? We need to be able to capture that that that particular resource exactly to meet their work schedule. Holiday plans. This means a little something different, for, from traveling a lot. Holiday in Europe can mean, you know, vacation. In this case, it means we want to capture PT, state, national holidays, right? When's everybody off of work? And this really does come in handy in in Europe, particularly because there's so vastly so many countries that have different schedules. Now before I go over to skills, one area is that, yes, we also will capture your absences. Vacation, true away from vacation, we have the ability to capture that as well. And the last area that we wanna capture is a skill. This can come in handy, because and by the way, this is not one to one. You can have many skill sets that map to, one individual. And this can come in handy as I give eventually, when we roll up a report, maybe we'll want to see I always use the term analyst. I need an analyst for a particular week to assign something to. Okay. So once we have that, we can then roll up a report to see if we have an analyst. Okay. So how does that work though? So the glue comes together when I have a resource and I know their read, their schedule, their workload schedule, and I know their holiday schedule, and I know their skills. Once we tie that to a Jira issue, now we can start talking about resource and capacity management. So let's come back up into our overview section in home. We'll select now I'm selecting selecting a safe art here. This works for anything. This just happens to be where I have data. So we'll bring up our safe arc, and we'll switch over to our resources module. So what we're seeing here and I should have had a better example on showing that it was over allocated, but what we see here is that Christopher has been assigned zero hours, is capable of twenty four, and here's the math. Now out of the box, it comes preconfigured. Wilkosch, correct me if I'm wrong. I believe it's at 75% out of the box. We turn it yellow to let you know that you're nearing capacity, and at capacity or overcapacity, we'll turn that resource red. Hopefully that's right. And I believe that that, is completely configurable on your end, that you have control yep. Thank you, Wilkash, to see the thumbs up. Appreciate it. So you have complete control over this, but what's important here is that notice as an example, Christopher here, there is an issue assigned to him and it's showing on this timeline. Okay. It won't show unless I have a start and end date. We're going to cover this in the Gantt module, but that's one aspect to show. And the other thing to show is yes. We want to look at this from the team view as well. Oh, is my team over or under allocated in that picture? Okay. Yanni, anything on this section you want to discuss about resource management? I think, you know, the classic way for people to look at resources is people and teams, and it's easy, you know, to look at this, view here that you see the time boxes and people. I think, yeah, start and end date are critical. And the fact that we can have multiple holidays, multiple, schemes of holidays, right, together and having people in partial, partial work or jobs within different team, that's really where you you can create and manage resources effectively. And at the same time, you can look at a team level on the agile scope and and don't, you know, don't get to the people level. Right? So you can have you can have it all again, which for us, it's, it's important for our clients. Yeah. I would add also I would add also that, many of our customers, for long term planning, they want to see only high level, estimations and high level, analysis of the utilization at the team level. They don't want to get into the details. But for the short term planning, for the next, few sprints, for maybe for the next, month or two, they do want to get, to the analysis of utilization per per individual, member. And, and, this is possible with Big Picture. This is very, good functionality of the tool. Excellent. Thank you, Rand. Then, you know, one thing to point out about these modules is that notice that I'm down in one of my folders, one of my boxes. Notice again, I've turned on all the modules. You don't have to do this. But just because we're looking at resource planning here doesn't also mean that I can't come back up to my home directory and look at resources from that way as well. And, again, I have a different view here where we're looking at it maybe in quarters or half year or how we want to aggregate it. So we can use this to push out, to look out further and further into the future. Okay. So let me go back to our safe module, the scaled agile. Again, that's just where we're using our data from. And I want you to notice, one thing for me. I want you to notice these gray box the the columns here. Now this is a United States based calendar, so it's Saturday and Sunday. It's showing when, your average resource is not available. For Israel, of course, where my my thought is, that's going to be very different. And for other countries, it could be very different. It doesn't have to necessarily be Saturday, Sunday. Also, I have to go down one level. Give me one second. Also, this is where now we also provide an API for this call. This is where you can then also come in and go, I have a person that's on vacation. This resource is on vacation. And what would happen then is that these gray boxes would be colored in here as well to designate that the resource is not available. Now why am I showing you this? Well, we're showing you this because we're going to come over into our Gantt module. And let me zoom in or zoom out. That's great. Notice those gray columns are back to designate that the resource is not available at that time. Well, one of the first things is that as you're creating this schedule, if you try, if you attempt to place a beginning or end date when that resource is not available, Notice that Big Picture will not allow you to do that. Right? So, again, we we can't schedule work against a given resource if they're not available. Alright. So a lot to point out and there's a lot going on on this screen. Another thing to point out here is that notice that we have a scheduling mode. So scheduling mode is important because a lot of times when you load a big picture that initial that that first time, maybe that start and end date are not set yet. Again, we have the ability to do that here. Maybe you'd want to kind of start pre populating some of those numbers. Now, Big Picture, if you're running Sprints, we can have Big Picture automatically populate that start and end date based off the sprint dates. We also have another thing, again, with our scheduling modes. We have auto bottom up. Now, auto bottom up means I want the children of an issue to drive the beginning and end dates. Now where this really comes in handy is let's imagine that you have, stories that feed into Jira epics. Jira epics feed into initiatives with that level above there. And you want those higher level issues to be driven by the start and end dates of all of these stories that comprise it. Really handy way to be able to set this, really handy way to be able to set your overall schedule. Now, conversely, we have auto top down. Auto top down means we have a go to market date. We cannot miss this date. So we set that parent to be auto top down, and that way the children cannot be scheduled to occur outside of those dates. Okay? Now, one other thing to point out, and I want to go to another screen to to to to highlight something. One other thing to point out here is that notice that we have these underlined symbol here. This is a baseline. So we have the ability to create a baseline against this Gantt so that you can see if your work slips. And I wanna check something on the resources here. Give me one second. This might be one where I oh, no. I do have the data. Perfect. So I wanna come back to that. Give me one second. Another aspect we have in here is that remember, big picture is bi directionally synced and we'll cover this here in a minute. It may be that you're not ready to schedule your issues just yet. It may be that that that you're you don't quite know what the schedule is going to be. So we come prebuilt with a scenario. You've if for any of you that have used advanced roadmaps plans, same concept, we have a scenario here. And a great use case for this scenario is that we bring up our resources panel and notice that we have resources that are over allocated. So in scenario mode, it means don't interact with Jira just yet. Hold off and let's move this schedule around till we see that these resources are within our allocation parameters. K. So I wanna pause there. Janib, anything on this Gantt chart? Anything that you've seen, best practices or areas that you would like to discuss? Yeah. I think first of all, again, the fact that we can have time boxes within a Gantt, different time boxes, sprints, PIs, everything we want, that's that's really where it's, brings value. You know, a lot of time we need to synchronize different time zones. And here, when you have time boxes, you can you can use it everywhere in the resource in the end. That's critical. We have customer working with PIs. They wanna see the PI. They wanna see the screen. They wanna allocate tasks. This is this is important. Second thing is that you have baseline visual indication. That's very important, to to a lot of our customers that wanna see also the the differences of over time of the original schedule. So I think these two together makes it, you know, a very attractive kind of way to manage timelines. Yeah. Alright. Excellent. And then I wanna go to a different view on the Gantt chart. I have a little one a little better because this question comes up a lot. Let me find this. Okay. So let me come back to the Gantt. This one has a little better view when it comes to dependencies. One of the use cases that we've been asked a lot, can I set, dependencies? Absolutely. We have we come with standard PM, be okay, start to end, end to start type dependencies. We can set a lag time. Let's see if I can highlight one of these. Oh, that's a soft dependency. Let me just add a dependency or not. Let's try this again. K. So, we can set a lag time. Do we wanna, you know, wait a particular day? Do we want it to be scheduled as soon as possible? Another thing we can do with this chart is, yes. Again, the use case we've been added is if I see a schedule slip, you know, can I slip all the children underneath it with that? You know, if you've set up your minutes, absolutely. We have the ability to move these objects as other objects slip in schedule. Okay. Let's see if there's anything. Now there are a lot of options that, of course, critical paths and other things. There are a lot of toggles in here. I try not to get too deeply into that. And then also notice that, again, we can push our effort modes when you push up our aggregations. Okay. So let's go back. Now we'll go back up to our home module. We'll go back into our smart house, and, again, this just happens to be where I have data. This works regardless of the module. And now we wanna look into our board module. If you ever want to truly lose track of your project, don't pay attention to your dependencies. We absolutely have to pay attention to these. Now what we're looking at here, this is, again, a scaled agile example, where I have four teams running synchronized sprints. Again, this works regardless. This is just a good example. And what we're looking at is all of our dependencies. Now the first thing to notice about these is that they're color coded. Green is good. Gold orange here means there's an issue. Red means that you've missed it. Over in this side panel here let me put this over again. You see that we have an info bar. You bring up this info bar and notice we have warnings. A great coaching tool. A great way to come in and go. There's a possible error with the way that we configured this dependency. Now, again, notice also that we can track dependencies within one team. Notice we can track dependencies across teams as well. We want to be able to handle all of this. Now, as we look at this one, now again, this is just an example of a team running sprints. Another thing that we can do out of this is PI planning. So we absolutely have access to our backlog. If it's green over here on the side, that means that it's been planned. If it's, you know, white, it means it can be brought in. And with the ability to drag and drop these into these individual sprints while paying attention to our capacity. Okay? Now one note on this capacity. This has to be set manually. Big Picture doesn't currently go in and grab your last six sprints of data or what have you and automatically populate it. You do have to populate that number, but once it is populated, yeah, as you drag and drop your member, your your stories in here, you'll have the ability to look at this, have the ability to plan out into the future, while also looking at your dependency. And, of course, these dependencies are both. Do you want a Gantt style dependency? Yes. You can put that in there. If you also want a standard Jira, this issue blocks another issue, We capture that as well. Alright. And, again, we can look at our warnings. So, Yaneve, anything as we're looking and but before I pass it over to you, Yaneve, one of the things is that this highlights two separate areas that big picture covers. A, we have to have resource management. That is one area. B, we do need to look at sprint capacity management, which is very different. Janeeb, you wanna jump in on this, please? Yeah. Just just to mention, I mean, a lot of our customers using PI planning, not necessarily doing safe, you know, as entire methodology, got the truth. But PI planning is pretty pretty strong within the customers we work. And this is, you you know, this is the way. I mean, you can see the teams. You can see the capacity. You see the dependencies. That's what you need. And and I think the cool thing about it is this, for one hand, you do PI planning with all your teams, make sure all the dependencies are ready. You have the warnings and the side that lets you understand what you have to do to make this plan work. And at the same time, you can switch and see it over again in a timeline. This is this is something that, you know, a lot of people wish they have a sort of but what they do. And, the the fact that you can see the backlog and allocate it manually into the screens, into the teams, this is, come handy. And and it's the classic. Right? It's the classic way. And I think, very useful from our experience. Makes the job. Excellent. Thank you. Okay. So this is one area of capacity planning, but if you wanna go deeper, we can go deeper as well. We have a capacity planning. So as we look at capacity planning, it will now are these numbers do you have to set these numbers? No. These numbers are automatically populated based off the Sprint. Can you modify them in case you want? Yeah. Absolutely. You can come in and modify these numbers as well. But, yes, we'll we'll Big Picture will automatically sum all of these numbers, place them here into your overall changes. And, of course, you have the ability to highlight the changes before you go back. Okay. So let's go back out for a little bit and we'll come back up to our main section and let's kind of before we dive into reporting and other sections, let's take a breath because that's a lot that's thrown at you, and let's go back. Can can I can I add something, Shane? Go ahead. Yeah. I think one thing that sometimes we miss, we need to work hard to get is some kind of a portfolio level, and it means that you wanna see a project by project or time box by time box and and see the data on it. Right? And this view, I think, may get the job done. You can change the columns. You can say, I wanna see the status. I wanna see the progress. I wanna see the you know, every data that we actually have here and arrange it as a portfolio view. And for you as a as a manager of, you know, PMOs or lead project manager, you can present a classic portfolio of everything, and, you know, design it the way you want. And I and I think that's critical. It's it's just obvious, but it's not. I mean, getting a portfolio like that takes a lot of effort without, without big picture. Okay. And thank you, Ani. And then I just saw a question come across in QA really pertinent right now. Does program increment and iteration require Jira Enterprise? No. No. Absolutely not. And on top of it, this is out of the box, big picture. And on top of it, if you have Jira Standard and you would like to create a hierarchy, usually Jira, a premium and up. That's where you can create that parent link. I have a in other words, everything above an epic. I have an epic a Jira epic, but I wanna layer above that, of an initiative, the capability, whatever. And maybe I wanna level above that. In Jira premium and enterprise, you have a parent link, but what if you're on standard? Yep. We can accommodate for that too. We can roll up your hierarchy by using issue links. So we have the ability no matter what on that. Okay. And to go back to what, Janeeb had just spoken about about a portfolio, I kind of briefly touched on that. So, and again, this is an example of of a scaled agile. Again, it this is applicable no matter how you've created your hierarchy. Remember that we have our modules here. We're gonna cover reporting here in just a bit, but reporting is a module. These all are boxes configured against the box type. So it means that I have a reporting module against a sprint. I can roll that up, that reporting module against a program increment, a planning increment. I can roll that reporting module up against the entire release train and back to what Yonahib had spoken about, about your portfolio. To me, portfolio is just a group. I want to group projects. And now, again, I like this portfolio because I can have my and by the way, there's projects. You can mix and match them. I can have an agile project here, and I can have an hybrid project here. However you again, we want this tool is built to be robust enough to meet your team exactly where they are. So I can roll that up, and that way, I can have reporting against an individual project. But I can also roll up that reporting against a group of projects. Also, that resource module is available. So that all comes together right there. So, yes, excellent question about that. Now when we look at reporting, we'll go to home here. And this is the part where we want to discuss, a difference. Now, Big Picture comes with three separate licenses. There's Big Picture, which is exactly what you're seeing here. I've shown you zero functionality that requires Big Picture Enterprise. Here's the first. Oh, I don't have Enterprise loaded on here. Perfect. So, Big Picture will give you access to these top three reports, and then we'll configure one of these reports. Big Picture Enterprise handles these bottom five. Now there are other things Big Picture Enterprise does. It integrates with Tempo. In Europe, this is a big one in Europe, your GDPR. Do you want to control where your data is stored? That's Big Picture Enterprise for an addition. And also, earlier in the Gantt chart, we showed you that you can have a scenario. Each box comes each Gantt style box, each resource box comes with a scenario, a single scenario per box. With Big Picture Enterprise, you get unlimited scenarios. That's another area. And there's a few other differences. But let's take a peek at one of these reports. So we just select a report. Notice that we can roll this up and, you know, do do do different visual methods. Group by, really cool. So with group by, it it's the ability to drill down into your data. You know, the first thing was, we're looking at a project, and then we want to look at the issue top and maybe the assignee, the ability to drill down, and these date filters. The date filter because, again, maybe you won't only want to look at, you know, data that occurred this year, as an example. So the ability to create several different reports based off what you need. And, of course, narrow down, I think the the most common use case for narrow down is I don't care about my subtask. Just show me everything from a story up or or what have you. So again or maybe you just want to look at epics. However you want to roll this up. K? And let's see if I can find you a decent example of yeah. So here is one we're able to drill down between here all the particular issue types we have have, and then we can go into the individual stories. Okay. Now, another thing to notice here, we're going to look at risk here in just a minute. Also, yeah, we can roll up our dependencies, again, team by team. Let's take a peek at that. I like the other view that we showed you in our board module a little earlier. And I think that's all I wanted to cover here. Yanni, anything when it comes to reporting, that you'd like to discuss on this? No. I think I think the fact that you can see risks, status, progress, and dependencies in one place, this is what matters. I mean, you wanna get it as a visual as visual as you can and make it on the top level of every all the projects together. At the same time, look at a specific project or which is an adjunct project or a waterfall project. This is where this comes handy. And I think, again, the combination here covers what you need. And, but again, looking at reporting of projects, it's never easy. Just to mention, we we do a lot of work around that. People want different measures, different KPIs, different ways to look at data and analyze their projects. And I think here you can find a pretty quick kind of, configurations that gives you a good grasp of the data. And of course, you know, you have to configure it and and as you go, you can get, additional dashboards and reports from this data. Good. And again, back to, one of the concepts we had is that this reporting module is available every box that you've configured. So you can keep building on these reports and go as granular as you want or look at it holistically across the system. Okay. Shane, I would like to add that, reporting reporting is, quite tricky because you can, of course, you, create huge amounts of reports and drown everyone in a lot of data without giving them value. Our approach usually for reporting is to first make sure that we understand what is most important for managers to what are the questions they are trying to answer. And based on that, we are trying to understand and build for them the correct, gadgets that will give them answers to those questions. So they will get the the the main questions answered, with as as little as possible gadgets. That's, that's the focus here. Absolutely. Thank you, Rand. Okay. So, before we jump over okay. So let's take a step back here. We started and this ties directly into reporting. We started with foundations. And, again, this is where methoda can really help you shine. If you don't have what I would call the minimum effective dose set in your workflows, do I have an assignee? If I'm trying to roll data up, do I have that parent link set? Am I using time tracking or story points? If you don't enforce that in that foundational level, we can roll up bad reports all day. And the thing that's so important about that foundation level before you get to big picture, and, again, this is where methodo really can help you. How comfortable are you with uncertainty? I'm not can you report me 5% off or 10% off? It scares me to death to think that I'm 1% off. I don't want that. You can set that with those foundations. Before you get in the big picture, absolutely, we want you to prioritize. Again, there are several tools out there to help you do that. But, yes, we want to rank those so that when we look in that Gantt chart, those items that we're looking at, we know that we've have those arranged. We're attacking the things that will deliver the best business value possible. So now that that foundation set, now that you have your backlog, your your issues prioritized, now when we look in that resource module, we know that we have accurate information. We know that we can schedule something out that, again, that will set you up for success. Okay. So one of the other areas, kind of the last module to discuss before we jump over into some of our q and a, is, also we have a risk module. Now I have a better view on this. Something would goofy on my view here. But when you install Big Picture, you have there are two custom fields that are automatically installed. Risk consequence, that comprises these columns. Risk probability are these rows from almost none to very high, from trivial to severe. Completely configurable on your end. All you need is your Jira administrator to change these columns. You can put those in there. Now I'm in the home directory, so I can't add it. So let's come down into our solution. Try oh, I've gotta go down one more level. Let's go down into here. Okay. Oh, oh, better view. So we can drag and drop these things. You can set these in Jira. You can set these in big picture. Do you have to have a risk issue type? No. Anything that you want to drag into here that you've identified as a risk is just as simple as adding this. This reminds me of one thing that I failed to mention. So, again, we can add these into the risk module. Before I jump over to there, Yadev, anything to talk about when we talk about when we discuss Yeah. Yeah. I I think yeah. I think that that first of all, the the the risk module of of Big Picture that is being around for a long time is very unique. I mean, if you look for other risk metrics is in the market, there's not too many and they're, I think, less capable. One cool thing you can do is use automations. I mean, you can set the value of consequences and probability through automations. So if you suddenly have a delayed task and it's it has a link or it's part of the critical path, you can automatically put it in a certain risk levels without actually doing it manually. So because of its fields over the issues. So using simple automations, you can set your risks automatically and suddenly you get this, you know, warning signs without looking for them. That's that's something that is relatively easy to do with those cool fields. And, a lot of people want it to be automatic. It's very hard to identify them. Not everybody has the procedures to actually manage risks in the right way. I think as as it gets more automatic, it gets more valuable. Alright. Thank you. Thank you, Yannick. Okay. Last section before and then please, again, in your QA, please enter questions that you might have. We'll have time at the end of this to get to those. I see a few, but would absolutely love to so we can get to those. Alright. Last thing, I try to stay away from configuration too much. It's it's but this one is important. So also in our configuration, we've stated that big picture is bidirectionally synced with, with with with Jira. What does that mean? We have big picture fields, and we have, Jira fields. So I wanna start with this start date and end date, and I have a horror story for you. And, again, this is why Mathilda can really help you on this. So notice that the big picture start date is synchronized with the Jira field start date. Well, it may be that not every team is using they they already have data in there, but they've been using their own particular fields for this. You know? If you're if they've been using advanced road maps, it's, target start and target end. So we'll accommodate for that. This is our general mapping stating this is how we're mapping this bidirectional sync from big picture to Jira. Well, again, this is our general mapping. We also have a custom mapping. And a custom mapping just states well, hold on a second. This project, uses target start and target end or some other methodology or or some other date field. So, again, we try to make this tool robust enough, to accommodate a team no matter their project management methodology and also parts of their Jira configuration. So let me tell you a horror story from one of our customers. And, again, this is where Mathilda really can help you. We had a customer that came to us, and they had created about a hundred thousand issues. And this is what their mapping looked like. Well, about a hundred thousand issues in, somebody went, you know what? That start date, do you see that lowercase d there? I don't like that. We're gonna create a brand new field called start date with an upper case field. So they just changed it without telling anyone. The the the the Jira admin changed it, and then about a 50,000 issues in, they're like, oh, no. We don't know which one was updated last. So you can really get into trouble with here. This is where methoda comes in. This is where when we talk about some of those best practices and governance come in. Yanni, anything on this top? Again, you know, just not explicitly about this, but things that that that method does very well for this. I I think it's important to understand this is a a platform. It it brings a lot of configuration capabilities. And I think one of the first thing is to understand your the way you wanna work within Big Picture. I mean, you have your own methodology, you have your own concepts. The fact that you have this deep configurations mapping to specific projects fields, how this how this app will work for you, I think that's the power of it. And at the same time, you need to be careful. You need to understand what you're doing. You need to to be educated. You need to, configure it correctly. When you know how to do that, it will work according to the the the way you want. Right? And so what we do a lot of time is to help people just to understand their methods, their methodology as a method. Right? And then helping them to move it into the system and suddenly everything fits. You understand the process and you see it in the tool and and everybody, you know, suddenly working with that. That's really, I think, the magic. That's why we need a platform. That's why we need all those configurations. Absolutely. Alright. So let's go back out. And and, again, we wanna pay attention to some of the questions that have come in. But I would like my buddy, one of the questions that came in, and, my colleague, Lukas, will be best to answer this. Lukas, are there differences between the DC and cloud versions? Some minor differences. So I'll just search, the link to our Wikipedia about them. Because, you know, data center, Jira, and Jira Cloud are, like, completely different tools. So the REST API communication between Big Picture and Jira, works in a different way. For example, on data center, you can use the period context to open or to change the workflow of task directly from the Gantt chart. In cloud, you cannot do it. But, you know, the differences are, like, minor, I would say. Would would you say Wooka's were, what, about 99% compatible, do you think? Something like that. Right? 99.9 feature coverage. That's what I've got. Perfect. Thank you. Well, gosh. Okay. So, another thing. And this is, yet again, another webinar where I didn't start here. My God, I can't believe this. Yoniv, I'm gonna bring you in on this one too. This this is an Appfire app. Okay? I don't care what company you're at. Most of the time they don't just go, yeah, just install any app, install any, app you want. You can go to Shane's house of apps and install it. That's never going to be the case at trust.appfire.com. It doesn't matter which app you're talking about of ours. We maintain this list of compliances. You can come there and look and we're SOC two compliant, all of these regardless of our apps. Jani, do you wanna talk about the importance of security? Well, I think everybody's aware of that today, but still, I think look. Working with Upfire, I think that's a big advantage here. You get coverage of all the major, you know, SOC two, other major, security, compliance that you guys already have. For our clients, it's part of the onboarding of every app. Right? They wanna check the app. They wanna understand your data, resiliency, your encryption, the the procedures you work at. Compliance is critical for enterprise customers, and I think one of the benefits for us as a partner is that we can count on you guys for that and bring the data to our customers. They have all this questionnaire. They have all these efforts we do around that, and and Appfire is ready. From customer perspective, if, you know, every app needs to be covered by security. It's not so simple in the Cloud world today. A lot of companies cannot achieve all those, compliance issues, and we see it as a great advantage from customer perspective. Definitely, they're working the and getting all those covered, all those compliance issues, excels that we have to fill in. We have the data, we have the capability. That's that's critical. Alright. Excellent. Thank you, Yaniv. One other aspect I didn't cover. I went ADD on everyone. There are three licenses within Big Picture. You get your main Big Picture license. We discussed, the, we discussed Big Picture enterprise. The other area that I didn't discuss is that we also have big template. That's a third license just to meet a use case where you want the ability to export import or export your data. So, again, we have the ability to export this data with a big template license. That's one other license. Okay. So let's see if there's anything else. Can you display the critical path on a safe art setup, or is this managed by the warning? Lukasz, I believe we can do critical path. Would you mind talking about that one, please? Yes. We do. But, you know, I'm just wondering, what's the use case then to be hide here? So, you know, a critical path is taken from PMBOK. Why would you like to mix that with, scaled agile? But, well, you can do it. So, if you, Shane, if you open that eye drop down icon but first of all, you need to, exit, the what if scenario mode. Right? So from the eye view, if you open critical path, as you can see, you've got it. So Yeah. And I don't have this configured very well, Lukas. You would have a better view on this one for for a great critical path. But absolutely I think it is just to mention, I think it is interesting if you have a safe kind of planning and if all those teams, all those dependencies, if you don't wanna see the path of a PI, you know, the critical path of the PI itself, it's definitely something we hear. And and I think, yeah, as you show, Lukas, it's relatively easy to do. You just have to change the view and click, view critical path. Right? Yep. Okay. So we have about ten minutes left. I don't believe I see any other questions. Janeev, I think we can probably close a little bit early. I don't have anything further, unless there's, one thing any or you, Iran, would like to discuss before we leave. Yeah. Shane, I I would like you to to emphasize something that might be overlooked, maybe, people didn't notice. If you can go to the home home box and go to the go to the, resources view of the home box. I don't I'm not sure that people understood the power the the power of this tool. Right now, we can see the resource utilization, overload, or underload for all the resources from all the programs and the projects in the company in one single place. This is, this is something very, very powerful. As you can see, the the the response time is very good. The performance is very good. It's a lot of data coming from bottom up for many, many projects and, tasks and and, everything shown in one place. So this is one thing. And another thing that I would like to emphasize is that maybe from all this presentation, maybe, all the participants, they they see all those configuration options and they and they and they, maybe get lost with all the options. But the main thing that we need to want to emphasize is that methodology methodology is senior. First, the methodology, the the the method, how you want to plan and track your projects, then, implementation in the tool. So the the good thing about Big Picture is that it has so much configuration options that you can it can adapt to whatever method that the company wants to use. That is the most important thing. Excellent. Thank you, Rana. Alright. Yeah. Shane, I think we covered, you know, we covered a lot of stuff today. Yeah. We searched those games, PIs, plans, risks in in just, a little bit of that over fifty minutes. That's, that's a lot. Good. Yep. Yes, sir. So, you know, as we're closing up here, just, for all of you that are interested in the tool, I encourage you to to reach out to to Mathoda, to reach out and ask questions. As Mathoda is one of our top partners, they'll bring us in, if if they need us. They're already sharp. But if they need us, they'll bring us in, and and we're happy to work with you, again, especially with that foundational part is getting started. But, again, we, we're we're happy to be working with them and just, I really appreciate all of your time today. Appreciate your, the the questions that you've had in, in the q and a. We'll be sending those out at the end of all of this, and that's good closing. Ron, Ran, Yaniv. Anything else before we wrap up? Oh, no. Just thank you, Shane, for this. It was really very interesting as usual. Alright, everybody. Thank you so much. I really appreciate your time today and, have a great rest of your day. See now.