 Yeah, some wire issue, okay. Let's see if we can work around with that. So, I am going to start with the very, very basic, you know, let's say, can we switch off the light? Let's say we are starting off a total new project, you know, for development or maintenance. You are coming up with a blank slate. The very first thing that Kanban talks about is, you know, you start with whatever you are doing, you know, whatever you are doing, you've been doing existing. So, let's say you have a development software maintenance process. So, you know, the bug comes in, you have a queue of bug, it goes through analysis, it goes through fixing, it goes through validation, then customer approval. So, what it says is you first try and visualize your process, you know, it could be in a physical board, it could be in a virtual board, you know, whichever way you are comfortable, you try and visualize that process. So, the capability first capability that we allow in law of Kanban principles that you see, you would see in our products with Kanban. Just to, as a quick introduction before we go, we have a company called Digite. You know, we build products for, you know, managing the entire application life cycle, which includes any sort of a methodology, you know, be it waterfall, iterative, RUP, we have a major leading product called Digite Enterprise, which is used by a lot of bigger IT organizations in India. So, if Kanban is a new product, which we are very focused on lean and Kanban, because we see that this is going to be the next wave of software development. A lot of companies are, you know, now trying, you know, more and more flexible and agile ways of working. And it is not, Kanban is not limited just to software. A lot of non-software, you know, development companies are also trying Kanban. You know, for example, we know of a bunch of HR folks who use Kanban board to do, to visualize their process and manage the work. So, sort of a Kanban has a much more larger universal appeal, you know, and that is where it is getting traction. So, this is a product shift Kanban. So, what I've just landed up is I just created a new blank board. Let's say you are starting off and you're trying to visualize your value stream. One of the capability we'd give you is you could go as complex in your value stream. It could be because a lot of teams have multiple team dependencies. So, you could actually, you have to visualize the entire process, including multiple teams in a single way. So, we give you a lot of capability to define your board. The very first thing that you can do is it's as simple. You can build the whole damn thing. Let's say you want to have a process which is in between. So, you will say analysis. We have a new platform that we've actually launched, SIFSync. Using that, we have integration with 10, 15 different tools. So, you can actually integrate. TFS is one of them, JIRA, Bugzilla, you know, all those tools you can go and integrate. So, tickets from flow in from there and move and then you take this workflow. So, basically, you can build, for example, I just added a stage. You could split a stage and, you know, let's say in multiple way, horizontal way, you can move a lane up. You could build a whole really complex workflow that you would like a ticket to take. But once you've done that, your first part is done. I'm not going to say this. Let's come back. The next thing that you would, you know, identify or build in the system is what are the type of work that you work with. You work with hot fixes, service patches, tickets, user story. So, you define your own type of work that you do. So, we allow you a capability which you can go and define your type of cards that you do. Each card is, you know, so typically Kanban, the way you would work with a physical board, you would put up a board and you would put stickies. So, cards are nothing but stickies, all, you know, they classify the work of, you know, type of work you do. So, you can color code them, define your own, you know, stuff that you would like to work with. And once you're done, you know, let's come back. You'll come back to work. So, now the work can flow in. It's very, very simple to use. And you'll see everything that I want to do, I will do it from this interface. You know, I have a new bug that someone will go and add. So, I could fill in a description, you know, a whole bunch of parameters. There's a priority classification. You can sort of classify it into various ways. If you're working with user story, you can rank code them. If you want, you can estimate them in points or hours or whichever way you would like. And if there is a due date associated, you can go and put a due date. Now, each board, you know, you can build, for each board, you can define a team who's going to have access to the board, who's going to work, you can define your team. I'm not going to give you the admin details, but you can define that in an enterprise where you have multiple boards and multiple different teams are working on it. Each team has only access to their own board that they look up to. The work will go in. Anyone, let's say you have a whole pipeline, anyone can simply, you know, take this up and move this card across. So, once the card has gone through the entire workflow, and it sits in the last lane, you know, that is sort of indicates the completion of work. So, you can go and archive it. Now, there are very simple metrics that Kanban captures. One is, obviously, you would like to capture how long typically it's taking me from point A, you know, where a customer gives a bug or raises a bug, till when what is actually delivered to the customer, how long typically it's thick. So, that is called as, you know, lead time or cycle time, you know, as you would refer. So, we'll let you capture the entire metric in a real time. So, at any point of time, you want to figure out, you know, what has happened to the ticket, you will be able to, you know, know it. I'm just going to move to an existing board that I have set up, you know, to display some of the features. Sure, you could do that if you would like. You know, there are a bunch of capabilities. I'm going to come one by one. So, what you see is a board. There are a whole bunch of cards that are there. There are a couple of yellow sticky which is showing that you are working on user stories of issues. There are pink cards, which are, you know, saying bugs. You see something in red. So, one of the things Kanban again says is that you have to limit your work in progress. You've been hearing the WIP limit, you know, from all these speakers that have been talking about. The whole key principle is that if you take up too many cards at a time, ultimately, you're going to lose productivity, quality, you know. Therefore, each ticket, you have to focus on it and you can set limits that, you know, let's say I have two developers or two support persons. So, at max, they can only work on two tickets or four tickets at a time. And you put this limit. So, if anyone has pulled too many tickets, you'll immediately get a red flag that, you know, something is wrong. So, the team is taking up too much, you know, on their plate and they will not be able to do it in a good quality way. So, we highlight that in a lot of visual indicators. You've been working on a card. There is some issue that you got stuck. You need some help. You can go and block a card. So, there's a feature where you just go and put an icon. You know, once you just hold on it, it'll show you that, you know, block a card. You can block it with a reason. And, you know, say, I mean, I have insufficient information to do it or XYZ. Anyone in the team will be able to see it's on hold, need some more input. It'll, you know, there is a notification built-in. So, everyone in the team will get notified that something is getting stuck. I need to come over and help me. So, therefore, this is also one of the same Kanban principle that identify a bottleneck and try and put together, you know, as a team and work to resolve that bottleneck. So, some of these principles, I'll keep talking. Now, once you're going through, you know, work, there are a couple of things that people would do. Now, if I'm working on a user story, I would probably like to split my, you know, story into sub-tasks, you know, so that I can at least assign, you know, different people who would work on that. One people can work on same card or there are multiple people's can, you know, can be assigned on this. I'm gonna show a quick task. So, if you, if you hold on, you know, this, you'll see that you can go and define, you know, sort of tasks for each card, okay? And once you're going through it, you can indicate the progress, you know, that sort of you will, you know, whether you're done or not done. Also, you can go and, you know, repay, you know, put, let's say, if you're, so some of these are very, very configurable. You've done through plugins, there are some teams who want to track time. There's something who don't want to track time. So, this is configurable. You can disable time tracking, but you can go and actually report actual hours or remaining hours as you would, the remaining hours are also used for burn down charts so that we generate. So, even scrum teams can use the tool and work with it. Now, once you've defined a whole set of tasks, there are a couple of other things that you would like to do. If you'd like to find out this ticket with that someone has been working, or who has, you want to come as a manager on a daily stand up and want to find out who's working on what, right? So, you could come and filter the entire board. This, you could have 100 team members, but you as a manager can come over and say, you know what, I'm going to see what is team member one working on and put this filter. So, you'll know that right now there are no cards assigned to him. There's something that is planned. He could go and pick up. There is something that he's finished, but right now he's not working on some of those. So, there are a whole bunch of filters that you can do. So, a lot of large team, you know, 200 people team also who use one board and they still very easily are able to manage the way around and figure out what to do what. So, you can filter on priority, you can filter on type. You could come over and say, you know, just show me all the critical bugs. So, the manager can just focus on those things. There are some special things that we build. You can always as a team come over and say, you know what, what are the things that we have to finish today or this week. So, you can filter on those and just focus and talk about only those cards. Similarly, by release, by iteration, if you work in multiple release, you could go and filter based on that. I'm just gonna go and reset. So, I have a whole bunch of bugs. Now, one of the other things that you could do is if you want to find out more detail, there are some cool things that we build. You can just scroll over it. You don't have to go anywhere. So, you'll notice that I've not gone beyond this board to see anything else, as of now. There are a couple of features which are behind the door, but as of now, you could manage your work from one single board. A lot of teams have also put touch screens in their bay. So, they could just display this Kanban board and just come and swipe the card. So, it is supported on touch devices, including iPad or any of these. So, they could just go, there's one team board. They could just swipe and say, I'm done. So, typically a lot of stand-ups also happen on a board where people can just hurl up and say, you know what, I'm done. They can just move it and mark it done. There are a couple of other features which we showed. Let me just show one quick thing. If you come over and you want to find out how long this card has been in progress, you could go and flip this card and it'll show you the entire log, how, when was it added to the detailed view. So, it could tell you that this card was raised or this ticket was raised by a customer on so-and-so date. It was sitting there for, let's say, 10 hours. Then it moved to ready where it waited for 21 hours. Then it went in progress or someone jumped the queue directly and said, you know, this is done, X, Y, Z. So, the entire detailed metric for your value stream, you'll get it right here. So, at any point in time, you will know how long something has been in progress, something is, you know, nothing more. There is also, for a lot of scrum teams, you would find this interesting that you could take up a bigger card and slice it into very smaller, you know, hierarchical, so you can build the whole decomposition right here. So, if you attended Jeff Payton's story mapping session, so you can actually take a big, you know, epic or if you work with big features, you can break it down into multiple ways and get a visual hierarchy of, you know, what is, you know, how much things are complete. So, you could see you have 25% of this epic done, whereas it has a whole bunch of stories, you know, and child cards. Now, these could also, if you're working with multiple boards. So, there are times when you have three teams working on a release. You could have three different boards at each of your team level. You have independent team members, but there are some interdependency that you want to manage. So, you can, you know, build a system here where you can have one big card and smaller cards in different, different boards. You'll still get the roll-up and, you know, you'll figure out that, you know, how are things working. You build your own structure. We are not putting any structure you define. If you can have 10-level structure, you can have three-level structure, you define your own thing. You know, and even the labels, we are not restricting. We don't say, you know, you call epic. Some call epic, some call theme, some call, you know, a big feature, you know, anything, anything you want to call, you call it. I'm just going to go quickly. I think we are almost done with the time. Absolutely. You can. So, if you see, if you notice that when I've added a card, you know, I have an option to choose the backlog or I can just choose to just push on the board. So, I have also my backlog, which I can go to, you know. Absolutely. You can go and do a planning. You have a backlog where you have all the list of backlog items. You can go do filtering and, you know, let's say do some smart building, show me all the card which are ranked greater than nine and we'll go and search and get you immediately. You can also do a bit of release planning and we have taken a little different approach for releases. You could, once you go and, you know, you have to do a release planning, let me show a different board. So, there's another configuration of a board where you have a sprint backlog which you can line up. You have, you know, prioritization, execution and, you know, then done. So, each team can build their own, you know, sort of lanes and sub lanes and stuff. So, there's one feature which I can show you. It's a release planning. When you can go, simply select your scope. Once you edit it, this will show you the entire backlog and you can go and push and put things into the release and based on the capacity of the release, it will go start filling up. The capacity will start filling up. And, you know, as you start, you know, doing the cards, the progress indicator will also show up. So, right in the interface, you can do release planning. From this, you can even break it down and do a sprint planning. But these are all configurable. You choose the level of, you know, scrum adoption you are doing or kanman adoption you are doing. Yeah, absolutely, absolutely, absolutely. So, the progress is actually based on the board. So, you're just, this is a planning view where you're just putting the scope. So, here you do a plan and then you can go to the board and pull from the release backlog and put it on the board. So, that is sort of, absolutely, absolutely. And once you're, you know, sort of done the planning, you start executing. Some of you will report remaining hours on task and based on that, you can even get a burn down chart. Yeah, absolutely. So, these are iterations and then you can go and pick up a chart and show you a burn down chart. So, both burn down, burn up, if you've been, you know, capturing effort that way. And just go over to come some of the kanman metrics. So, we support a lot, we give a lot of, you know, default kanman metrics. One of the key metrics, which is similar to, let's say a burn down in, in scrum is sort of cumulative flow diagram. So, basically you track, in all possibility, you should have an even line. But if you see there are too many spikes in between a lane, that is where your capacity is not up to the mark. There's something which are getting piled up in dev lane or down. So, a lot of predictions can be done. You can even filter this board based on, you know, a lot of type of card, select lane, unselect lane. You can also track lead time, cycle time, as I was saying. As, so, a lot of team, one of the things that you will see is that you don't have to work on any of these metrics. As you're working it, we are capturing time at each stage of your workflow. And based on that, we can tell you the, you know, average time of typical card took. And you can even slice it and say, you know what, show me average time that a user story has taken or user story of size XL took. You know, based on that, you can get a whole bunch of metric put in. We also support a lot of control charts. So, you can get a control chart, which can say, based on the three sigma limit, how many cards have exceeded, gone beyond, you know, the cycle time, beyond three sigma limit and, you know, not. And a bunch of other charts. I mean, I'm not going to go into too detail. Just quickly switch back. This also has featured a lot of other notifications and inbox each team member can come and see his inbox for the cards he has signed up for. And it is due to deliver. There are dashboards that you can see for various ways each guy can come and personalize his dashboards. One other thing that I'm going to show, something we are working on and any questions on this so far, anything specific that you guys are looking for. So, in a way, it covers the entire Kanban workflow and it's fairly, very simple. You can adopt it anything. We have seen people using personal Kanban, it's a big wave, where in, you know, to-do is something which is a little old way because you have a whole bunch and, you know, a lot of time you'll keep looking at the to-do and not do. So, it says that, you know, that is what multitasking sort of becomes. And Kanban says, if you just simply say, you know, this is my to-do, this is in progress done and pick up one thing at a time, the chances of finishing that are much higher than actually when you keep looking at your backlog. So, a lot of people use personal Kanban, there are books on personal Kanban, Jim Benson, one of the thought leader is working on personal Kanban. So, he spirits a lot of these personal Kanban. We have seen in schools, at least not here in US, they use Kanban board and, you know, put the whole homework for kids and say, you know what, this is your list of homework that you'd go do and, you know, as they do it, they finish up. So, the whole feel of moving a card also, you know, is sort of a lot of big productivity booster. So, every time they go and move a card, they say, you know, I'm done. And so, it'll let you slice in a small way or ticket, which otherwise just to update status in some tool is boring. So, sort of, it's a different way, you know, that is picking up. Apart from this, I'm just gonna show you one thing that we're working on. It is more of a sort of, it's still in progress, but we thought in this demo we can probably show. We're working on a whole simulation model where we can simulate, if you're given, this is your backlog. This is the speed of your delivery. How long will it take to finish off your entire backlog? So, for example, I'm just gonna show you that I have, let's say, three resources. I have one developer, one designer, one tester, and let's say I have 30 user story. I could run this simulation and it'll actually take, and I only show you there's a lane that you can go and set up. Just give me a minute. It'll actually simulate how the things will go and pile up. It'll show you the burn down chart right live, how the whole project will go for, let's say, six months from now, and tell you that it'll take you 17, 63 days to be able to finish at the current pace you're doing. So then you can go and now plan a little more and say, you know what, let me try adding three more developers, because if you see here, if you notice, the coding lane was getting choked because we had just one developer. He's taking a lot longer than the tester to fix, but the tester is sitting most of the time idle, so there was a utilization chart that we were showing. Now we're gonna go change it, and I say, you know what, I will put in 12 developers and save it, and I could come and again run the simulation. So it is telling me now from 17, 63 days, you can finish this whole thing in 241 days if you have 10 developers. So you can define your optimum size, figure out using some of this simulation, and it'll help you to predict a lot better than what you do. There's a whole lot of capability that we're building in this. We are saying, you could also say, you know, things are not ideal. You will have user stories, but once you're going through, you will get bugs. So for any lane, you know, I could go and say what? I can go and define, you know, saying that I have a primary source which is developer, but as soon as the tester gets free, we usually go and put him on testing. So you can even simulate that scenario and go. There are a couple of scenarios that you can model that saying, there are 50% probability that bugs will get injected once tested is tested. So it could even simulate and say, you know what? Once 30 stories are done, let's inject some bugs for 50% of the time and then simulate and then tell you the real time. So this is something we are working on with a lot of early customers. So it's hard to show. So we're trying to build a lot of other scenarios. If you guys have any difficult scenario in mind, drop us an email, we'll be happy to solve that. All right, that is what we have to show. Any questions? You guys are doing Kanban. Scrum, okay. Same company, which company is it? Let's go, okay, yeah. There's more to your expertise. Absolutely, absolutely, absolutely. So if you go online, swiftkanban.com, there's a free trial sign up. It's on the web. You don't need to ask anyone. It'll just go and get started for 30 days. If you need an extension. Do you need an option to run as well as? No, this is not there. This is still we are working on it. Tf, we can look at that. We can look at that. That's a separate piece. We have to see how we enable it for you. Jira demo is available immediately. TFS works with the whole integration plugin manager that we have built. So we're still trying to put things. But we can run it for a pilot for sure. Any other questions? All right, thank you. Thanks for your time. Thank you.