Name: [Live Demo] All-in-one Project Management with BigPicture
Uploaded: 2025-08-27T14:16:26.045Z
Duration: 45 min 56 s
Description: [Live Demo] All-in-one Project Management with BigPicture

Transcript for "[Live Demo] All-in-one Project Management with BigPicture": Excellent. Hello, everyone. My name is James Barnett, and I'm a senior solutions adviser at Appfire. And today, we're gonna be covering big picture. In addition, we're also gonna look at big picture enterprise. It's a separate license. We'll go through that. Now for a little bit of housekeeping, joining us today is one of our better partners, iTmethods and, Ivan Lima. Ivan, please introduce yourself. Yeah. Absolutely. Hi, everyone. I'm Ivan Lima, a Lawson consulting team lead here at iTmethods. And I I run our a Lawson practice helping, you know, enterprise customers get the most out of their a Lawson stack with solutions and expert guidance across all North America and beyond. And, yeah, like, looking forward to today's conversation. Excellent. Thank you. Also with us, Łukasz Romaniuk, a colleague of mine, also another solutions adviser. Please introduce yourself, Łukasz. Yeah. Hello, everyone. My name is Łukasz. And as Shane mentioned, I'm your solution adviser, in Empire. And today, I'm going to answer any questions that you can ask, in the chat. Excellent. Thank you, Now that also brings us to another element of housekeeping. You notice that you have a chat and a q and a. Please enter all your questions in the q and a. We'll get to them as the, webinar progresses. Okay. Housekeeping over with. Let's get started. So what we're looking at here is an app fire solution, a big picture, and, it's our portfolio management solution. Now we do we do need a little, a little bit about this before we dive into the other areas. So when we look at this, when you install big picture, for starters, this is the Atlassian cloud environment. We also can be installed on DC as well. So when you install this app, you are granted a one and only one root folder. Okay. So as we look at this, you'll notice that we have, what we call boxes associated to box types. Well, what does that mean? Big picture loves your teams exactly as they are. You don't have to change your workflows. You don't have to modify anything to connect big picture and Jira together. So as we look at these box tops, let let's dive into this just for a little bit. So what project management methodology is that project in Jira running against? So agile, you're just running sprints, nothing more. Scaled agile. So we have program planning increments. We have teams running synchronous sprint schedules. Hybrid. You're running waterfall, but we've broken it into state. You've broken it into stages. You have planning and execution and delivery. Portfolio. Portfolio here means group. I wanna group like work together. Maybe I wanna group business units or all teams that run story points or all teams run time tracking. However you want to group these naturally together. And the last one worth mentioning is classic project, waterfall. So regardless of what you're running, big picture will accompany that. Now once you've configured a box, and we're gonna try to stay out of too much configuration today, But couple of things worth pointing out here is that so we'll select a box, and we'll go into the configuration, and we'll look at the scope definition. Now what that means is that now that we've configured a box, what's in that box? So notice that we can select Jira project or projects. Notice that if you go on to select that, you can select particular scrum or Kanban boards, or you can create your own cool JQL filter. However you wanna populate this box, Big Picture will handle that. Now one other area about this piece of of, configuration, security. So big picture acknowledges all Jira permissions. If you cannot do it in in Jira, you cannot do it in big picture. However, we do go a step further because this is the beginnings of governance. So who can configure this box? We we you can't allow everybody in here. Right? So you need that process of identifying again who's responsible for it. Again, that that talks a little bit about governance. Ivan, would you want to jump in on that topic a little bit, please? Yeah. Yeah. For sure. Like, looking at the basics, what what I like about having that flexibility, like you mentioned, all the boxes, types, the scope, and permissions. Like, it's really about understanding all the building blocks and how they're gonna fit into the way that teams actually work. So, so the deeper question then becomes, like, how does your organization actually structure itself? And having those different types, you know, hybrid and, you you know, even more traditional approach and the flexibility to scope them to projects in in JQL filters. So that's a that's a blessing only when you pair with the actual rules and and the governance that you're gonna put in place, which touches on the permission component there. So that's how we're gonna build trust in the system. Like, you wanna give people, you know, all the freedom to to work, but also draw the boundaries so so the system actually doesn't collapse under its own weight. Right? Oh, excellent. Thank you, Ivan. And we're gonna come back to governance a few times in this topic. Okay. So let's go back to our original main area. Now so we've covered boxes and box types. One other element here that we're gonna cover are modules. Now we're gonna get into every one of these modules today. And, again, with each of these boxes, these modules are available. So it was an easy example. If you want reporting against this box, you have it. If you want reporting against a group of projects, you'll have it. If you want reporting against everything, you will have that as well. Okay. So boxes, box types, and modules. That's the basics. Okay? So big picture does one does a few things very well. And the first thing that we're gonna talk about is resource management. Now doesn't make sense to start here, but this is a great place. We're gonna look at our global teams. And the concept here is that, yes, we can integrate naturally with the Jira team. But the use case here is that we want to define a team because it's common that someone, a resource, is available across multiple teams. And the first area about resource management that we wanna capture that is right here. We want to be able to state, okay. Well, they're 50% on this team, 50% on that team, or 25% across four teams. But that k. So that's element number one. Element number two, which is the main area, is we will look at our resource configuration. So what are we looking at? This is a cross reference map to provide metadata about Jira assignees. Alright. What is that metadata? Workload plan. Are you working eight hours a day, five days a week? Are you part time? Are you off every Monday, which would be awesome? Whatever that schedule is, we want to capture that. The next thing is a holiday plan. It's a very common use case that your company is working across multiple countries. So we want to establish a holiday plan per country because we need to know when that resource is not available. The last area is skills. There are three listed here. List as many as you want. And these are not one to one. Multiple skills can be associated to a single individual. So to come back to this, we configure the resources and get that metadata. And when the assignee field is set in Jira, now we're gonna know more information. Well, where that all comes together let me go back to overview. Expansion. I'm sorry. Let's try this again. Expansion. And then we'll come into resources. Alright. Where that comes together is we'll put this out to a half year, is here. So what are we looking at? So now right now, we're looking at individual's capacity, and it's in hours. Well, you can toggle that between hours and story points depending on what your team is using. And and in this example here, Agnes has been assigned as thirty six hours of total capacity, has been assigned zero. That's thirty six hours thirty six hours left. Alright. Now these are automatically color coded for you. At 75%, they turn yellow. 100% or over, they turn red. You have complete autonomy over that color coding scheme. However you would like to color code that again. Now the next thing to notice under here is that underneath Agnes, we see the Jira issues assigned. For those to appear in this list, we do need a little more information. We need to know a beginning and an end date of that issue, and we need time tracking or story points, either one. Just as long as we have one in here, that'll suffice. And, again, here's a great example of somebody that has gone overcapacity. Now previously, we talked about teams. Well, it's one thing to state is the individual overcapacity is that team overcapacity, and that's why we wanted to capture, okay, use case. Somebody's 50% available on this thing, 50% on that one. K? So is that team overcapacity? And then last, we can look at skills. Now I don't have a great example here, but the purpose is that we can add skills to that individual Jira issue, and you can come into here and go, I need a developer. Is there a developer that can handle this capacity for this task? Now before I hand it over to Ivan to discuss a little bit, put one thing in the back of your mind. Notice these light gray columns. They're gonna represent a Saturday and a Sunday, or or, if that if that particular resource is on a PTO, it will have a horizontal gray bar to designate that resource is not available. And we're gonna discuss that in a minute. Ivan, I wanna turn this over to you. Anything on the resources module? Yeah. Sure. One of the biggest values actually, like, the solution like this, it it brings that visit like, visibility into how people are actually allocated. Because if you don't know, who is doing what, you cannot know how, you know, who is actually doing too much or too little. Right? So and, to your point, you know, if you wanna get that right, so we have to have the reliable data in place, like all the assignees, assignments, availability, and so on. So and once that's in place, so that's when we can start kinda layering in things like work patterns, time offs, excuse. Right? And it's not not just kinda tracking, hours or story points, but also matching the right people and and the right work that you have so people can actually focus on what it's meaningful, in terms of work and not just kind of firefighting all the time. So Excellent. Thank you, Ivan. Okay. So we have a lot of great columns representing Saturday and Sunday. We'll get back to that. Now we're gonna jump over to the Gantt module. God. The resources module and the Gantt module play very well together. So let's jump over to here, if it'll ever pull up. Okay. So the first thing that again, we discussed the resources module and that Gantt module play well together. So when you select this resources module, we can now bring up our overall resources, and that is in story points. So let's take that effort. My aunt's in original net. I could've sworn that was Łukasz different. Okay. So what we can Łukasz at here with the resources module is that we can already tell that this plan cannot be executed against. Okay? So one of the first things about the gap module again is that you can these two play well together. Now I wanna go down a level. We'll go into legal info. Don't and let's come down into here. Alright. So this is more of what you would think of when you think of a classical Gantt module. So first thing you want to designate is this. Those light gray columns are back designating when a resource is not available. So in big picture, if you attempt to schedule an issue when a resource is not available, I'm gonna drop it right there in the middle of that gray line, Notice big picture won't allow. And, again, if that resource is on PTO, it won't allow you to schedule that issue. K. Another element about here is that we wanna pay attention to these modes here. So the picture comes with a couple of modes. Auto bottom up. You have data that's structured, and, you know, we have stories that feed into epics and feed into, you know, a higher level initiative or what have you. Auto bottom upstates that I want the children to drive the beginning and end dates of that particular higher level issue. Then we can also go auto bottom up. We can also go auto top down. We have a go to market date. So classic use case. I have a Jira epic broken down into stories, and we know that we can it's a go to market that we can't miss it. So what happens here is that Big Picture will not allow you to schedule outside those known parameters. Alright. The other thing that we see here on the screen is a baseline. So you can see auto visually that this issue has slipped into the future. There are a lot of elements about this module we're not going to get into. We're just gonna cover the absolute base. Okay. So let's see if there's anything else in here that I wanted to discuss. Okay. The last thing area to discuss is that I don't know if any of you have ever used advanced road maps, but just like advanced road maps, we have a scenario mode. Remember, big picture is bidirectionally synced. So it may be that as you're looking at your resources panel that you think, we're not gonna be able to execute this. So as big picture is bidirectionally synced, let's still have that traffic flowing back and forth as we're setting those beginning and end dates. We can come into a scenario mode where you can then set your schedule, as needed. And when you're done, merge changes to live. It just means set the beginning and end date. Okay. Alright. Ivan, anything that I've that I glossed over here on the Gantt chart, anything you'd like to comment on? Yeah. I mean, not much. I think, like, Ganttributes, to me, it's one of the most, powerful ways that it can bring all the schedule dependency capacity altogether, in a single place, and that gives you really the ability really to identify all the potential conflicts, right, and see how the work it's gonna fit over time, which is, by the way, the most unforgiving resource. Right? So having that, you know, view that it can it it's more about seeing the cause and effect across time. And I wanna just call out the scenario piece. I think that's, especially valuable because you can really explore, like, different options and, explore alternate futures. And, without having having to pay the price of mistakes in the present, so that's a real real superpower right there. Excellent. Thank you, Ivan. Okay. Before I jump to the next module, I remembered something that we wanted to point out. I'll jump back over to the resources module. Alright. For starters, one of the first things the big picture can do for you with your resources, look at all of these unassigned issues. That's a problem. So and this goes back to governance where iTMethods can come in and help you. If you're not enforcing in your workflows that minimum I would call it the minimum effective dose. If you're not enforcing that, an issue has to have an assignee. If you have structured data, story to Jira epic to initiative, If you're not enforcing a parent link, we can render this any tool obsolete. And this is where iTMethods can come in on that governance method of that governance layer to help you get started. Ivan, anything on that? Yeah. I mean, like, that's a that's a very important point. Like, the tool is just a mirror, you know, and then if your data is law pure, there's something missing there, the reflection will be, you know, the same way, like, successful adoption and approach for any tool that's really comes from the discipline and and the governance, like you said, that we're gonna put around it. So and then, of course, includes setting, you know, clear standards, assignees, very basic in how, you know, work gets created. So, so you can actually rely on the data that we're working on. So the data is accurate and consistent over time. Alright. Thank you, Adam. Okay. So I'm gonna jump over to another module. Now this is the data center version. I just happen to have good data here. Okay. So in this example, we're looking at scaled agile. This is just an example. This works with with all the other types, all the other project management methodology styles as well. But the last thing so we've covered resource management. We've looked at the Gantt style. Now we want, for starters, look at dependencies. Now we want to track dependencies between a single team, or we can track dependencies across teams. Ivan, from a governance standpoint, if you saw this, what would you immediately think? Yeah. I know. Sometimes it's, it it gets kinda scary. But, like like, visual queues, it's extremely especially for dependencies. Right? Because, so that's one of those things that can kinda make or or break a plan. So that's for sure. So from my experience in helping enterprise customers over the past number of years, I can tell, like, most porch follows, they're gonna break not on strategy, but on the dependency. So, like, one team blocks another, one assumption unravels, and all of a sudden the whole plan collapse. So having that zero queue, that's extremely important because it's really about exposing the risk early. While it's just too cheap, you can actually do something about it. So Excellent. Thank you, Alex. Alright. Now so big picture does a little more. So notice that we color code these things for you. Green is good. Orange g here is there's a possible issue. Red, you absolutely misconfigured it. The the dates are backwards. Now to help with that, let me bring this off the screen. You can select the info bar, come over to warnings, and it will tell you why we say why Big Picture has flagged this thing to be inaccurate. Now we do a little more here as well. So it's one thing to have resource management. It's another thing entirely to do sprint capacity management. So from this board view, notice that we can bring up our backlog. You'll have your capacity set. Big picture's bidirectionally synced. You can drag these items in between the sprints, and it will affect and reflect in be in Jira. And, also, we can drag items straight out of this backlog into here. So, into in, into your sprint planning. Okay. Ivan, anything on the sprint planning portion? Yeah. I mean, like, I think that's, very straightforward. What I what I like about this, it's being able to actually set the capacity and see the impact of adding work in in real time. So that helps, you know, avoid that overcommitment trap. Right? So, and and that when it comes to capacity planning, like, I like to think it's kinda the art of honesty. Like, you wanna match the ambition to reality, and when you have that tool that, you know, matches that, you know, well so that, for sure, it's gonna help you, you know, really make sure that the teams are set up for a realistic delivery. Like, the planets, at the end of the day, is just kinda only useful if it's really achievable or not on there. So Excellent. Thank you, Adam. Okay. So we're gonna kill this. We're gonna come back to Jira. I'm back to big picture. Okay. So so far, we have covered the absolute basics of big picture. Flexible enough. You don't have to adjust your workflows, resources, Gantt, and, sprint planning slash dependency. So Big Picture comes in to basic licenses. You get Big Picture. We also have an add on license called Big Picture Enterprise, which, expands upon, what Big Picture can do. Now one of the first things before we even look into it is that if you want to add PTO, you know, a vacation to a particular resource, Big Picture provides a few manual methods on how you wanna do that. But Big Picture Enterprise, if you happen to be using Workday, we have an active integration with Workday to be able to pull in all of that vacation and set that for you. Okay. So with Big Picture Enterprise, what happens is that anything that says new here, these are the additional modules that you get with Big Picture Enterprise, and we'll pick them off from the bottom to the top. So financials. Now in this example, what I have is a portfolio. Remember, it just means group. And we've grouped a bunch of initiatives that we want to accomplish. So this costing here is driven upon two things. We can have a blended rate per box, or we can have a blended rate per team. We'll go into a little more detail about that a little bit. And in addition, it's story points or time tracking, whichever one you will drive this report. Now, of course, we can look at that report by these particular toggles, or you can give it a custom date range that you want to view it. As we look in the cost variant section, now notice that we can set a baseline. And that baseline, again, we you can take up to 15 of these snapshots, and we'll look at where we are as opposed to what we originally forecasted as an original. Alright. Now little bit more about the financial section. As we go into the, configuration of it, notice for starters, one of the things that differentiates setting your baseline against the team is this. Just because your team's blended rate last year was x, doesn't mean this year it's not y. So we can keep that historical nature of your teams. Set big picture. You can set it to whatever currency we we have all currencies in here to set this against. Back to baselines, again, you can have them taken automatically. You can take them ad hoc, however you wanna create that snapshot. And last thing you mean to your custom expenses. This module was released in April, and it is constantly being modified. So what you didn't see was things like CapEx and OpEx. That's already in the back backlog to be released. And one of the things that was introduced are custom expenses. One time one time, you know, license cost and what have you. Okay. Ivan, anything on that finance financial module you'd like to discuss? Yeah. I think, like, a real value here is is connecting, like, the work actually being done to the, to the business impact because because money, you know, is the lens of truth. Right? So having a high level view on cost budget. So that's for sure it's gonna give leaders all the insight to make better decisions more quickly while still being able to really drill down into, you know, all the work items and details, if that would be necessary. Like, what just wanna call out one point here. It's it's about permissions because that play a huge role because you don't wanna open all the sensitive information like rates, for example, for everyone in the system. So you wanna make sure the right people, they're gonna see the right numbers. So then again, back to, you know, to the governance point. So that's extremely important the way that we're gonna set this up. And, it's not about control and secrecy, but it's really about kinda stewardship and accountability and make sure, you know, that trust you put that trust in the system that you were running there. So Oh, excellent. Thank you, Ivan. Okay. So that's our financials module. Now we're gonna jump over to priorities. I find this to be a I for me, this is a module that out of it's not highly it's not as highly used. I think it should be. So what we have with, financials is that well, we're looking at key results here. We'll get into that. So what we're looking at with financials is notice that usually we would see, see if I can get that out of there. We'll come back. Usually, what we would want in our priorities module I've seen it as a common use case to use GRAS. Right? And so what you don't have to be agile. Let's imagine you're planning out work for a given business quarter. Right? You throw all your Jira epics in here, and we provide an easy, clickable interface that will that will set a particular score to this module. Now this is an ICE formula. What is that? Impact, confidence, and ease. You don't have to use this. We come into the configuration of priorities. Big picture comes preconfigured with from quick wins up to ice. You'll notice Wizchimp is there, but you can create your own formula. Now I don't know who created this formula, but that's a mathematical nightmare if you ask me. We'll accompany whatever you need in here, whatever formula that you want to derive, or, you know, a, a cost benefit for this. Now as a concept, what I love about this module is, again, let's go back to the the back to what we discussed earlier. So you have a given business quarter, and you have all your Jira epics, and you've applied a mathematical score to them. And one month then to that business quarter, we rank these from top to bottom, and you see the Jira epic that's ranked dead last, having work accomplished against it. That's a problem. And that's a governance problem if you ask me. Ivan, anything on that? Yeah. And that's actually a good point. It could be a problem, but it could've might as well be perhaps a decision, as long as it's it's, it's a reason. Right? So, just one step back, I think, like, in terms of prioritization in general, like, that that actually works best when there's a clear, consistent way that it can actually score. So having a model like this, that would, for sure, that would help a lot. Whether it's through the formal that I was just sharing there or any any other approach that would make sense, but without having a system. So everything becomes like urgent. And then urgency, it's gonna fully destroy a team's focus. That's something that we don't want that to happen. And, so the real challenge is making sure that those criteria, whatever the criteria that you're using, so they're gonna apply consistently. Like, if priorities change daily, so they're not priorities. So I guess something else. Right? And that's that's where the power comes from because then you can empower teams to say, well, perhaps not this, not now because they have a clear picture of what the priorities. Right? So they have the confidence to work on that and and say no sometimes. And, back to your point, Shane, there, yeah. So there there might be some kinda low hanging fruits down in the, you know, priority list that, you know, that makes sense just to tackle those because we just wanna get them out of the way. They're just kinda quick and easy to have these queue sets available to work on. But as long as you have that system and those things actually make sense and can reason over. Excellent. Thank you, Adam. Okay. And then what I goofed up on on this module is I was over in the goals portion. We're about to discuss OKRs, but you can with the prioritization module, we can look at your individual task, or we can also rank your OKRs, which we're gonna take a peek at. Okay. Now let's jump over to our OKRs module. So objectives and key results. Alright. So what are we looking at here? We'll come up, and we have a top level portfolio level objective broken down into a team, broken down into a key result. Yeah. We went into the configuration. You're not limited to these. Again, for a big picture, very flexible. We can divide that. Both oh, I'm sorry. And as we look in this key result, this is where you link it to Jira issues. Okay? These the I mean, these key results all live in this module. You're not modifying your Jira issues. You're just linking it to it. Okay. Now, Ivan, I'm about to throw something at you. I want you to correct me on my reasoning here. Here's what makes sense to me with OKRs because I'm analytical. It would make sense that okay. Step one. We've talked to iTmethods. We've normalized that or that base layer because we know that the assignee is gonna be set and apparently accept. Step two, we come in and we load maybe we go to the prioritization model, maybe not. Step two, we load it in the big picture. We check our resources. We ensure everything's ready. And then finally, now we're ready for OKRs. I bet there's another approach on that one. I mean, I'm sure that I'm just that this is just horse blinders that I have on. Yeah. Do you what comments do you have on that one? Yeah. Like, so there are, of course, there are different approaches. And, again, from from my experience, healthiest organizations, they they are gonna blend, you know, like, whether it's top down, it's bottom up, they're gonna blend both, quite well. And it it's extremely important. So when you think at top down, because that brings, you know, directions. So leadership, it's gonna define all the strategic objectives. They're gonna set the big picture priorities, and that's, you know, that's good. That's extremely important. But also bottom up, in that sense, it's gonna, you know, kinda bring all the engagements and the buying from teams. Right? So teams, they're gonna contribute to their, you know, perspective on how best to achieve those goals. So they know better, you know, how to be more efficient and the best way to achieve those goals. So so I think that's kinda blend that that that works, well. And and what I like about this view in particular that you can clearly create a connection between all that strategic objectives that you have to the work happening on the ground. So we're linking them to to the right work items in Jira. So that visibility into progress. So that makes it easier, you know, if you wanna swap things like the you know, if it's on track or off track, for example. Excellent. Thank you, sir. Alright. So let's gonna stay in this module for a little longer. Now, again, as we look at our key results linked to the issues, this module, back to governance where iTmethods can help you, this module also has its own set of permissions. We you you generally can run meetings out of this particular module with the, you know, the particular resources that you've identified, limit who can update these things. And why we would want to do that is here the key result here. Notice there are a lot of fields that we didn't cover. Lot of columns with weights and, you know, proposed and start and end dates and what have you. When it comes time to update this thing, notice we can go on track, at risk, off track. Ivan, should we ever see that thing go from on track to off track, or is something going horribly wrong for that to happen? Well, it's it's not rare when you see that. So that's the danger of the, sort of the watermelon effect. Right? So it's, it's just kinda green outside, but in in reality, it's it's being red inside. So and, kind of numbers look fine until reality actually catches up there. And then I I like to think about it, you know, very simply an old solution. It's, you know, just honest in measurements. You're gonna ask, well, is that really green really green? So just kinda be honest and do that measurement, you know, in a, in a more transparent way. And and, and another point, of course, it's the, regular course correction process that you have in place. Right? So whether it's a daily meeting, it's a weekly meeting, whatever the process that it's gonna make more sense for your organization. So that regular course correction, cadence, that's extremely important. And that's what, you're gonna, you know, save you from, you know, going from, you know, green to red right away. Right? Excellent. Okay. So one more item about governance. As long as you've got your have your Jira notification set up correctly, you could technically go, we're off track. I could at mention Ivan and go, oh, no. There's a problem. And Jira will automatically send that notification email for you. Okay? Now a little more about this, particular module. Let me go back to the concept here. You don't have to be agile to use this module. We have you have something you want to accomplish and you've given it a time frame. K? So let's look at a little bit of the settings when it comes to this. So periods, what is the time box in which you want to accomplish this? OKR types. Notice you can create your own cool OKR types. And then also, permissions. Yeah. Yeah. You definitely wanna talk about governance and permissions and who can set this up. Let's go back to our OKR. Another thing to look at here is, yes, provide a report against all of your OKRs that you're tracking, which is really nice. And one last item, we'll come back to the overview. And, there was one more thing I wanna discuss in here, and it is leaving me. I'll come back to it if we need to. Okay. So OKRs. Now we're gonna go into our last module that we wanna cover today, which is the risk management module. With this module, we create a set of risk registers. We'll select one. Our financial risk, and here is here are our risk. Now starters, let's take a look at the configuration on this, and we'll go into our settings. And for starters, how do you wanna calculate this risk? Again, completely up to you as you wanna do this. And we also want to define that risk metrics. Now notice again, all of this is completely up to you as to how you wanna define it, and we get into our risk metrics. And again, once again, you're able to get down into the mathematics of what happens. Okay. So also in our general settings, we have financial, notice that we can select the issue types that we wanna associate that risk, and we bring up a a a new link called is mitigated by. So you've identified a risk. Well, you can create an issue to mitigate that risk. Alright? So that will come naturally with this module. We select cancel, and now we wanna go into our report. Okay. And here is that risk metrics that you discovered. The first thing about this risk metrics is that easily selectable to bring it right up into Jira, and we provide a report against all of your risk. Okay. Let's come back to the risk register. Ivan, tell us about risk because I know it's a big thing when you do a portfolio management. Yeah. I know. That's definitely a big thing. And, and then, like most most projects and and, you know, in in organizations, they have some kind of, you know, risk management process. And so they're they're gonna write, you know, risks down at the beginning of a project. And, typically, as you get busy, you know, project ramps up, those, risks, they often they get forgotten or are not kinda monitored properly. And really the key, it's it's kinda tracking them throughout the entire life cycle. So it's the cadence that you're gonna put in place for that. And, as we're sharing here, so having a structured way that, you can surface risks continuously and, you know, having the ability to categorize a score and and visualize. So that for sure for sure, it's gonna make easier, right, if, you know, to to see where the attention is actually needed. And what I like that you mentioned there, so you have that, you know, native linking that you can put in place. So, you know, when you're working on the issue, so that is gonna be right in your face. So it's more visible, therefore, you know, more accessible, so that information and that becomes, of course, easier that you have to address, you you know, risks before they they actually escalate. So it's too you have choice to to make. As for, you know, risk management standpoint, having choices, it's extremely powerful. You can, you know, whether mitigate or eliminate fully. Right? Excellent. Thank you, Ivan. Alright. So let's come back out and let's do a refresher real quick. So big picture. We have boxes. We have box tops. You can populate that box any way desired. We have modules that you're selecting. Right? So we can configure teams, people across multiple teams. You can look in the resources panel of that resources configuration to garner that metadata so that we can actually look holistically at your resources, to find if they're over or under capacity. Gantt style views to be able to set your schedule, that plays well with the resources module. Then we jump over to the scope module, and we reviewed, dependency tracking. Now as we've gone through here, one of the areas that we're missing, and this is a little bit of a date dive, but just a little bit of one, Is again, this is where I as we've talked, governance is huge. This is where iTMethods can help you. Now we've stated that Big Picture is bidirectionally synced with, with big picture. Well, there are 12 big picture fields that we can associate to a given project, right, or to a give you know, to Jira. Now there's two ways to define these. One is the general map. Right? Just this is applicable to everyone unless they're in custom mapping. Again, big picture tries to be flexible. Advanced road maps is a great example. If you're using advanced road map, you're not using start date and end date. You're using target start and target end. So however your project is mapping that data, Big Picture will accompany that. Now has heard me tell this story a 100 times, but I still think it's applicable, is this. Let me tell you a fun story that iTmethods would never allow you to do. We had a Big Picture customer come in, and they had about 300,000 issues. And they had configured it again start date and end date for the general mapping. They had nothing in custom mapping. This applied to the entire instance. And about a 150,000 issues in, somebody looked at this start date and end date and said, like, do you see that lowercase d there? That doesn't look very good. So they created two new custom fields, start date and end date, with an uppercase d, remapped the entire instance, and then they had no idea which one they had updated last. This goes back to governance and setting this thing up correctly the first time, which is where iTmethods will really help you out. Ivan, again, Ivan, that's just an example, but anything more about this governance that we wanna nail that first time. Yeah. Well, that's, that's, I don't know if it's a fun story, to be honest. No. It's it was fun for them. Yeah. But, like those stories, it kinda sounds like, oh, we we thought it was just kinda small change, and all of a sudden, it's, it's caused a a kinda massive impact in the system. And I feel like stories like that one, it's a kinda good reminder that, you know, governance isn't just kinda nice to have thing, but it's it's extremely critical. Right? And, I like to think that governance, it's that, you know, it's boring until that saves you fully. Right? Because, yeah, like, all all that stuff like naming fields and then, you know, configure all, you know, permissions and schemes and setting rules and define change controls. Like, all of these are, sort of, unglamorous work, but that it's going to fully protect the trust that you have in the system. So without without it, all the data and configurations so that becomes a lot, you know, a lot of noise. It can it can be a lot of noise. So, like, a well intended change like this one, this example chain that you brought up could've caused, like, unintended and massive, you know, problem in the system. So so that's why it's important and, you know, to have full control over all the changes that you were making there. Excellent. Thank you. Okay. So that's what we had to talk about today. Did anything come in, Łukasz? Oh, and Łukasz, is there anything that I've missed? Is there anything that came in over q and a that you think we should, reach out and and discuss? And, Łukasz, I can't hear you, but there you go. Well, maybe the questions I'm currently trying to answer, Peter, like, those big picture use Jira native fork hierarchy. What is Jira native fork hierarchy? In big picture, it is like you desire. So there is nothing in the world like a Jira native fork hierarchy, because if you've got big picture, you can create, like, 10 levels above the epic. And, that's that's pretty much one of the killer features of this application. But, when it comes to creating, OKRs, yes. If you've got Big Picture Enterprise, you can, in Big Picture, create objectives and key results, and then fire them as a part of work break of structure. Excellent. Okay. Now one of the things that, also that was failed to mention is back to and, Wilcox, help me out on this one. Back to our priorities module. I do believe that once you apply this mathematical score to a given epic, that the Gantt chart will reflect those numbers. Correct? We can put them is that tell me if I'm phrasing that right. That's correct. You cannot, priority score as a column to the Gantt chart. So then you will see, the score that you've, well, calculated in priorities in the Gantt chart. Oh, excellent. And then also, with the Gantt chart, we can load your OKRs as well, Albert. Okay. Alright. So that is an overview of Big Picture plus the additional Big Picture enterprise license. So as we wrap up today, Ivan, last words from you. Yeah. I mean, not much. I just, well, actually, I do. I just wanna thank you, Shane and team, and, you know, thanks everyone for for joining us today. Like, it's been honestly a great discussion. Learned something a little something today too. So and I, you know, I just hope that's given you, like, some useful, you know, ideas to take back. And, if you have any follow-up questions, wanna continue the conversation, I'm just happy to connect. Thank you, Ivan. Okay. So thank everyone of you for attending. Really appreciate it. Hope you've learned a little bit more about big picture today. Remember, reach out to iTmethods. They're they're standing by and willing to assist. Łukasz, anything from you for as we wrap up? Maybe the fact that if you've got enterprise, you can connect, your Jira clouds, to external Jira cloud. So That's a good point. Alright. I love it. Well, thank all of you. Really appreciate your time, and, have a great rest of your day. Alright.