Name: [Live Demo] All-in-one Project Management with BigPicture
Uploaded: 2025-11-26T15:16:05.880Z
Duration: 59 min 48 s
Description: [Live Demo] All-in-one Project Management with BigPicture

Transcript for "[Live Demo] All-in-one Project Management with BigPicture": Hello, everyone. Let me welcome you to Big Picture webinar, where we are about to cover, the well, few use cases when it comes to Big Picture. But together on the stage with me, we've got Nicholas, who is a business consultant from our solution partner, NSI. Hello, Hello. Nicholas. Hello, everyone. Hello, Lucas. Right. My name is Lucas, and I'm a senior solution adviser, in BigFuture. And, well, we can make an initial assumption that, I know this tool kind of well. Together, with us back in a backstage is a friend of mine, Shane Garnett, who is also senior solution adviser in Appiah, and he'll cover in the q and a session today. So all of the questions that you can ask, that you will have, during the webinar, please, please ask them, in the chat. And then before we start, let me just, mention one thing because most certainly, you will require I mean, after this this short webinar, you will require services like tool implementation or, the training of your crew. But please take note that we as a vendor of BP sure, I mean, Appfire, we do not provide, this service. So this kind of services are exclusively offered by the network of our partners. So in that case, NSI, that's the main reason that, we've, invited, Nicholas to co deliver that webinar, with us. Right. As you can see, that will be a fully implemented big picture running in cloud. And, actually, one customer once told me that there are many applications, in the Atlassian marketplace, But when it comes to big picture, that will be operational system for Jira. And, you know, it's kind of true, because we've got a few killer features, that big picture provides that you cannot do, in Jira. So first of all, as you can see, Big Picture can adjust to multiple frameworks in the same time. So, we've got an ecommerce platform where the work will be divided to iterations. Then we've got the first portfolio, with the level of initiatives, and then we've got, two projects that will be managed by teams. Then, it's another framework. We've got another portfolio with, this time, five projects. So let's start with the first one. Project there is my tiny sandbox where I explain the customers more most difficult parts of big picture like scheduling and so on. Then, two waterfall, base house constructions. So, this is pretty much pure PMBOK, pure waterfall. Then, we've got hybrid. Hybrid is support application development project where we blend waterfall. So as you can see, we've got three waterfall stages. So deployment, initiation, and operational preparation. And the only agile that would be software development, that will be decomposed then to three iterations. And then the last, would be risk register. We scroll down, and as you can see here, we've got three examples how Big Picture can adjust, to scale agile. So less requirement area divided to sprints, and then, as you can see, we've got solution train with two agile release trains, of course, following safe manual, decomposed to increments and iterations. So, Big Picture can support scaled agile as well. And, here would be, the second killer feature of this app because, if you ever decide to change the way how you manage projects, big picture will follow that. So it will not force you to change the way how you work. It will not force you to use a given framework. It will adjust to your best practice. Right. Having that said, let's maybe jump, to the first example. So the house construction. And as you can see in here, we've got, well, a project, from Jira. The only configuration screen that we would see together is the one hidden, in the configuration because, well, the key message or the key question can be, but what data we are looking, at or or what source of that data will be. Well, if you go to tasks and school definition, as you can see here, you can decide what projects, boards, or filters are going to be bidirectionally synchronized from Jira with big picture. And here, we've got one project, from Jira or space as, the recent name suggests. So one space, from Jira. So all of the 33 issues are going to be visualized in Big Picture, but from here, we've got also a new possibility. So we can connect the Trello board or to external cloud. But for that, you need Big Picture enterprise. Right. So our data comes from a single project in the Jira that is visualized, as a top parent on the Gantt chart, plus, it is a part of our breakdown structure. And then, so you can see, we cascade down for location search, design, financing, construction, and so on and so on until the whole project is finished with the final milestone. And please take note that, in this example, we use something that we call basic tasks, to act as a role of a parent. So a basic task, that will be the first and actually major feature, of, Big Picture Gantt. So basic task is a task that doesn't exist in Jira. It is a perfect solution where when you are in the ideation phase, or, it can also act as a milestone or as a full parent. But, of course, whenever you're ready, you can convert that, to become a Jira issue. But, but, if we expand, that work breakdown structure a little, as you can see, we've got aggregations on, the parents and aggregation, on the top parent, so on the whole project. So for example, when it comes to location search, we've got 50% of tasks in the status of to do, zero in progress, and 50 done. Of course, everything comes from, the workflows, in the Azure. But the point is that if you open any task or work item and change the workflow, So let's change it, maybe to in progress and go back to big picture. It's like three, two, one, as you can see. We've got that task in different workflow. And then if we change back to to do, it will be automatically sent to, Jira. Right? So we've got bidirectional and life sync, between two platforms. Plus, if Nicholas joins me, in my, in my cloud, I'm going to see the avatar of his user in, in, the spot that I'm pointing for my mouse cursor. It would mean that Big Picture automatically turns collaborative validation mode on, meaning we can altogether all work on the same gun chart, fully remote, and we are about to see each other changes live. So, yeah, that's that's a very important, feature when it comes to, project management. But when it comes to, the waterfall features, well, certainly, you've already noticed that we've got some, stripes below every task. Right? So as you can see, the black one, which is the current baseline, and then, I believe this this this green one or this green connected with blue, I think. But in general, we've got the second baseline over here. Right? So, baseline, of course, that that feature gives you an overview what was the initial initial position of a task. And then please take note that we had a little delay. Right? So, the end date of a project differs from baseline. So let me override it, like so. So as you can see, currently, we've got a baseline that is equal to the project end date. Right? So, of course, after you finished in the project planning phase, you you should baseline your tasks so then we can track any delay that can happen in our project. So for example, when it comes to design including spaces, if we've got a delay in here so you can see that the end date differs from the baseline. But when it comes to, the project, well, no harm done, so the project wasn't affected. Of course, you can well, first of all, you've got the end button. Right? So if the change was unintentional, you can revert that operation. And as you can see, it will be, automatically reverted. But, certainly, you also notice that some of the tasks will get different different colors, than the workflow. So the tasks, that are highlighted in this pink and red stripes, well, these are, of course, tasks that are included in a critical path. And then if we stimulate a delay on the task that is included in a critical path, as you will see, all of the remaining issues are delayed, causing the whole project to be delayed. And this is, exactly the concept of a critical path taken from the PMBOK guide. Meaning, if a delay is, that will happen on a task will cause the whole project to be delayed, therefore, that task should be included in the critical path. That's, of course, not everything because you can track all of the delays when it comes to the reporting section. So as you can see, we've got the report called plan delays. So, you can like, from the very first point of view, you can see, that we've got, well, a few tasks delayed, and this number is going to exactly return the difference between baseline and, the actual end date of a task. But, to use that report, let me just underline that this is Big Picture Enterprise report. Plus plus, we can track, we can, track the baselines that happened in the past. We call it baseline versioning. Right? So as you can see, we've got few baselines over here. So big picture can visualize up to two baselines in the same time and store up to, 20 baselines in the version history. But please also take note that, the version history, that would be another feature of enterprise. That is not in the standard b picture. And, also, most certainly, you're wondering what this diamond shaped task is. Well, that will be a milestone, but milestone created us an issue type of milestone or so I'll use the word of, work item. Right? But this work item is really a milestone, in the Jira as you can see. But what big picture will do, first of all, we've got this ticket labeled with milestone, and then this task will have, the form of diamond. Plus, according to PMBOK standards, milestone is not a task. Therefore, as you can see, the links that we've got, between these issues, they are not going to be affected by the actual milestone. Right? So milestone, in in that case, it doesn't reschedule, this task. Right, because milestone is one day event. And then milestone is not included in a critical path chain because, again, it's not a task. That's something to be achieved. Right. Then, if we collapse work breakdown structure panel a little and then open infobar, as you can see here, we've got a few useful information from the perspective of project manager. So first of all, the list of dependencies. And as you can see, you can expand, the given, the given set of tasks. And then by these three dots, you can focus your view on the source or on the target. So if you get a lot of dependencies, you do not really need to search them by yourself because when it comes to big picture front end, it's really beautiful. And then a second option, so the tasks that are overdue. And, again, if you highlight the task, big picture will snipe your view automatically and focus it on that task, and the number that you can see in the right corner indicates, the overdue. Days, of course, calculated with the marker of today. Then the list of milestones. And, again, big picture. So you can see every time I highlight a task, we'll focus your view on a given milestone, then the list of tasks that are on a critical path. Then if you're interested, what were the recent changes, to your project, you can track them, in the change history, bulk change. Well, if you decide to make a bulk change, when it comes to big picture, you don't need to JQL that in the Jira. You can do it from the graphical user interface perspective or the very recent enhancement, so, reporting section added to the infobar. That is going to currently track, as you can see, team's capacity and the progress of our tasks. Right. Having said that, if we are about to return to the actual Gantt, first no. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No. No If you press this plus button, you can add any custom field from, your Jira instance, and then you can save, this data, as a column views. Right? So that's well, the set of data that you require that you would like to see, you can fully customize it. Yeah. You can fully customize it. Plus, two more extra features, before we jump to another example. So a what if scenario. Right? If you, create, a scenario mode let's rename it three. It's me being creative. As you can see, big picture, is not anymore in the live sync of Jira. And currently, we can modify our Gantt chart a little. Right? So let's simulate the delay on two tasks, and then, of course, scheduling impact is here. But then the point is that I haven't done any changes in the Jira yet. So that's my production Jira, and this is the scenario that I've just created. Right? So in the scenario mode, you can try different variants of your Gantt chart schedule without affecting, the actual Jira. Of course, here we've got a few more possibilities. So first of all, you can review your changes. So what you've done and what are the consequences of your action. From here, you can override, the Jira data, but you've got also the undo button so you can revert the latest change. Or if, you're not satisfied with that scenario at all, you can just delete it, and then nothing is going to be saved in the Jira. Let me just mention that in standard Big Picture, you can create, only two scenarios. I mean, one public and one private, so one per user. And Big Picture Enterprise will give you unlimited, numbers of scenarios. And then, last but not least, of course, you know, when it comes to the the GAN sort, we've got many more features. But last but not least, if you'd like to if you'd like to turn your GANs more to a dashboard, you can activate the function of task grouping. And then, the list of grouping elements, they are going to be taken from the column views, from the gunshot so we can use any custom field to enable grouping. Let's say that we'll, group issues by, issue types or work items and statuses. Hit apply. So then big picture will temporarily ignore or break down structure and give us the report. So we've got 26 tasks. And among them, we've got six in progress, 18 to do, and we keep scrolling, and two done. Then we've got seven milestones, three are in progress, three to do, and one done, and so on so on. And then please also note that these tasks are going to be grouped also when it comes to, the graphic user interface of the Gantt timeline itself. So, Nicholas, what do you think about these features? Or maybe you can share, some thoughts about, you know, PMBOK or or waterfall best practices. Yes. Sure. Thank you, Rakesh, for for do those features, demo. And, indeed, what people, usually really like, are the, the ones you showed, about grouping tasks and, customizing the columns and so on. Because planned work project activities always have multiple links or can be analyzed from different perspectives. And what they find great about, those features, is that from a common set of data, your Jira work items, Jira tickets, It's easy to provide several views of the same planning. For that, then the grouping features are just great, really appreciated, by the people who use Big Picture. Besides the main planning view, like waterfall hierarchy, for instance, as you showed. With a few clicks, you can have a focus on specific teams, specific components, operational, or even strategic topics. And if you add that, if you add to that the capability of customizing columns, with some aggregated data, for instance, statuses or estimates, you have all you need to easily provide accurate information, adapt it to the different stakeholders, or the the different meetings you will have. So, yes, really, really good, a good thing to to use. Pretty much. Thank you, Nicholas. By the way, when it comes to sharing the data of the with the stakeholders, we've got exporting button over here so you can, export, in that case, your Ganshard, to CSV, image PDF, Excel, or Microsoft, project extensions. But, for that for to do it, for that, you need to install big template, which is yet another application from the AppFires table. Let me just hit the export, and then, while, the library called PuppyDir, well, is exporting the image PDF. Let us jump to another example that, we've got. Yeah. Let's, let's switch it to a hybrid. So, hybrid. Oh, by the way, as you can see, we've got our, Gantt chart exported, and let me just show you, how it looks like. So as you can see, that is, the full Gantt of our house construction project exported to image PDF. So having said that, the module of, the project of hybrid, and currently, we've got additional extra feature in here because, the the project phases that, you can track from the overview. So, oh, by the way, from the overview, you can also, track, team's capacity, status of the boxes, and OKRs. Right? But let's disable them for now. You can, see that we've got four stages when it comes to our project, and you can track them from the gantt chart. Right? So they are visualized in here. So your waterfall teams, exactly know, in what stage they are. Plus, here we've got little bit different, work breakdown structure because, as you can see, we've got processes and tasks, so the waterfall part and then features and stories. But, what I would like to focus on because, technically, that's a gunshot. Right? But, in this example, I would like to focus more on the resources management and a little bit of governance. Right? Because, the resources module would give you an answer. Do you have any resources that are over or under allocated? So in general, this, module will provide you, an answer, what is your resources utilization? And then, first of all, here, we've got a list of assignees, from Jira, but you can track assignees, teams, projects, or skills. Projects, of course, that will be useful when it comes to the level of portfolio, which I will very soon show you. But, for you to understand how this module will calculate, will calculate capacity, we'll need to jump to the smallest possible scale, which is daily. Of course, of course, I know that the daily, daily management daily scale is, not the scale that well, let me just reload the page. Not the scale that, will be used in a company, but, with this scale, you will very clearly understand how Big Picture calculates the capacity. So first of all, we've got list of tasks, in here. And then as you can see, we've got our daily escape enabled, so we've got the timeline on the very top. And then as you can see, we've got three rows. So first of all, this icon with, fully charged battery, that will include, that that will give us, an answer. What is the capacity of a given user? In that case, myself. And as you can see, I can deliver eight hours of work, Monday to Friday, excluding Quick Hits. So then the question is, how Big Picture knows that value? How Big Picture knows that it is eight hours? Well, if you hit that, if you hit that box, you can see that, we've got, the resource that is assigned to the default workflow plan. So let us deter that presentation a little and go to the module go to the section, actually, of the picture called resources. And in here, you will see that we've got the list of, assignees from Jira automatically, imported to, Big Picture. Then, every resource needs to be assigned to workload and holiday plan. So then as you can see, you've got multiple, workflow plans. So we can create, more than one and adjust, the plan, well, to your country. Right? So or to the plan that, you've got in your company, but, I'm assigned to default work plan. So, end user assigned to it will deliver eight hours of work, Monday to Saturday, eight hours per day. Of course, no one will be happy about five to four Saturday, so then holiday plan kicks in. And, again, we can create more than one, but I'm assigned to default holiday plan, so I've got weekends free. And, of course, it's fully, editable. So if you hit edit details, you can, select some extra working days, or, you can specify fixed or floating holidays. So you can, adjust it, the way how you want it, but the combination of workload and whole day plan will return us the base capacity of, user. And then this discharge battery, so the second row, that will be remaining capacity. So the amount of work that I can still deliver or I need to deliver surplus when it comes to overallocation, which is indicated by the red color. And then this checklist, that will be workload, so the amount of work that I need to deliver in a given scale. And then with the speedometer that you can, open from the top, you can actually track three fields followed by three effort modes. And, of course, every effort mode will, will cover different business use case. Right? So original estimate, will give you an information in the project planning phase. So after you've done the whole planning, and after the original estimate is, is specified, in the level of tasks, So then, this module will give you an answer about your resources utilization. Remaining estimate will give you the answer, what is the amount of work that you need to deliver that you still need to deliver, and then story points if you ever consider an agile transformation. So, I need to deliver two tasks. So testing and deploy and deployment. And as you can see, this task has got one week of original estimate, and the second, well, has got four weeks of original estimate. Therefore, in order to deliver these two issues, I need to work, well and as I told you, we've got a little governance problem because for five days, I'm going to be overallocated. Then we'll need to address that. We'll need to, for example, extend the duration of the task called deployment. As you can see, these calculations are about to change. They are about to change accordingly. Right? So currently, we've got over allocation problem fixed. Right? So in order to deliver these two issues, well, I need to, in that time frame, I will have zero point two hours free, every day. And, of course, if I expand it even further, well, you can see that right now, I can deliver zero point nine hours of work, every day, more so I'm not over allocated anymore. Right? But then, if I shorten this task for the duration to be only three days, so as you can see, I will heavily overload that resource, so in that case, myself. Right? So, these three values are going to, cooperate together. So since you already know, how everything is calculated, let me just mention that, in big picture, you decide what this threshold, is, how it is calculated, and, and what color will indicate, over or under location. But to do it, you need to go to box types, and then you can decide what that thresholds would be. Treat the box type as a template. Right? So box type would be a template as the fruits that will be used, while you create a new project in the picture. And then when it comes to coloring rules, as you can see, as I told you, you decide what that thresholds would be and what color, will be displayed in the module of resources. And then, of course, let's raise that view to the scale that is more connected with reality. But most certainly, you're asking yourself one question the very moment. So what if we've got cross project work and resources? Or what if we need to scale that information to the level of portfolio? Well, big picture provides that answer or these answers as well. So first of all, if you would like to track overall assignment of your resources, so if you've got cross project working resources, you can activate the button of showing overall assignment. And then as you can see, big picture will include, in the calculation the tasks that are outside of this project. And, of course, it will affect the capacity of a given user. And then, of course, you remember that hybrid among with, four different projects, they are all part, when it comes to the portfolio. Right? So that portfolio is good to aggregate, our data, but not only from the perspective of the overview. And, by the way, as you can see, Shane, is on that instance with me. So big picture turned on, the auto turned on, the collaborative edition mode. But then if we go to the resources section, you will see that you can engage with double grouping. In that case, we've got, our, our, resources grouped by projects and then individuals. So first of all, I can track the health status of my project and then the personal contribution, and I can do it for every project, in the portfolio. Of course, if you're interested in, the team's capacity, you can just switch the module to show you a team's contribution. You'll see as in big picture, you can create teams as well. Or, you can see the capacity by skills. Right? So here from the very first point of view, you know, if we are missing, some skills or not really. So, yeah, big picture scales, that information, to the level of portfolio as well. And not to mention that if we, go to the main root box and scroll the view all the way to the top, that main home box, will aggregate everything as well. When it comes to the resources module, please don't mind this error. You know, it's like live television. It's live presentation. So if anything goes wrong in here, you'll for sure see it. So that's not a PowerPoint. Right? But, as you can see, if we engage, double grouping in here, so we've got, like, this this let's call it the c level of resources dashboard. Right. So, Nicholas, what do you think about this module? And, yeah, tell us more about the the governance problem that, we're facing here. Yes. Yeah. Resource management, of course, is, is a really big topic. In every organization, resource management practices vary. But in an ideal world, they should always be grounded and recognize methodologies and adapted to the project context. So whether you're for PMBOK, PRINCE two, agile, or lean principles, the goal remains the same. Optimize the use of available time and capacity to deliver value, and we must all keep that in mind. So planning and capacity assessment should be proportional to the benefits they deliver. That's what I always say to to my customers. Excessive detail, can create waste, while insufficient planning can lead to risk and misalignment. So I advise the people I work with to always consider the return on effort, but also remember that some activities, such as risk analysis, compliance, stakeholder alignment are essential, even if they or if their return on investment is not immediately, visible. The most efficient planning must contain the right level of detail. That that's what, we we have to remember, the one that fits best with your context. So in general, for predictive or complex projects, you can begin with high level planning and resource location, then progressively elaborate, as more information becomes available. While for adaptive or agile environment, it will be more interesting, to prioritize smaller iterative planning cycles, focusing on continuously delivering the value, and focusing on the team autonomy. And if you add on top of that, that planning and capacity are always based on estimates and assumption, uncertainty and risk are inevitable. Things are not always going as planned. Therefore, your planning and resource management tool should offer different options with high level and detailed views that are possible, adapted to organizational rules and context, and enforcing your standards where needed. And that is exactly what Big Picture provides. So we assessed several tools, and we found in Big Picture, the the best match, to to adapt, to this, to the different, situation the the companies can, can face. Yeah. So, they didn't mention thank you, Nicholas. Yeah. That's that's so true. I didn't mention it, but, yes, Big Picture is a smart tool. So if. you need to reschedule if you need to assign the task to a team or change, the the user. Right? So Big Picture has got, the mechanism to suggest you the perfect match. So, yeah, if you've got, over allocated resource, Big Picture can suggest the change. Right. When it comes to resources management, I didn't, cover one, extremely useful topic. So the topic that's, main feature, of course. So the feature that lets you to create, the scenario inside, the module of resources. But, here, the scenario mode, will provide you, the feature called or will support the process called, resources forecast. Alright. Having said that, let's let's switch our approach completely because as you can see, this presentation is designed to give you, a customer journey, a customer that will change the project management framework as we progress. Right? So let's go to the train. Let's go to the, release train to show you all the agile features of this application. So first of all, as you can see, we've got, an agile road map. Well, technically, don't be confused by the name because, technically, that's a gunshot. But, you know, as far as my knowledge about safe goes, there is no GANT in in the safe. Right? So that's the reason I've renamed that, that module, not to sound that waterfall. Right? So we don't have GANT. We've got an agile road map, and that's true because, very soon, you will realize that it is an agile road map. So the Gantt chart was redesigned to serve an agile feature. And, well, here, on the top, we've got the hierarchy of objectives and key results, but this is a part of big picture enterprise. But in general, when it comes to the issue level, we've got epics and then save features and stories. Please take note that this is really a save feature. I mean, when it comes to work item type in Jira, this is a safe, feature as you can see. Come on, Claude. Right? So safe feature. So but, well, let me maybe show you something different. This is 10 user, Jira Cloud sandbox, but, well, if we switch our box a little when it comes to a product that's called advanced training, you'll see here that we've got work breakdown structure kind of complex. Right? So as you can see, we've got work packages, initiative, epics, stories, tasks, and so on. And this is really a work package so that it that is an issue type or work item in the Jira of work package. Right? And then it is connected to, initiative with the link consists of initiative. And then if you open that initiative, as you can see, it's in between epic and work package, and that hierarchy will be displayed, in big picture, Ganshardt. Right? So, if you've got big picture, you decide what your work breakdown structure will be. You need 50 levels. Please be my guest. You can create 50 levels when it comes to your issues hierarchy. There are no constraints. Right? But, here, we've got, like, three levels, and I think time to time we'll get capability. But as first of all, you can see that increments and iterations are visible, in our agile road map. And then if we activate the quick filter of epics only, you can exactly see an agile epic road map. So you exactly know what epics are going to be in cross increments. And from here, you can see that if you manage to deliver, the tasks that are scheduled for development, in the first iteration of program increment two, if, you managed to, deliver them in the previous iterations, so then that epic might be a part of the MVP. So after the first release, after the program increment one is delivered, so, yeah, that IP can be a part of the MVP. Right? And let me also mention that here, the scheduling of auto bottom up will always automatically calculate the duration of epics based on features, and the feature duration will be automatically calculated based on storage. Right? So we are sure that your epics are always up to date. But, when it comes to the very beating heart of any agile, company or any safe cast any safe company, that would be the module called and, again, don't be confused by the name. The original name is board, but, in that case, we've got a different, different name supporting PA planning because that's exactly PA planner. So, first of all, let's activate another filter of epics and features only and go to the level of program increment where according to set, we plan features. So as you can see and then, if we clear that filter and drop one level down, that will be a team level, where you can plan tasks, in iterations. And, of course, these issues, they come from Jira. So, if we open one of them, and then, let's go to the board, the software board in the Jira. The software board of team alpha, you'll see that in here, we've got back we've got backlog. I need a backlog. We've got come on. Come on. Well, my backlog doesn't want to to open. Right? But, let's switch to team gamma. K. And the backlog is going to, is going to give us, to return us the tasks. Right? But in that case, I've renamed the sprints in Jira to follow, follow the framework. Right? So sprints are named as iterations. Of course, we can plan a quality mark, between iteration and sprint, the only difference being the fact that, iteration comes from safe and sprint is more scrum. But as you can see, we've got few issues in iteration 1.2 Tim gamma. And, of course, these issues are going to be visualized here in the swim lane of Tim gamma under iteration 1.2. And then if we are about to send one of them, let's say, p p 65 let me highlight this task, in, big picture. By the way, of course, I call it Spaghetti view. So as you can see, the Spaghetti view, of course, indicates dependencies. That's yet another feature that Big Picture provides, but let's collapse them. Well, let's, first of all, show you the graphic user interface. So if I highlight a given task, as you can see, all of the remaining dependencies are going to be blurred, and your view will be focused on a task and the dependent issues. But we can, collapse them, for that view to be more transparent. P b 65. Right? One of the many tasks that we've got in here, and let's send them to next next, iteration, in the Jira. You can already feel what's going to happen in here. Let me wait a whole second. Come on. Well, I'm a little impatient, so, let's reload the page. But I think that we've got the task already in the next iteration. Wait. The second way. The second ping p P60 5. It's there. Right? So, well, tell you what. Let me, let me send it back, to the previous iteration and then and then arm myself with patience. P p 65 highlight on my screen. And three to one. K. Man, as you can see, it it just jumped to the next or to the previous reload the page. Right? So we've got bidirectional and live sync with Jira Sprint. And, you know, of course, I love Larsen and and I love Jira, but, when it comes to, the agile features of the Jira itself or when it comes to scaling that, information to scaled agile, we are missing a lot of vital information, from the agile world. So first of all, what is the estimation of story points? Well, theoretically, we can find this value in here. To be honest, that information doesn't scale. Right? Because these stories are about to compose some higher level task like feature and then epic. Right? So then what's the story point weight on my parent? Then what are the dependencies that can be cross teams, cross sprints, or both? Then what is the developer velocity? What's the developer capacity? What's the buffer, that I need to undertake when it comes to tasks that cannot be estimated in story points like bugs? Then can I prioritize my backlog in here? What if I would like to use another factor, name it weighted short and job first, if we are speaking about, scale of agile or any other prioritization, mode that you prefer to use? Well, I cannot do this in Jira. But what you can do, is to go with big picture and ask Nicholas for implementation. Yeah. So, then first of all, dependencies. Right? So if I expand, the dependencies, of course, these are created with graphic user interface. You know, very often, when I speak with with customers about the big picture and about project management tool, very often, I hear, when it comes to, like, other project management tools that the one, can be Microsoft Excel. Oh my god. No. I mean, you know, I'm an Excel guy, so, I kind of know that tool, including creating formulas, pivot tables, macros, and so on. But, you know, Microsoft Excel has great calculations. It It's missing one feature. Most certainly, in the daily basis, use this beauty called, cell phone. And that cell phone will be completely inusable without the graphic user interface layer that you use every day. Right? So Microsoft Excel, well, doesn't have that. But Big Picture has so in order to, like, create a dependency, let me just find a task without any. I think that's the one, p p 35. Let's open that in Jira. Yeah. Well, linked work items, well, we've got only one. But in that case, each child also will create a hierarchy with feature. So let's use the GUI. So with your mouse, you drag end of the line, and that is how you create dependencies in Big Picture. Of course, right now, we've got a dependency in Jira. So, if we reload the page of that work item, you can see that we've got the link of blocks that was created by Big Picture, and it is indicated by this, green line. And, of course, this information scales because we've got over here, the null dependency that in this case is cross teams and cross, and cross sprints. But, as most certainly, you've already noticed, we've got three colors of dependencies, red, amber, and green. And, well, we've got, like, a lot of issues. So this information, of course, scales, and to do it, you need to open infobar. And from here, you can not only track your backlog, you can also track, your dependencies. And, well, of course, of course, this this view is, like, one to one related to the size of my screen. So currently, I'm sharing four k, and that is a 27 inch. But if you've got screen big enough let me simulate that. You can zoom it out and then zoom out the view of board like so so you can see we've got, like, cross increments kind of view. Right? But, you know, it's still 27 inch. So, well, let me zoom it in so you can see more details. And then the information from the infobar will be provided, from, the boxes, the the iterations that are, in the range that can fit, my screen. So then, we categorize dependencies well into four categories. So first of all, dependencies out of view. Right? So it's pretty much, I think, self explanatory. So dependencies that you cannot see because they are in the future or past iterations. Then correct dependencies, meaning green lines, so the dependencies that pretty much you don't need to worry about. And, of course, big picture, has got beautiful front end. Again, beautiful graphic user interface. So if you expand the set of, of these two tasks, by these three dots, you can focus your view on the source or on the target, so you don't really need to, like, search it by yourself, in the maze of tasks. Then dependencies at risk. So, the amber dependencies. Right? So this is the set of, of tasks. This is a pair of tasks that are scheduled in the same iteration, so please be careful. And then the dependencies that are incorrect, meaning at risk, meaning cred, So the dependency that will cause the failure of delivery. So we've got PP six scheduled in iteration 1.2. But as you can see, we've got and, well, let's, focus on the target. The dependent task is PP 14, but PP 14 can be delivered only after PP six is done. But it will be delivered in iteration 1.1. Of course, that will not happen, so we've got a little governance problem. We need to address that. Otherwise, we'll fail. Right? So then let's, let's go back to that view and collapse, that's spaghetti view of of dependencies. Right? And then, of course, team buffer. Right? So team gamma in, for example, iteration 1.1, as you can see, they're all overloaded. So they can deliver 13 story points, but we'll deliver 24. Right? So we've got eight 185% of, capacity allocation that is, of course, not going to happen. Things are, little, different when it comes to next iterations, so 1.2, because then, TeamGambma, will deliver 90 story points. But right now, they will deliver only 40, which gives us team utilization at the level of 44%. And, of course, from this level, you can clearly see what is the amount of buffer that you need to undertake. The best practice, of course, is more or less 20% of team capacity for a bug fixing process. And, of course, this 40, so this number would come from story point. Right? So, well, we've got, our story points in here, and then, we've got five story points when it comes to this issue. But, let me show you, one cool trick. Because if I change the value of story points like so, let's say 10, hit the check mark, go back to the picture. Five three points, 44% of capacity location change in three to one. Come on. Come on. You know? As I told you, live television. So, if anything goes wrong in here, you will see it. Come on, big picture. You know, people are watching the presentation. You know? It's like, well, let me reload the page because that may be maybe yeah. It's 10. Alright. So, no. Let's let's change it again. This time, let's say to eight, hit the enter, go back, and click on the picture. Like, 321. And the moment of tension, well, I think it's caused by my Internet speed or well, you need to trust me in that case. Well but, as you can see, the oh, no. Wait a second. That that was a wrong task. That's p p 100, Jesus Christ, 79. Tell you what. Seven. K? And then 179 changes to seven. That's correct. Big picture. K, man. Yeah. Seven, and then, aggregation change. So, again, bidirectional and life refreshment of data. In 90 story points, of course, that will be a team capacity. In order to edit that, we need to go to capacity planner. And in here, you can see that, every resource of course, that's 10 user Jira, so vast majority of resources are are are hived. But as you can see, our developers can work with a different, velocity. And, of course, you can calculate, you know, the team capacity based on the developer's capacity. All you need to do is to press this triangle and hit restore. So 87, that will be the current capacity of team gamma, that is calculated based on the capacity of the developers. Right? But that's, of course, not everything. When it comes to the board, the card views that you can see, of course, they represent Jira issues or work items. And, well, actually, the cherry on the top, in that case would be that tiny score that you can see in here. That is a priority score. So, if we open a priority score, of that plus, as you can see, we can choose three factors or, actually, four. Yeah. Business value, so let's give it three stars. And then estimated size, that would be l. And then time criticality, let's say medium, and the risk reduction will be high. So then Big Picture will automatically calculate weighted, shorted, job first factor in here. So, that comes, of course, from the module called priorities, which is Big Picture enterprise. But in that case, you can prioritize your backlog based on well, in that case, waited shorted job first, based on or done by graphic user interface. You don't need to script that. So, if you go to configuration, as you can see, we are using, that factor. Right? So business value plus time criticality and risk reduction altogether summed up and divided by estimated size. This is how our weighted sorted job first will be calculated. Of course, here, every, every metric will have a different value. And if you would like to, add a numeric custom field from Jira, you can do it as well. If you'd like to change it, of course, you can use, some predefined templates, or you can create your own. So however you'd like to prioritize your backlog, you can do it. But then after you specify all of these four factors, so risk reduction, then time criticality, then t shirt size, and the business value, as you can see, big picture will automatically give you the priority score, which in that case is weighted shortage of first. That you can see from the perspective of the board. So in that case, the team that is working, in a given iteration, they can see what the weighted, shorted job task is and deliver this task first as safe suggests or another priority score that, you will calculate. And then what you also can do is go to control agile road map and then add the priority score, in here. And then you can aggregate it with the aggregation of sum without parent. So the priority score, in that case, WSJF, will be summed up on the level of feature and on the level of epic, and then you can aggregate everything. You can sort everything by, that score. So you will see weighted, shorted tasks on the Yeah, Nicole. So tell us few words about scaling casually in general, agile possibilities of of big picture. Yes. Yeah. Really quickly. So we have still time for the the questions. But, indeed, you you showed, the the most interesting parts. We we control many other things, many other features, about big picture. But, again, for, the the more waterfall approach, or mixed hybrid metallurgies, the resource management that's always important in terms of planning. And finally, in agile environments, I often see people struggling with unexpected delays or tasks that are waiting for another teams for too long, putting their iteration or their sprints, at risk. Reasons are mainly that they focus on direct dependencies and have limited information about other teams, screens or iteration. So they usually lack time to dive deeper, and they miss indirect dependencies. So if you go for second sort of first level of dependency, or they miss the activities planned by other teams, pretty much of those issues are solved or at least are better managed, when we start using the big picture boards or PI planner as you showed it, thanks to a more visual approach across product, cross team views, along with the capability, of course, to filter and to focus on specific, part of the dependencies or on specific, work items indeed. So thank you very much, Lucas, for for the the demo here. That was really, really helpful, I I think, for everyone. Well well, Nicholas, you're most welcome. And, yeah, for all the audience that is listening to that demo, well, you can have a misleading opinion that big picture can be a complex tool. Tell you what, it's as complex as you need it to be. So, you know, big picture is very often compared to the Swiss army knife. You need a fork. You will have a fork. You need to have a rocket launcher. Big picture will be your rocket launcher, but for that, I advise you to cooperate with, Nicholas for the service of implementation. Yeah. Yeah. Usually, of course, that that's what we try to do, with all our customers is to, to start with the basics, and then we build more and more stuff. So we prioritize. We start with the the most basic needs. They start, using big picture. They understand the basics, and then we can go, go up with more more power, more, more value, for for for them. But from the beginning, the the the modules you showed really helps really bring value directly, for for their planning, short, midterm, and long term. Yeah. Pretty. much. You know, we've got a nice proverb in in Poland. So, in order to run, first of all, you will need to master the art of walking. Right? So True. that that's exactly the case. Right, everyone. Thank you, Nicholas. Thank you very much for for participating in this webinar. And, yeah, wish you have, wish you have a pleasant day. Thank you. Right. Cheers. Take care. Bye bye. Right.