Video: [Live Demo] All-in-one Project Management with BigPicture | Duration: 2740s | Summary: [Live Demo] All-in-one Project Management with BigPicture | Chapters: Introduction and Housekeeping (0.24s), Jira Big Picture (115.56s), Configuration and Security (232.37s), Resource Management Foundations (375.75998s), Resource Management Tools (485.8s), Resource Management Overview (844.26s), Resource Management Planning (1089.165s), Tracking Project Dependencies (1310.345s), OKR Implementation Strategy (1437.85s), Risk Management Features (1799.9501s), Governance and Best Practices (2033.835s), Planning and Differentiation (2218.9202s), Module Configuration Overview (2479.7s), Closing Thoughts (2641.3699s)
Transcript for "[Live Demo] All-in-one Project Management with BigPicture":
Three. Hello. Hello, everyone. My name is Shane Garnett, and I'm a senior solutions adviser with Appfire. And today, we're gonna be reviewing our, big pic our, portfolio management solution, big picture. Now got a little bit of housekeeping. For starters, joining us, from ISOS is, Daniella Paula. Daniella, could you, please introduce yourself? Sure. Hi. Good morning, everybody. I'm Danielle Paulo. I'm from ISOS Technology. I'm a principal consultant with them. We really work on making sure that you're getting the outcomes you want to out of the tools specifically within the Atlassian suite, especially things like Appfire that, integrate with it. We focus on the people, the processes, and the tools to make sure that you are getting that value that you expect out of those tools. Love it. Thank you very much. Also with us, from from my team is Lukas Romaniuk. Lukas is gonna be into the, answering your questions in chat and q and a. And, by the way, that reminds me another we have a little bit more about housekeeping too. So, also, as you have questions, enter them into the QA section. We'll get to them as the demo goes. If we don't, we'll get to you afterwards. Also, notice that you're looking at Appfire Trust Center. So before we talk about any app, regardless of what you're gonna install in your system, generally, InfoSec is going to need to be involved. So regardless of any app that you have from Appfire, you'll notice we have our list of a real time list of compliances. The last portion of, housekeeping is this. As we look at big picture today, we're also gonna be looking at an add on big picture enterprise. It's going to introduce a a few new modules we're gonna be releasing in April. So as a heads up, that's what we got. Okay. So, let's start. So, what we're looking at here is that this is the Atlassian Jira cloud environment. We have Big Picture as an add on installed into it. And, you know, the first thing that we notice here is that you get a home directory. The home directory serves as a summation of of everything that you're going to configure in there. And then also, we're we're gonna have a list of modules. Now before we kind of dig into this, one concept is this, is that in big picture, on the left hand side here, you'll see that we have box types. We'll show you a little bit of the configuration of that. But these box types are meant to meet your team. We're we're agnostic on our project management methodology style. So as we look at some of these boxes, notice that agile, you're running sprints. Scaled agile, you know, you're running a true scaled agile. Hybrid, Hybrid to me means that it's waterfall, but it's, you know, been broken down into some individual buckets. Portfolio. Portfolio really means group here. We we want to be able to sum up, you know, a series of projects into an overall container. And then the other one that to really pay attention is classic project, waterfall. Danielle, I believe you had something on this. Yeah. Thanks so much. So what I really love about this tool and the ability to have those different types in here is that this is really meant to be an enterprise tool. So a lot of organizations that we work with, they're not looking at implementing this or getting the value out of it specifically with, like, one group of folks. Right? You have possibly different verticals that might have different ways of working. And so this really allows you to have a format that allows you to manage that work, again, with those different types across the organization and still have it roll up into a format that is useful to see what's going going on across the business. Excellent. Thank you, Daniel. Okay. So I'm gonna try to stay out of configuration too much. It just bores people to death, but we do wanna talk about one thing. So we created a box. Well, what's in that box? Let's kinda discuss that. So when we highlight any of these, remember that we have our module selectors. We're gonna go into our configuration, tasks, code definition. Okay. You can put project or projects, scrum and or kanban boards, or you can create your own cool JQL filter. However you want to populate this box, we try to, again, be as agnostic as possible to allow you to, you know, to to do that to to meet your needs. One other area about configuration we want to discuss, security. 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. However, once you have configured a box, we can't have every Tom, Dick, and Harry in here pushing buttons. So we introduce security for this, but security is another thing. That's governance. And this is where ISOS can really help you, out as you set up this product. Danielle, things on this? Yeah. Thank you. So there are some things regarding, like, security of who you wanna have access to these different, box types or, you know, who has access within it. There's also governance around how you use the tool, and do you really have a strategic understanding or structure that you're looking to implement, like the architecture behind it. Right? Because you wanna make sure that as you're making changes within the system, it's really driving towards the goals that you're trying to get out of it. We have had a lot of organizations that we do work with that sometimes they don't have great governance around the systems, like whether that's in Jira or even within Big Picture. And as requests are being made to add different fields or reconfigure things, you have to understand what the downstream effects of that are across the business. So making sure that you have that governance in place to not only know from a security perspective of who has access to it, but also what are the goals behind using these tools and making sure that you keep that in mind as you're configuring it, holistically. And, again, that comes from not only the IT admins, but will also come from the business partners that you're working with who are using this tool day in and day out. Excellent. Thank you, Danielle. Now before we really dive into this, let let's back up for just a little bit. Foundational levels. We're going to start looking at resource management. And let me give you an easy example. If we need if we have resource management, we need the assignee to be set. Now you can enforce that at the foundational level in your workflows. Right? Again, because if that assignee is not set, we don't have a proper plan. We're never gonna be able to roll up as we look into resource management for this. And this can apply to other different areas too. I'd call it the minimum effective dose in that foundational level to set you up for success. And, again, the reason we bring it up is that you don't have those minimum things set. How comfortable are you with uncertainty? Right? Can you be 5% off, 10% off? So, Danielle, can you walk us through a little bit about that area and the importance of it? Yeah. I I wanna just be really clear is that a lot of times people will look at these tools and be like, oh, it has, like, some really good features. I really need that. And you have to also understand that it's built on the data that you put into the tool. So you have to have some really good discipline about making sure that you and your teams are recording the information that you need in order to get these results right. Like, if I don't have a start date or an end date in, the different epics or the different initiatives that I have, I'm not gonna get it into a Gantt chart where I can see all the wonderful things that can come out of that. So there really is a lot of discipline behind that. And so also just keep in mind that, again, this is not just like an IT implementation. This has to be done in conjunction with the business to make sure that people understand how to use it, how it functions, and make sure they're getting the right data into the system so you can get those desired outcomes. Excellent. Thank you, Danielle. Alright. So foundational level. Well, let's go to kind of the next level. And I'm gonna go into one of my, portfolios here, and we're going to bring up prioritization. Now I'm gonna briefly show you again, this is part of the new big picture enterprise that'll be released in on April 3. But so the concept here is that, you can easily see that we have a really nice clickable interface. It's going to compute a number. That number can be mapped to a custom field so that you can look at this by rank. And, also, notice that, we come with different prioritization templates. We also come with the ability to create your own cool formula out out whatever meets your business needs on this. Danielle, can you walk us through a little bit on this prioritization phase? I actually really love this. So a lot of times when we work with organizations, again, we're working with both the business side and then also the IT administration to, like, do the implementation and configuration of it. A lot of times when we're working with organizations, there's not a really good understanding about what the priorities are across the organization. Right? My priority is not your priority necessarily. This is a really good way if we get some business leaders together. We can kind of make some objective decisions about what is the impact of this particular thing that we're looking to deliver, what's the ease of that implementation. Right? So we can more objectively understand what the score is and then understand how we should be prioritizing versus necessarily, like, well, it's my priority. It's something I really care about. This is a really great tool for that. I also really love that you have those different templates in here because there are so many organizations that have different ways of doing this or just need some sort of a push in one direction of, like, let's just pick one. And so it's already built into the tool for you to be able to help to help make those decisions. A lot of times too, you'll also see a Shane as this is working with the business. Right? So if you don't have a lot of, if you don't have a lot of experience in this area, this is something that we can help you with. We can help set up those kinds of environments where we can get a lot of those business leaders together to have the conversations about why prioritization is important across the organization, across different verticals, and then using a tool like this to help help, execute. Excellent. Thank you, Danielle. Okay. So let's do a little re recap, and we'll dive right in. So we've looked at that foundational level. We ensure that we have the assignee said we prioritized it. Now we're ready to start, you know, our our plan. So one of the best things this tool does is resource management. So there's a couple areas we want to highlight. Number one, as and we'll just look at this from our home directory. One concept of teams. Now this team is, it's it's a it's a big picture field. Let's come into details. Why do I not perfect. So the first thing we'll do, you can populate this team however you desire. But one thing I want you to note, as as we look into, resource management is overall availability. It's a very common use case that people are on separate teams. And we've also seen it in the industry where people are like, well, what if I have a team that's, what if I have a member that's on a team and they're using story points? And I have another team member, but they're on a project that's using time tracking, can we do that? Absolutely. So remember for starters, we'll come back to this, that we do want to capture the overall allocation per team member. And, Shane, if I could jump in real quick there. Also, we're also seeing cases where we're having people that are part time. So maybe they only work, 25% or maybe 50%. Right? So this is another great way to make sure that we're allocating for the fact that maybe we don't have a full time person. Excellent. Thank you, Danielle. So, the next okay. Let's don't do that. Let's try this again. The next element. So with each resource that you have, we can allocate a couple of different things. So a workload plan. Are you working eight hours a day, five days a week? As Danielle mentioned, are you part time? Are you work ten fours? We try to make this tool as robust as possible to meet you where you are. The next thing, holiday plan. In Europe, holiday means, like, p t what we in The United States would call PTO. In this case, it means state or national holidays. And, also, we have skills. You can create as many of these as you want, and they're not one to one. Right? We can have multiple skills that map to a single individual. And once we have that set, this is where the glue comes together. Once you are assigned a task, in in in Jira, we now have that person configured so that we can now go look into resource management. Danielle, anything on that before I jump over to the resource tab? Yeah. I think that this is also really good, especially if you're an organization that different holiday schedules. So depending on where you are, maybe you're in different parts of The United States or maybe you're, you know, multinational. This is a great way to have different holiday plans that you can apply to really understand how that's going to affect the actual work that you're doing. So I really like this tool. Excellent. Thank you. Okay. So we're gonna come back out here, and we'll go into a portfolio. And now we're going to look at our resources. Okay. So, starters, what are we looking at? This is Agnes. She has zero hours assigned to her. Forty hours capable. Here's the, you know, the overall capacity. Out of the box, at 75%, big picture will turn it yellow to let you know that you're nearing capacity. And I think I have a good example here. Yeah. So red means that you are at capacity or overcapacity. By the way, this is completely configurable by you. Once you can get inside the box templates and go, well, I don't like 75%. I want it at 61. Whatever number you wanna create, however you want to do this, and you can color code this in in your own way too. Now, also, as we're looking at this, notice that we're seeing issues underneath here and assigning. This is a really long issue, but, we have that assigned. I have to have a start date and an end date, which goes back to what Danielle had brought up earlier too about foundations. Right? It won't appear on here, and it makes sense that the issue wouldn't appear on here because I don't have that start and end date to help me with my overall resource allocation. Okay. Back to this. Now we're looking at individuals. Remember that we could allocate per team and a particular percentage. Yeah. We can also look to see is your team over allocated or not. Lastly, the other thing to point out on this, for this is that skills. Where this comes in handy is that, again, we're looking at a developer. Well, maybe as you're looking into your resource plan, you know you need a developer. Do I have a developer that has the capacity to carry out this plan? One thing to note, before I turn this over to Danielle, is I do want you to note these grayed out columns here. And then this represents a Saturday and Sunday. When a resource is not available, this is going to bleed over into our Gantt view, which is next. Danielle, anything on resource management for us? Yeah. I think resource management is actually one of those things that we're hearing a lot from our customers these days. It's, like, really a driver for wanting to implement tools such as this one to really understand, you know, do we have the right people in place? Do we have the right of the right number of skills in place in order to achieve the goals that we have? I think there's a lot of pressure on organizations these days. And so having such a clear understanding in these tools of, like, where you are from a capacity perspective, where you can flex and where you have to pull back, it's really important to organizations to be able to see that. Again, this is something that we work on not only from a configuration perspective, but we'll also work with organizations on how to better conduct capacity planning or resource planning to help you understand, like, where you can flex, where you can pull things back, where maybe you're not getting predictability right now. So these are areas that definitely go into the people and processes side that then get manifested into the tools. Excellent. Thank you, Danielle. Okay. So one more time. Remember, we have these gray columns representing this. Now one thing I failed to mention, we don't connect necessarily to an HR system that's like that states this is when somebody's in PTO. We don't look into Outlook and do that. So, unfortunately, that has to be manual, but it can be done. We also provide REST API calls if that's something that you wanted to implement. Okay? From there, we will go over to our Gantt chart, if it'll ever load. Okay. Alright. I think I wanted to go down into legal because that's a bit of a jumbled mess there. Give me one second, please. Alright. Let's zoom in. Give me one moment. We're okay. Zoom in better. Okay. For starters, notice that the gray columns are back again that represent a Saturday or Sunday in this case, or if that resource has an absence, then you would see this whole row here grayed out. So first thing about big picture is that I'm going to attempt to place a issue to begin or end when a resource is not available. Notice big picture does not allow that. That's one element of this. Another element to look at, and I did not mean to bring that up yet, another element to look at is our scheduling. The two most common use cases for the scheduling are auto bottom up, auto top down, auto bottom up. Classic example where I have Jira epics broken down into stories. I want that Jira epic, the begin and end date, to be driven by the stories. We can also go auto top down. Okay. We have a known end date. We have a go to market date. We can't miss it. So do not allow the children to be scheduled outside of those known parameters. Okay? Now another thing to look at here is that I don't know if you've any of you have ever used advanced road maps slash plans. It comes with a scenario mode. So remember, big picture is bidirectionally synced with Jira. So, it may be that you're not quite sure of that schedule just yet. So we can come over to scenario mode, move things around as needed, but we can also do a little more here. We can show our resources panel, and, let me come back up. Give me one second. They think I have a much better example up here. Forgive me for jumping around. Or not. There we go. Let's try this again. Why am I losing my right there better. Okay. With our resources plan, we can now go into this scenario mode and look to see, do we have the resources to carry out the plan to begin with? And, again, since we're in that scenario mode, we haven't, we're not interacting with Jira. So I'll make a small change here. I have to I have to make that in another one. So you can make the small changes and then merge that with live and which is basically setting the beginning and end dates. Danielle, anything on this, section on the on the resource management slash Gantt chart area? Yeah. I think that this is really helpful. A lot of times, especially if you're, say, like, a program manager, portfolio manager, maybe a director of a certain vertical, a lot of times you're being asked, like, well, when will it be done? How are we gonna get this done? This is a really great tool for us to be able to have those different scenarios. Again, even, like, the auto scheduling, the bottom up and the bottom, bottom up and the top down, what do those actually look like? And do we have the right people in place to be able to actually execute on it? What I also liked, and I think you went out of it, but at the bottom too, like, even here, like, you'll see that there is a section that shows unassigned. So going back to some of those foundational layers too. Right? It's another way for us to understand what work has not yet been assigned, And so we can see that and then make the decisions of who should be taking on that work, again, with the the resource planning, capacity management, and then getting into more of the predictability of when something can actually be delivered, both looking at it from a task perspective or story perspective, and then also from a need by date. Right? Like, how far off are we going to be based on the types based on the people that we have available to work on it and the other competing priorities. Excellent. And my fault for skipping screens on you, I'd go down one level. So once you do make a change, to a given plan, absolutely, you can merge that to live. It just means basically setting the the start and end date on here. One other element about Big Picture is that as you're creating a plan I don't have the button. I'll have to come back to that one. We do have the ability to create a basic task, and a basic task is something that lives only in Big Picture. Afterwards, you have the ability to turn that into a a known Jira issue, and it's a way for you to, to kinda mock up work that you think may or may not happen in the future. Okay. So covered that one. The next section I wanna cover and I'm gonna jump over give me one second here. We wanna jump over into our, board view, and I switched instances because I have a great view over here. So tracking dependencies is, lose tracks of your lose track of your dependencies. You could be in poor world of hurt. So what we're showing here is, we have dependencies between a single team. We have dependencies across teams. So we're able to visualize this. Now for me oh, I'm sorry. We also color code these. So we have them in green. It's good. Yellow, gold means there's a possible issue, and red means it's an absolute misconfiguration. For that, on our info bar over here on the right hand side, we can also bring up our warnings to see what is the possible issue with this dependency. Now for me, if I saw this, this looks like a process that's out of control, but I bet Danielle and ISOs has a better viewpoint on this. Yeah. I think this is one of those one of those features that a lot of people see this and they're like, oh, I want that. Right? They wanna be able to visualize very clearly where those dependencies are, whether they're, you know, they're going in succession, and so you just wanna make sure that you have enough room between those just in case something moves so that you can still meet your deadline. But also so that we can all we can see the ones that are out of sync. Like, we can see a couple of red lines in here and understand that, hey. We've gotta go talk to those particular teams, like team alpha in this case and the team below them. There are dependencies between them. You really have to make sure that we're getting those teams to talk to each other, not just look at it on a board and say, oh, yeah. There's a dependency there. Right? Like, our goal is to make sure that we're reducing those dependencies, eliminating them as much as possible. And, again, that's something that we can do from the consulting side as we see these things to help you understand what those insights are and then the next steps that you should be taking with those business teams or delivery teams to make sure that you're gonna get the outcomes that you want. Excellent. Thank you, Danielle. Okay. So in this example and, again, we can use this with other different examples. In this example, this is a scaled agile where I have, multiple teams on synchronized sprints. Reason we're bringing it up is there's resource management and there's capacity management, which can be two different things here. So in big picture, we have a overall capacity. Now, unfortunately, this is not calculated for you. You do have to end enter that yourself. But from, again, bringing up our info bar and looking at the backlog, you have the ability to drag and drop these issues to do sprint planning, for the future. So and then, also, we're gonna be able to roll that up on a per team basis and then holistically, overall at an overall sprint, overall sprint basis. Danielle, sprint capacity management. Yeah. I think that this one's a really good one too. We're seeing a lot of teams now that are focusing more or a lot of organizations in general that are focusing more on, say, quarterly planning or even, program increment planning if you're following a safe methodology. This is a really great way for you to understand that, especially if you have distributed teams. Maybe you're not all in the same location. So this is a great way to visualize it and then also start doing that quarterly planning, making sure that you're within your capacity. The other thing I will I will say here, associated with this is that, we do have a lot of, I think being able to see the total capacity for the entire iteration across multiple teams is giving people giving organizations a lot more insight into how much work can get done and when you're overloaded. A lot of times, organizations don't really have that visibility, and something like this in a a sprint format or a quarterly planning format is something that's really useful for them. Excellent. Thank you, Danielle. Alright. So back to my other instance. So let's come back out, and we'll come back over to overview. So where are we at? We've normalized your data in your foundational level. We've prioritized, your your your epics or your stories or what have you. We've created a plan. So as we look we're going back into this portfolio section. So as we look now remember, if you see beta here, this is what's coming up in the, April 3 release with Big Picture Enterprise. The next level we want to look at is OKRs. Now let's see if this will load. Alright. So, again, back to those steps. We've done all that work. Now we're ready to establish your OKRs. Danielle, I talked to you about this previously, and I believe that you have another opinion because my way is technical. Yes. We we technical. If you get the foundation, I believe there's another alternative view on this on how you create these. Yeah. So there's there are a couple different ways. I think, logically, it totally makes sense that you would have those foundations in place and then go about creating your OKRs in the system. A lot of times, what we're seeing with organizations and what we would like to see more of is that the objectives and the key results are set by the executive team, and then we're making sure that our work actually connects back to getting that result that we're looking for. Right? We wanna make sure that all the work that we're doing actually ladders back up to an objective and a key result. Because if it doesn't, what's the purpose of us actually doing that work? Right? It's not helping us achieve those goals. Well, we work with organizations that are doing both. There are some organizations that already have OKRs. They just don't have a place to actually manage those. And so we'll work with them to figure out how to get it into the system, make all those connections with the actual work that they're doing. But we'll also work with organizations that have kind of scaled or grown to a point where now the way that they were managing maybe goals or maybe even initiatives that they had for the organization have now needed something like an OKR tool for them to be able to work in. So at that point, Shane, you're right. And that that organization most likely has all the foundational level completed. And now what we need to do is start actually implementing the OKR level. So it can go both ways. It just really depends on where you are as an organization. But, again, the big important part here is making sure that we're working with the business to have a really good consistent way of managing and tracking the objectives, the key results, and then the work that kind of flows down from that and making sure that they all connect to each other. Excellent. Thank you, Danielle. Alright. So one of the things I didn't cover, of course, I just brought up the OKRs. Well, let's take a peek at it a little bit. Again, I try not to get into configuration too much, but there's some important concepts in here. For starters, what kind of a OKR type do you want? You have complete, autonomy to do that. There is an API call, periods. Again, we can establish however you want to track this. And also, we come back to the overview. As you look at these OKRs, from a technical standpoint is that once you've created it, we have the ability to link it to any issues. And by the way, just because, just because an issue meets an OKR one OKR doesn't mean it doesn't necessarily meet another. So we allow for multiple linking in that way. Also, this has its own set of permissions as well, so we can do that. And, also, again, we can have the ability to update this thing. Is it on track? Is it off track? You know, how does it work? Okay. So If I could just from a consulting perspective. For any of you that are making risks within your organization or managing work, I really do love that you can set the status here. Also, I just wanna make sure, just kind of a plug, make sure it's not a watermelon. Right? It's not green until it's red. Make sure that you're being realistic with understanding when you do cut get into that at risk period and making sure that you're updating that. That is, that again is a discipline to make sure that you're getting the value out of the tools, and it's also gonna help your organization. Excellent. Alright. So let's come back out. We've covered a lot of material, for starters. Let's look at since we have a little extra time here, what we do wanna do is get to some of the chat and q and a questions. Danielle, if you could help me look through there. Wanna go over a couple of more things, and then, Danielle, again, I'll hit you up for other information as well. Let's go back into our expansion module. Let's cover a couple of more items that's being released. Financials. So when we look in our financials, realize this is in its infancy. This is going to be something that's, that's going to be developed over time. As we look into this, let's kind of look at our methods right now, good, that are current. So we can edit our calculation settings. We can set this to a day. We can set this to story points, and we can apply this at a box rate or a team rate. Now like a moron, as I was like, why can't we do this individually? And then I talked to the team. They're like, Shane, you you can't log in to the resources panel and go, Danielle is is rated at that rate? That that's what she is? It could cause anarchy. So we're keeping it right now through this team level and the box level. Again, this is something that's absolutely gonna change over time. Let's come back. And I I think that's a really good point there too is that, like, a lot of this is meant to give you an understanding or a general idea of how much maybe a particular component or feature that you're developing costs. Right? So So using something like a blended rate or an average rate is totally normal for us to kinda get that data out of it instead of doing a very more, like, financial analysis based on actual cost rates or actual salary rates for employees. Thank you, Daniel. Okay. And, again, Daniel, forgive me. I'm throwing this at you just off the cuff. We also have a risk module. So understand one thing about Big Picture Enterprise that is coming out. We've taken let me see. One, two, three. We've taken three Appfire apps and blended it into one rate. If you own Big Picture Enterprise, you own all three of these Appfire apps. So we have OKR, Surgeera, Foxly priorities, and this is going to be our replacement for our risk module. And forget me, Danielle. I'm throwing this at you off. Sorry. So what we have is that we have a risk register that we can create. And with each of these, it comes with, you know, your identified risk and and oh, I take it back. There's a better view on this one. Let's come up to our expansion. So now we can look at our risk, and we can if this will ever render. Yeah. And now we can do true risk management. Alright. Danielle, this is off the cuff. Anything on this section? Yeah. I think risk is another one of those things that organizations are really, you know, clamoring for. Like, they really wanna be able to do this. But, again, it comes down to a lot of discipline. This tool is great for understanding, you know, under or rating yourself on what the risk levels are. You gotta get into the tool. You gotta do it. You also have to have processes and, understanding across the organization about what really, constitutes maybe a higher risk versus a lower risk. It could be different across the organization. It could be different across different verticals. So making sure that you have that understanding as an organization of when something reaches a high, this is what happens or this is what that means. That's really important. And, again, that happens outside of the tool, not just in the tool. The tool will give you some of those indicators, but then there's gotta be processes that happen outside of it to really, you know, again, reap the benefits and get the outcomes you're looking for from a business perspective. Excellent. Thank you. Okay. So, we'll dig into some of the q and a questions here in a minute. But, something from our customers that we've seen and this is an area where this is where ISOS really can help you along with you along with the governance of who you're setting up, you know, per team and how you're setting up your security sessions. Let me give you a great example of something that went horribly wrong is that we say that, Big Picture is bidirectionally synced. What does that mean? So we have 12 custom fields here on on the left hand side. This is Big Picture. On the right hand side, this is my Jira counterpart so that you can set it in Jira or you can set it in Big Picture. Now this is a general mapping. We can also do a custom mapping. Great example. Teams, some teams are have already used, plans, and they are using target start and target in, not start date, not start in. So we allow for you again, we try to make this tool as flexible as possible. So we allow for that kind of, again, allow for you, you know, the the differences between your individual projects. So let me tell you a horror story right quick. And, again, this is where ISOS can shine. So we had a customer come to us and, like, okay. So a hundred thousand issues in, we noticed that this start date has a lowercase d. I don't like that. I need start date to have an upper case d and end date to have an upper case d. A hundred thousand issues in, they change it. Now they have no idea which one was updated last. But and on some of them on their screen schemes, they had both of these dates listed and became a nightmare. This is a just an easy soft tosser where ISOs can come in and help you establish these practices to not allow you to get in this situation. Danielle, anything on kind of a little more about governance and best practices on this? Yeah. I think that's one of the places that we do really shine, and thank you so much for calling that out. And a lot of times when we're working with organizations, like, we do understand the second and third order effects of what we're doing. So a lot of the time or I guess all of the time, actually, we'll come to you and tell you what our recommendation is and why that is our recommendation, and that goes within the tool and the way that we're setting it up. We'll identify, like, the risks or issues between their different systems and the configurations. But we're also gonna tell you what those second and third order effects are from the business perspective. Again, those people, the processes, the practices that are in place that are going to need to change or that will need to be working side by side with the business leadership in order to get the value out of the tool. So, again, you know, that is something that we'll do. If you want somebody to work with you that's gonna do everything that you ask and not ask questions or not push back, we're probably not the right, consultancy to be working with. But, you know, we do it because we wanna make sure that you're successful and you get those business outcomes you're looking for. Excellent. Thank you. Okay. So let's go back and regroup. We've established our foundational level. We've prioritized. We have a plan set inside big picture. And, again, just you don't have to necessarily get big picture enterprises. Those are just add ons to allow you for growth. We planned it. We have your OKRs as an example that we've set up. Let's see if there's any other areas we wanna talk about. Did you find anything in the q and a, Danielle, that we needed to bring up? I'm just gonna go with the the first question maybe that, I see on here from Dennis Gay. He asked how much time should an organization set aside for setting up the configurations? So it's a great question, Dennis. And but a lot of it and this is such a such a consultancy answer. A lot of it's gonna depend on your organization. Right? It's gonna depend on how many people are in the organization. It's gonna depend on, where you are as an organization. Do you already have Jira or is it a completely new system that you're getting into to then be able to put big picture on top of it? The other thing I would say is that from a configuration perspective, it's usually relatively quick. However, a lot of times during that discovery process when it comes to configurations, we're gonna identify things that don't really jive with the implementation of a big picture. We're gonna identify things of, like, hey. There are teams working in various different ways that maybe you wanna think about consolidating or getting some teams on the same page so that we can reduce, you know, some of the, duplicity in some of the configurations that have already been created. So it is gonna depend, and I'm sorry that's, like, a really, terrible answer. But a lot of it's also gonna you also have to make sure that you're planning time for the actual rollout, the training, the business, the business getting involved in how you're gonna be using this tool. So it it can take, you know, a significant amount of time for that as well. Excellent. Thank you. Alright. So I'm looking through the the some of the q and a, and I see one one not answered. My southern's going to butcher this. Jyoti Babad, technical question, but can you map a script runner custom field to the app configuration? Jira plans doesn't support it. Unfortunately, I've tried that one. No. You cannot add a script runner custom field. It just doesn't work. Let's see if there was anything else. You know, one of the questions that comes up a lot too, and this would be a great one for you as well, Danielle. I'll give you some of the technical part. Well, what's the difference between big picture and advanced roadmaps plans? Advanced road maps plans, I love that tool. I I find it a great way to to view my work in the in the nice, you know, Gagantt style. I think the key differentiator is what we covered in our resource management. I believe that we excel there. And, also, dependency tracking, you can do that in advance in road maps, advanced plans. I think that we do a much better job of highlighting that. Danielle, can you think of other areas just as a differentiator between those? Yeah. I mean, honestly, that that, planner that you had when we were looking at the boards for the different iterations, right, for the capacity planning and the dependencies, that's a really big one. We don't have something out of the box like that for advanced road maps. And this is honestly, it's the biggest reason why people, I think, will will end up buying big pictures when they see this. This is what they're really truly missing is, like, this particular view that shows the iterations. I mean, it's very it's very representative of what a quarterly planning or a program increment board would look like. And, again, it's a way for us to make sure that we're not duplicating effort to get things from, say, a physical board into the tool itself. It's a great way to plan with distributed teams. It's also another great way to make sure that we're not, we're not fat fingering things as they go into the system from coming down from a board. So I think that's one of the main one of the main things that we see. The other one that I'll call out, you know, that we were talking about earlier is that prioritization and understanding from an objective way. Right? A lot that's not built in right now into Jira. So it is something that a lot of organizations need so they can understand, you know, if I'm gonna use Rice or I'm gonna use Wiz Jeff, what is the actual prioritization based on those factors and being able to calculate that natively. Excellent. Thank you, Danielle. Okay. So, as we come back out, one topic again, I always manage to skip a couple of things. So when we talk about our modules, here are our module selectors. We go into manage modules. That's a lot of modules, especially if you have Big Picture Enterprise. You would never toggle all of these on at once. It's almost death by too many options. It it's overwhelming. Another area now one thing that Big Picture does is that remember, we have these templates. Now these templates will auto configure these for you. You still have the ability to turn them on, turn them off. Again, another area that ISOs can help you in is again, we go back to governance and foundations and all of that. It's another area. But, again, with our modules, yes, you have the ability to turn these on and off as needed. Alright. So I'm gonna look through Danielle, do you have anything? This is the material I had. We might be able to close a little bit early. What I wanna do is I wanna go back through our q and a and see if there's anything else. And forgive me for putting you on the spot. No. It's okay. Just looking through. I think when we were looking at the dependencies, Kira Graff was asking, do you only have one link type, or can you specify multiple link types? That's a good one. Lukasz, you wanna come in? Because I know that we can specify the blocks link, and I know where the configuration is. You wanna jump in on that one, please? But, of course, you decide. So in general, if you go to, application configuration yeah. Go here and then to general and then to links. So dependencies. Exactly. Yeah. So if you scroll down, you can see that we've got, strong links. So the Gantt chart links I mean, the links that will always cause the scheduling impact, and you can, of course, synchronize them, with a custom link from Jira. But when it comes to sole dependencies, as you can see, that's, it's another, it's another use case. So sole dependency, it's an agile type dependency to visualize, well, dependencies that are across teams, cross sprints, or both. And as you can see, we can, visualize up to three types of links, from Jira, so blocks, relates, and, well, any other. However, when it comes to the creation of link in the Jira directly from the graphic user interface of Big Picture, by default, it is blocked. You can, of course, change it. Makes sense. Alright. Alright. We've gone through the q and a. As we close here, Danielle, I'll pass it over you for closing thoughts here in a minute. But as we close here, remember, big picture is agnostic. It tries to meet you exactly where you are. Lot of flexibility, a lot of bells and whistles, and a lot of areas where ISOS can truly help you to set up this product the right the first time so that it just flows into the future with no issues. So, Danielle, any closing remarks? Yeah. Thank you so much for having me. It was really great to be able to be a part of this webinar with you. The only thing I would try to get across is just know that when you're implementing a tool like this, it is truly something that has to be done in partnership with the business. It cannot be done completely and get the outcomes you're looking for by just having, like, an IT administration, IT ops be the ones that control this tool. It really has to be a partnership. We love working in that environment to both help the business, but then also the IT side. I mean, we have the expertise in both, and that's why we love working, with Big Picture. Excellent. So I'll stop sharing here. Thank you so much for your time today. Appreciate you joining and appreciate our partnership with ISOS. So thank you so much. Have a great rest of your day.