 So, good afternoon everyone though we have been using Confluence and Jira from a couple of months today we will be talking about project management using Jira and Confluence and we will look into those details which we have not discovered so far or some of the teams are using some of the features of Confluence and Jira but it is not being used to its full potential. So, let us begin with the content we will be talking about a brief recap of Confluence and Jira what they are and what all features they have and then we will cover project management using Jira. So, to begin with what is Confluence? So, I may not need to repeat it again as all of our teams have been using Confluence since a very long time. So, I will just read it out Confluence is basically a team collaboration tool built for storing, sharing and working on any kind of document. These are some of the companies which have been using Confluence and Jira worldwide. So, Confluence structures are document in a very better way. So, before Confluence you can see there are n number of documents there of different types spread all across your organization but with Confluence you can organize them with predefined or custom structures. I think since we have been using Confluence we know what a page is so and what are spaces. So, let us consider this room as a space and these elements as its pages each element has its own property. So, in Confluence we every team has a space and in each space there are n number of different type of documents fulfilling a its own purpose right like we have a document for meeting notes, we have reports, we have presentation slides like that. Space and page have are of different types I will not go into much of the details of these as we have been using Confluence since a long time. Some of the Confluence use cases this is to make you aware about aware about how it is being used across the organizations in the outside world. So, some of the companies or the organizations use it for technical documentation for drafting release notes and releasing. For example, if there is a product and they want to release its notes its documentation they use Confluence as a wiki. So, it is being used in that way for some of the companies say for example, who has a help desk they use Confluence to share their how to articles their troubleshooting articles. So, it is being used in that way as well. It is also being used by the software teams for product requirements making documents such as product requirements SRS, BRDs release planning documents customer interview pages and for agile teams sprint retrospectives and all those documents related to agile projects. So, I will skip this slide this is one of the examples of drafting a requirement specification document in Confluence. At our place, we have been using Confluence for firstly for sharing all the documents since the inception of project and VLI at IIT Bombay. We have collated and uploaded all the documents in a space named national virtual library of India. This space the access to this space is typically with all the senior managers managers and all the associated members with project NVLI. It contains all the MOU letters presentation progress reports etcetera. The other space is NVLI at IIT B. Now, this is again to facilitate cross-team collaboration and all those teams which are in some way or the other associated with NVLI project. All those teams have a page by their own name under which I think most of the teams have been creating their respective timelines and activity and sub activity list so far. 4 to 5 teams have created. So, only a few are remaining. Another such space is named DBP teams at IIT B. So, this space includes all those teams which are not associated with NVLI, but are part of DBP teams. And then there comes private team spaces. So, each team has their own space with their respective name. Then there comes another space which is named DBP staff worksheet. So, here we have created predefined templates to log their daily work. Now, our recommendation is that you must decide a time when you start working on a new fresh day. So, let us say at 11 am or something. So, there you plan what all activities you are going to do for the rest of the day and what you did yesterday and then problems faced if any. So, you can simply write a to-do list in this template and then you can proceed with your working. Confluence has certain features like versioning. Now, what we have noticed over the period of last 4, 5 months is that most of the teams have been using confluence, but they have been using it merely for uploading documents. So, but that is not it is all about. Its main functionality is to create automated versions of the documents. So, what we would suggest is that any document that you create you must create it in the form of a page in confluence. So, however iteration it may go it will always create an automatic version and you can always you know compare two versions if you want to backtrack to a previous version a previous draft of it you can simultaneously like multiple users can simultaneously work on a document. So, that way it is very helpful here in this we yes, yes we have to simply create a page and write text there every time we save it creates a version automatically. No there is a create button on the menu bar yeah I will show how to do it live. So, you can see you can it when a document gets created automatic version it gets automatic versions you can delete a particular version you can even restore a particular version and you can compare two versions. Next is sorry plugins and macros. So, now macros I would say are the heart of confluence when you create a page I will just show you yeah sir we have restricted the delete permissions of all the pages. So, you can only create and move because in order to avoid accidental deletion we have done so. Mum the spaces which are a private spaces of each respective team they have all the permissions they can add they can delete they can do whatever. But the spaces where multiple teams are there where some important documents are there there we have restricted. So, a page can be created by simply clicking on this create button if you want to use a predefined template of a page you can click on these three dots and here you get a whole lot of predefined templates like meeting nodes product requirements etcetera. Now, for example, I give a title test document draft one I save it I again click on edit draft two draft three I again save it now I just have to go and see the page history. You can see the version when I first saved it it created a version when I again saved it after a few additions it again see now I can compare those versions I can even backtrack to the first version I have this line was added appears highlighted in a green color. So, it appears like this. So, what happens is I will show you a document of the Envili cloud setup project server specification and required items. You can create a document in such a way wherein you can provide some metadata what we call like who is the author what is the status of the document and what is the version status is helpful when a document goes through multiple iterations over the time. So, initially a document may be in draft phase a document may be in review phase for example, if it is a report and if it has to be reviewed by the hierarchy by the senior people in the hierarchy then it may be in the in review process. So, this status can be changed and lastly you can mark it as freeze then the document is ready. Now as per our slides our next thing was macro. So, I said that macros are the heart of confluence. So, apart from the basic functionality of creating spaces and pages and all and different types of pages there are whole lot of other options. For example, the timeline what you create using a roadmap planner macro. So, it is one of those macros you can create spreadsheets using macro you can mark a status of a document using status as a macro. So, these are some of the macros I will come back to my slides. So, in any of the document or the page that you have created in confluence just click on edit and then you can see a plus sign over here. Just scroll down to the bottom and you will see other macros as an option you will get a so this is how we create a macro. So, there are other very useful macros as well like you can create diagrams block diagrams etcetera using gliffy. Sometimes what happens is when you in your organization there are repeated documents and there is some part of the text which keeps on repeating. So, you do not want to type it again and again for example, template that we created for report. So, some part heading header or footer keeps repeating. So, there are macros named excerpt that can help us reusing that content. Then I skip the macro pardon me yes, yes. Basically, whichever content gets repeated we save it in a form of a excerpt and then we use then we call that excerpt in that document again. Yes, yes, yes every time it can be. Then we can label documents. So, we can categorize documents in that way and then there is a macro named label list. So, I will just show you see when we preview although right now I have just added it at some location not a proper location. But this is how we can when we label all the documents then we can get a label list. So, it becomes very much easier to navigate those documents different kinds of documents like say in operations lab. So, it must be having n number of different kind of documents. So, you can label those documents with their category and you can have a list of those documents here as a macro. Again labeling those documents and even if you do not label it confluence has got a very good search feature wherein you can quick search just by typing a few initial letters of your of the name of your document and it even search within the text of your document. So, either it may be a word document or text a page whatever it may be. Then there is another very good feature through which you can share knowledge among your teams that is block functionality in confluence. Now our team have had been publishing blocks in the space named DBP at IITB. I think none of you have read those blocks so far, but we have been we will be publishing more of such blocks and we would even appreciate if some other teams come up with their own blocks and their own topics on which they want to share knowledge with all the DBP team members. I will show you where they are. Yes, yes, yes, we will be doing that. So, this is how a block appears. On the side bar we can see an option named block. If we click here we will get into all those blocks which have been published so far and on the right we can get their respective content. So, I will be keep swapping live demo and the slides in order to get a better feel of that. This is how they appear. You can even like comment not subscribe only like and comment here. So, you can share your own thoughts on the blocks. So, initially what you can do is you can start with writing blocks in your private team spaces and later on you can move it to the team which has access to all the teams. We as a project coordination team would recommend that you create documents as in the form of pages in Confluence itself. You can skip a few there are exceptions like creating these slides would not have been possible in a better way in Confluence as we need to present it and those functionalities are that tool is not meant for that, but you can always upload it in the form of a file. But for rest of the documents like creating excel sheets any other documents that you can create using that you can collaboratively work on a document multiple users can work. And though I have covered a very few macros but I would recommend that you please explore other such macros even if some macros are not listed there and you may find it on Google that these macros are also available then we will ask our CISAD teams or our JIRA and Confluence administration team to configure those respective macros for you to use. So, if there are no further questions then I can move on to JIRA. So, JIRA is basically a project tracking and project management tool it is developed by a company named Atlassians I will skip these slides. So, how it helps? It helps in better planning in better tracking, releasing and reporting some of its benefits are that it is massively scalable and it has n number of add-ons like we had macros in Confluence here we have so many number of add-ons which adds to the functionality of JIRA some of them are big picture JIRA portfolio agile tempo time sheets etcetera though we have not we are not using all of these. So, what a JIRA project is? A JIRA project is a collection of issues and is defined according to your organization's requirement. So, for example, we have different teams fulfilling serving different purposes. So, we have JIRA projects for all other teams. Now, we have a combination of teams we have some teams which are specifically into software development while other teams are non-technical teams or some business teams. So, a JIRA project can be for both kind of teams or any kind of teams whichever domain they may be serving in like they may be HR teams, operation teams or in case of software they may be a development team they may be a website enhancement team etcetera. Now, what an issue is this term sounds a bit ambiguous to many of those who are very new to JIRA. So, an issue in the simplest terms is a unit of work to be done. So, you can also swap it with a word task. So, an issue is can be also called a task by default and it is a unit of work to be done. For example, creating a purchase order is an issue book the conference room for meeting is an issue develop the mock up for home page of a website is an issue for a software development team. Now, an issue is a unit of work to be done and it can be it can have different types like a work to be done is can be a task or it can be a sub-task. So, for all the teams which are not software teams we would recommend that they use only these two types to start with while creating an issue in JIRA. So, their issue will either be a task or a sub-task. For other teams let us say for example, Shweta Mamm's team is using agile practices. So, there the issue can be an epic it can be a story it can be a task it can be a sub-task it can be a bug etcetera. Next comes an issue workflow. Now, let us understand it in a very you know real life terms whenever we do a task whenever we get a task for say from Vataxar if a PR team gets a task firstly they get a task then they understand the task then they actually do something to in order to complete the task and at the last the task gets completed right. So, it transitions over different status initially it is in to do state then it gets into in progress and then it ends finally as a done right. So, every project has a predefined workflow in order to complete their tasks. This workflow can always be changed for example, there may be for example, in operations lab there may be some additional steps like sending file to DRMM or getting file to be signed or it has to be reviewed. So, we can identify a proper term term for that. So, that way we can set a task life cycle which is named as workflow in 0. So, any questions so far I would like to know let it be an interactive session feel free to ask I will try my best to answer all your queries if not right now after the session I will try to fine yeah yeah. So, I am coming in that. So, these were some of the basics now let us understand what a JIRA issue is again what all fields are required to create an issue then we will see a live demonstration of how to create an issue. So, first thing a point to remember is that whenever we create an issue its title or the summary must be well defined sometimes what happens what happen is that user create an issue, but they write its summary in such a way that it is very vague it is very ambiguous. For example, write one issue is named simply a meeting or simply send attendance now what you can figure it out only by reading send attendance. So, these are some bad examples and some good examples would be that send list of staff attendance to IRCC for the month of November 2006 now you can properly make some sense out of the summary of this issue. Another one is organized meeting with Envelay cloud setup team to discuss the status of stage 1 and decide activity timelines of stage 2 and stage 3. So, to summarize you must your issue title or summary must be well defined. These are some of the JIRA issue fields which are very much important in order to create a proper issue and later on to generate some meaningful reports out of these issues. So, whenever we create an issue this let me show you live again like we create page in confluence by using the create button the same way in JIRA using the create button we can create issues. For example, I would like to create an issue for the project Envelay cloud setup now you as a user will when you will open this list you will get to see only those projects to which you are associated with. So, first you have to choose your respective project then your issue type. So, in your case only two options will appear one task and another is sub task then you have to write your issue title here in the summary field all those fields which are marked with the red asterisk sign are mandatory fields in order to create an issue this is self-explanatory then you can skip to write detailed description or you can you can even write it later. Reporter is the one to whom who is creating the issue basically and the assignee is the one whom you want to work on that issue. Reporter and assignee can be the same person also for example, I will choose myself as the assignee then comes the component sometimes what happens is that in a team there are work happening in multiple domains for example, I would like to put it in a way like workshop team. Now, workshop team has one team which organizes workshop which plans workshop and the another team is the software team which develops a platform to facilitate that workshop. Now, all those issues say for example, over the time of one year you have created 2000 issues now if you want to filter those issues how you will do. So, you can create two components to logically group your issues you can create one for workshop software team one for workshop team we can name it in a more better way. So, component field is for logically grouping those issues then comes the original estimate. Now, this is very much important that you all must fill while creating an issue. Now, this is the time required to complete an issue yeah then comes the start date and end date. Now, so this is again very important and in order to create meaningful reports you have to you must put a start date and an end date which you think an issue will take to complete. Then there are two other fields that we will discuss in the upcoming slides one is risk probability and another is risk consequence. Though I will be sharing these slides but you can always note down whatever you feel is important. So, I will reiterate that start date and date a proper summary an assignee original estimate these fields are very very much important in order to create good issues and to generate meaningful reports later on. So, this is how an issue looks like in JIRA on the top you can see there is a number NVLI 63. So, this is basically a unique key every time a issue is created it gets an automatic generated unique identifier. So, this is the 63rd issue created in the project NVLI this NVLI is a key for the project NVLI. Now, as I said the title of then of the issue should be meaningful. So, here I want to make multiple selections so that I can make annotations for different contents in the image. So, this is one functionality of the Drupal NVLI website that was ongoing few months back. In the details section you can see the detail of your issue for example, what type of issue it is. So, here in your case it will appear either task or a sub task. You can see the status of your issue whether it is just been created and has a status of to do or it is in progress or it is done when it is done its resolution is also set to done. You can also label issues like you can label documents in confluence same way. If there are any sub tasks of that particular issue they appear in the section of sub tasks here, wherein the summary of the sub task whom it is assigned to and what is its status. Here in the people in the people tab sorry not tab people section you can see who is the assignee who is the reporter. You can choose to be a watcher of that particular issue if you would like to receive email notifications for any changes in that issue. There are dates so whenever an issue is created that date appears over here when it is updated it appears over here start date and date is the resolved date both are the same work log. So, it is the same basically in the slide which I display I will just show yes yes I will show you this is one such workflow in progress and done like that. So, it can again be redefined, but the recommended practice is that when you initially create a project when you set up a project with the help of the admin teams only that time you define a standard workflow it should not change once the issue gets when once you start working on that project. So, these are some of the things which have to be no these are the default this is the default workflow yes yes. So, then comes the time tracking in the next slide was the time tracking thing. So, when while creating an issue when we fill in the original estimate that appears over here that estimated time is 1 week 1 day 5 hours remaining time when we first create the issue it is the same as the estimated time when the user start logging their work then it gets changed when then the log time and remaining time automatically adjusts with respect to each other. Sub tasks again are appearing over here you can see this is the main task and these are the sub tasks in order to complete that task all have been done here you can see comments on any on that issue work log I will be explaining it and any activity done so far with respect to this issue. So, it can be reopened if required no dropping means what you can you are changing the state okay. So, it will be on the records you are not deleting it you may flag it with something that yeah or irrelevant or so your efforts are not being wasted actually you can comment on that issue and you can put it yeah I will show hi in your scenario it must be happening yeah very frequently yeah. So, you can see a comment button near the edit button simply you have to click on this comment and that comments get added below the issue or we can create a separate field okay we will call it a flag and yeah yeah and we can write. So, later on if you would like to search all your irrelevant issues, but you had spent some time on it you can search them using that filter as a that field as a filter flag yes yes. So, these were some of the issue fields and this is how typically an issue looks like one another field which appears over here is development this is for the software teams. So, there is a git integration available in JIRA. So, all those teams which are whenever they check in their code in git they simply have to take the issue key and mention that in their commit message when they do so it automatically gets appears over here in that issue in JIRA. Git hub yeah the one which is hosted outside okay. So, even that is possible since we had we had not received any such requirement as of now. So, we have not configured it it can be configured for local git as well. So, this is how when you click on the commits or the branch it pops up and you can see who was the author, what was the message, date of the commit files etc. So, any questions so far yeah sure. It is created whatever options you can do with the issue are only on these two buttons one is more okay and the another is edit edit is basically to edit some more fields more is to do some more tasks with respect to that issue okay. Now, you would like to link an issue with some another issue. So, you simply have to click on link now in order to link it you have seen a lot of options has to be done after is blocked by is cloned by is dependent on depends on okay. So, this is how you can link an issue. So, any more questions yeah ma'am okay yeah. So, yeah. So, in that case if you have like if your project requirement is such that there are multiple teams involved then we can configure in it in such a way that both the team users will be associated with your Jira project and you can then change the sign. Every issue has an activity log right wherein whatever change it goes through gets listed. So, if say for one month your team members are working fine it is on the records if after a month another team is working that is also on the records. So, it can be done. Now, even if he does not say if a sign he gets changed it it gets recorded in the form of a log there but you can always comment that changing the sign he yes yes. So, what we will do is we will we will set up a common project for your team okay yes yes. I know maybe we can we can what we can do is we can after the session we can work around with your requirements or our team will visit to each team in person and we will find out because each team will have different requirements yeah. So, we will visit each team and then we will get your requirements and then we will customize the Jira projects or set up the Jira project or Confluence space the way it fulfills your requirement. Yeah sure. So, now we will look at Jira Confluence usage flow. So, basically this flow we have identified we have been we had been using it with the vendors all as well. This is the flow that we recommend to the NVLI partners as well although you have always the liberty to modify this flow. But as of now this is our recommendation that you must follow this workflow to begin with. Hello sir. So, initially what happens is you create documents in the form of pages in Confluence okay. The document goes through several iterations that you can always see in the form of versions okay. Once the documents is freeze or it is frozen you also conducts some meeting okay. You organize meeting your intra team meetings. When you conduct a meeting you come up with meeting notes right. So, we recommend that you create those meeting notes in Confluence using the predefined template of meeting notes okay. For example for the project NVLI cloud setup we had conducted two meetings and we had created two meeting notes. So, when you draft meeting notes using the predefined template you can write the discussion items over here okay. And based on these discussion items you can figure out the action items to be done based on these meeting notes. You can simply write what the action item is you can assign it to a user using the at mentions in Confluence and you can write a due date okay. Once the task has been done you can simply put a check mark. So, this is a lightweight project management but in order to track the individual progress of each issue the time tracking for that we will have to use JIRA. So, I will again come back to our recommended usage flow. Once we are done with creating meeting notes in Confluence then we create activity timelines based on these meeting notes okay. And we also create a detailed activity and sub activity list in Confluence based on these meeting notes. Then you have to create JIRA issues from Confluence. We will go through all these steps one by one in detail. As of now I am just reading out these steps. Then you edit issue fields in JIRA, you update issue status regularly, you get and receive issue event notification. Then being a manager, you manage programs using big picture add on in JIRA. You also use dashboard and gadgets to track your project progress and at last you generate meaningful reports. So, let us see step one. So, create yeah yes sir yes sir yes sir yes sir let me tell you from my own experience that it takes some time for you and you have to remember to get used to it is not as if you do this once and then so you have to dirty your hands. So, two important things firstly what process you have outlined is the one process to which you can actually get your timelines and so on. It is entirely possible that you yourself write down the activities. So, there are no meeting no meeting nothing but you can actually create those independent. You can create them directly in here. This one easy way of doing things where the activities flow out of the meeting. Usually in the agile methodology of programming the software requirements specification themselves emerge in this fashion and that is the reason why saying that the requirements will emerge through discussions. So, it is quite possible that for a small project or even for a large project just the team leader sit down and identify some activity. You always add more activities and always add more activity. It is possible to create that is one important. The second important point is that the entire mechanism of activities depends heavily on each individual team member updating daily activities. Now, this is something that we are not used to do. You probably update things once in a week or something like that. Once you get used to it you will find that you may not spend more than five minutes at the end of the day to say this is done this is not done. In fact, have you described the five minute standing meeting that you have done earlier? Yes. So, that could be a good point to do in the morning where these minutes, these meetings are actually not this long discussion meeting like this. These are actually standing meetings because actually stand not permitted to sit because if you sit the five minute meeting will extend to 20 minutes. There is no cup of tea and no naan. It is a five minute very crisp meeting. What was done yesterday? So, we don't play what difficulties I face. That's it. Exactly the same way at the end of the day each individual person must spend five minutes in updating the. If this is not done the whole mechanism of project management will fall. Whether project management depends upon whether inputs are coming every day or the progress made or not made or whatever. We are not setting this up as any kind of policing activity. We are setting this up to improve our whole productivity, collective, immediately your productivity will improve. That's all I wanted to stress. It will take some time for everyone to get used to it. But I want every member except those who are at the lowest level in the attendance or someone who cannot figure out how to type in their thing. Although they should also be trained to write something if they have any task of part of the course. But otherwise everybody has to follow this. Any other issue that has come up through your discussions so far or you are still going through that? Still be clarified. Yeah. So, the point is that zero and confidence have been used extensively for software project management. RedMind is a general project management tool which our partner CDAC uses. But RedMind components, I mean reports, etc. can be actually imported in Jira. So, even for nowadays it's widely used for non-software projects as well. And when we had updated the Jira version, the hosted version of Jira, now when you create a new project, it basically gives you two categories. Either your project is a software kind of a project or it's a business project. So, we have all kinds of teams. So, we can actually utilize it to its maximum potential. I'm looking forward to team not software project management. Yes. That would be done by a few teams which are involved in software development. And they can actually create a parallel project for software development. But all of them must participate in the general business project which deals with the timelines of activities in companies and so on. And it is a general project management that they're working on. So, please try to assimilate as much as possible. I know it to be difficult because we've never done that before. We rarely write. We don't write our diaries here. We are saying everybody must write a diary entry every day. So, assimilate as much time as possible. And then people say, I forgot. So, this activity has to be treated like your dinner or evening. You don't forget to have either. So, you cannot have your evening tea unless you have written one line or two lines. It's as important as that. You don't have to eat at night. So, if there is no entry, there is no dinner. So, that is the discipline that we learn. I would like to remind that as part of the project proposal, we are needed to share a live dashboard of your ongoing projects as well as reports. So, until and unless we do not make an entry against an issue. Yeah. And I will not be surprised if he calls me someday and tells me that your workshop team, for example, is goofing up certain activities that are not yet done. It is to that level where we expose ourselves and others. Big brother will be watching. The whole idea is to make the process transcribed. So, it is not the purpose. It is not to fire anything or something, but to get used to increase that. All right. I will leave it to you. Thank you, sir. So, now we will be seeing the recommended usage flow and detail step by step. So, step one was to create, is to create requirements specification or other documents as pages and confluence. As Professor Fatuk said that a team may not be conducting internal team meetings to find out the requirements or to find out the activities and sub activities. So, based on the nature of your team, you can proceed. So, organize internal team meetings. Then you can draft and share those meeting notes and confluence. You can identify action items and assign them to a user with a due date. And this is what we call as lightweight project management. This can be done using confluence. For example, last week when we conducted a training session in CEDAC Pune, we came up with these notes. And then based on these notes and the discussions we did there, we came up with these action items. Like they need to create a timeline in confluence and a list of sub activities. So, not even like not only our internal teams has to do this, even the EnVyLive partners have to submit a timeline of next 2.5 years. This is a mandate by the ministry. So, this is how we identify action items. These all tasks are dependent on meme. These action items are dependent on CEDAC users. These are again the same slides. The step third is create timelines based on these meeting notes. So, timelines using the plugin roadmap planner can be created. And you, I think most of you have worked on this macro. So, you know how it appears. This is how a timeline appears. Next is creating a detailed activity and sub activity list based on this timeline. Your timeline may not have a detailed list of activities. It may only have goals in very brief form. So, we recommend that you create an activity and sub activity list in order to complete the tasks listed in your timeline. So, again activity and sub activity list can be simply created as a confluence page, wherein you can list all the tasks and sub tasks. This is one such example of a sub activity and activity list. For example, we had conducted a meeting, we have for NV like cloud setup, we had identified action items, we had created meeting notes, we had created a timeline, then we came up with a activity and sub activity list. Now, how, why it is useful that we will get to know in the slides ahead. Next step is create JIRA issues from confluence. And you can read the point number 2 that how simple it is. It is as simple as eating a vada pao. Why it is so simple is, which wherever in whatever form the text is in confluence, you have to simply drag and select it. As soon as you do it, it pops up you with two options. Either you create a issue or you write an inline comment. I will show you how. Say for example, I want to create this issue. I will simply select it. I will wait and I get two options. Either I add an inline comment over here or I create a JIRA issue. Now, whichever project to which I am associated with, I will get all those access. I will select only the basic fields over here. I will click on create and the issue gets created. Further, you can go in JIRA. You can open that issue and you can click on edit and fill in the rest of the fields. So, you can create issues from confluence in JIRA directly from the timeline itself or from the activity and sub activity list, the detailed list that we created. So, it becomes too much very simple. This is how you get to see all the issues in your project using issue navigator in JIRA. This is the issue navigator. This is the issue navigator. Next step is to edit and update issue fields in JIRA. So, again all those fields that we discussed in the previous slides, the important fields, you have to fill in those fields which includes original and remaining time estimate field, start date and end date. These are very much very very important in order to create meaningful reports. This is how you can edit an issue field. You can simply click on edit button and you get to see all the fields, start date, end date, original estimate, reporter, assignee, components. So, if you are creating an issue from confluence to begin with. So, that time you will get to fill in only a project summary that is all, but you have to fill in rest of the fields. Then again as the issue or the task will progress, the assignee in particular will have to update its status. Initially it will be to do, then the assignee's responsibility to change it to in progress when he or she actually are working on that issue. And lastly when it is done, when the user has logged the work against that issue, then they will mark it as resolved or done. So, then a user or the assignee to which the issue is being assigned, he or she. Actually we have not worked with such a requirement, so maybe we will have to. Confluence that action is there, but we create action when we assign it. Yes. And once the action is completed, we put a tick. Yes. Then that is completed. Yes. So, like here we can create an issue with that action. So, can it connect like when we put a tick here, then automatically it changes the status to done? Probably not. And we have not actually this use case we have not explored. So, maybe we can try and then we can see what the result is. Yes. Yes. It is a single sign on. So, yes, yes. Right. Right, right. And it may be even there may be more such transitions. Yeah. Right. The status can be many. It cannot be only start and done. So, good point. So, next step is log the work against each issue. Now, being a user of JIRA and being a signee, it is very much important as Professor Fatak also said that you need to log your work at the end of the day. So, for example, if a task in JIRA has an estimate of 2 to 3 days. So, we would recommend that before marking it as done, you must log the work against each issue. How this logging of work happens is. So, as I said that all the options that you will get with respect to a JIRA issue will be in these two buttons. One is edit button and another is more button. So, you have to simply click on log work. As soon as you click on log work, you will get a pop up. I will show you when you click on this. So, say for example, an issue was assigned to me which was supposed to be done in 3 days. It is a 3 days long estimated issue. Now, this is my first day and I spent one day on it. One day is considered as 8 hours here in JIRA by default. Then I will put the date started and remaining estimate is adjusted automatically. Now, work description here I can put that what all things did I did today in order to complete that issue. Then I will simply click on log as of now I am not doing that. Now, all these work log will appear over here. The user Vimal Joseph logged the work on 20th June at this time. The time spent was this and whatever he wrote in the comment is this. So, that is why I wanted to know whether they should use correspondence or. Yes ma'am. So, what happens is. Yes, yes. So, even for texture mentioned the same thing like whenever we start a day. So, we plan the activities of that day that is what we do in the daily stand up. If your team is yeah. So, if your team is very small in size you can even conduct that meeting by sitting on the chairs. But the idea is to discuss what are you going to do for today. What you did yesterday and were there any blockers or problems faced right. So, when you plan for say 10 tasks to be done on that day. It may happen that you may not be able to complete all those tasks. So, you have a log of that a to-do kind of a list there. And here specifically you are mentioning for this activity I put this much effort. And so, I am logging that effort with against that issue. So, this is how they are different and. Where is the time to do. Yes. So, ma'am in order to resolve it I will suggest you a practice. What you can do is when you conduct your daily scrum. And when you come up with your activities. You simply noted down in the daily staff worksheet that space in confluence. You can simply drag and drop to create an issue in zero. Once it is done. If it is done, you have to simply mark done at the end of the day. If it is not done, you have to just log work and write the comment. Okay, this was the activity I planned. But I did only this, this, this with respect to this issue. That is it. Next day we come in the yesterday you did this and it was not completed to the same thing will be there that this much is done. The same thing. So, here you do not have to write the description. You have to write the amount of time spent so that when the reports are generated. We will come to know how much time is left for that last thing. What is it? You do not log the time that you do not need for start time and end time. As a confluence, you do not get that. Yeah, yeah. So, this. It is not a high rate thing. The deadline is there. Tomorrow it has to be released and so many works are coming and all it if I ask why it is not to be released, they will not do it. They will do it. So, this is also part of the work. And if this is not done, then you will pass the delivery income. It is also that time it is also needed. So, can we do it once the work is completed, one day we check and we bill it. So, that would mean that you know after the end of the project you are filling up jeera in the story. Actually, we will have to inculcate all these practices. Even confluence now we are used to it. So, we just come in with us like we check mail, we do that. So, we just put whatever is there. Now, this is the additional work that is offered. No, as of now it appears to be an additional work. Moments, 20 minutes from now, 20, anyway I will be resharing these slides. So, there are like multiple options. You can integrate SVN itself. Replication, because repetition now that is the only thing. Yes, yes. So, it appears to be replication as of now. But we can. That is why I feel it is a repetition for us. Committing the code, writing the all those things we are writing in SVN. SVN is completed here, then that can be done. But I do not know how the code management system. Code management is not only SVN. Only SVN. Only SVN. So, once the user logs the status, once the issue is marked done or the status gets changed, next step is to receive issue event notifications. So, anytime there is an update in an issue, be it the issue creation itself or be the issue gets updated, an issue work log has been done against an issue. All those notifications you can choose to receive. Now, these notifications we have set up a dedicated Slack channel for each team to receive JIRA and confidence updates specifically. So, you can either choose to receive it there or you can we can enable email notifications for your team to receive JIRA updates. Now, in the last few steps, one is program management using big picture in JIRA. So, program is basically a level higher in hierarchy than JIRA projects. So, this is actually a very important part in facilitating project management using JIRA and Confluence program management. We have a plugin named big picture in order to do that. So, I would like to show you. So, this plugin big picture is used for portfolio and program management. For example, a program for NV like cloud setup, it has four modules, Gantt, Roadmap, Resources, Risk and Teams. So, this is very very important in order to manage your project. So, we will get into the details of this add-on big picture in the next session. Just as a brief reminder of one thing. You remember I had shown activity and sub activity list of NV like cloud setup project. Here it is. Yeah, here we had identified stages, stage 1, stage 2, stage 3. When we create a roadmap in this plugin, you can see we can use those stages as phases and we can put in those issues in each respective phases. It is a little new for teams here, but I am sure we all can do it. No, any, any, any, any, any. Thank you. Thank you everyone. Yes, sir.