 Hello and thank you for joining us today. My name is Ty Davis. I'm a technical marketing manager here at kit lab Today I'm going to be talking to you about agile project management using kit lab We'll also be touching a little bit on safe scaled agile framework and how you can set up the structure I see organizations looking to align themselves with the safe framework We'll touch on a few slides here first before getting into the demo and then once we get into the demo we'll start looking at how We've built on agile structure with our a mock organization health care provider incorporated When we take a look at the structure of get lab we have groups and projects groups will be at the highest Level so you can look at a group as you'll have one group as the parent group or the umbrella group and then they'll be Subgroups that can fall underneath that there could be subgroups under those subgroups, but When we're looking to do agile at this top layer at this group level We have the ability to have access to epics milestones Which is a time box and get lab terminology so you can build out sprints You can build that releases using the milestones feature. There's a roadmap which is going to show you a compilation of all the epics and the timelines associated with them and then you have the ability to create labels boards and Projects that fall underneath those groups or subgroups So we see here when we're talking projects that project resides within that group Level or layer That that project there could be a project associated with one group And then there could be a subgroup underneath that group and that can have its own projects as well So once I have a project you see that there's your gift repository Issues and discussion can happen at that project level labels are also Built into that project so you can have specific labels for that project where maybe that team is using Identify all or a specific naming convention for those labels and they can build out their own boards as well Create milestones which may maybe associate that with a sprint and doing scrum Or just a a release a start and an end date and then as well You have a cycle analytics that can give you insight on that project When we're talking agile in the way that that git lab has its Its names for for what we've built inside of our tool We call issues Or we call User stories issues or for people that are familiar with issues are ready You could just keep moving along with issues But some people are familiar with user stories We call that an issue again re-itering what I said earlier about milestones Is that something that you could build out of time box in this particular case for if we do a scrum? We built out sprints using that milestone capability So within that project you have a repository the repository is a very powerful capability as part of git lab It's something that we're very well known for Inside that repository you have the ability to do Merge request you can make changes you can have reviews and discussions around those MRs You could do approvals you have visibility into your CIC pipeline So if we're looking to have visibility along the end-end DevOps we can see the status of Co-change when it comes to quality when it comes to Security when it comes to performance you have that capability Inside of the repository and and specifically with merge request and identifying Pipelines that associate with that merge request You also have the ability to do a review app so once you've added that code you can review the app before it goes live to production and Like I mentioned you have security scans That give full reports back on any vulnerabilities that are detected whether they're me like medium or severe You'll have that Review and report given to you around that merge request When we look at git lab and scale the agile framework the organizations looking to move towards safe You Are going to be able to align via what we just talked about the groups and the projects How we look at it is for that Maybe that if we're looking at portfolio safe and we're looking at that portfolio level That that high group that top parent group or umbrella group is going to be at the portfolio level There's going to be a subgroup that aligns with the value stream and then a second subgroup that aligns with the program And then we could see that You know there's possibly depending on how large the agile teams are that are contributing towards that agile release train and there could be a third subgroup if it's just a couple of Scrub teams that are all added together that contribute to an agile team as a whole that's contributing towards that agile release team But a lot of that work is going to be done at the project level we could see here That's where we consider the team level. That's where you're going to create many boards issues User stories are be created in there, and that's we're going to have a lot of our our dev work and testing done Breaking it down a little bit more. We look at that portfolio level. So we're looking at that Top group level. Maybe it's the Maybe it's an application. That's part of an organization. Maybe it's the whole organization That's at that group level. We'll see in the demo here the healthcare provider It's a smaller healthcare provider organization But the the enterprise is represented at that portfolio level and they're going to build out value streams that align With where they want their healthcare organization to be headed towards So we look at the portfolio level and doing safe We create those portfolio epics at that group level. We create levels The way we look at strategic themes is that when your business leaders are deciding what are the strategic themes that are going to drive this Organization that's going to be done via group labels. So in the case of this healthcare organization, maybe it's satisfied patients satisfied employees Modernizing technology or being innovative and they're going to create those strategic themes via labels And then when we create those portfolio epics, we're going to are going to tag those strategic themes that align with that portfolio epic You can create a project on that high that that portfolio group level so that you could create Maybe non-functional user storage issues. There could be discussion around those. That's going to drive that backlog that's going to drive The the epics that we are moving into progress at that portfolio level a Subgroup will be created at this portfolio level. That's going to align with a value stream We'll see again in the demo and there's six value streams that the the business leaders decided would drive the organization and those are created in subgroups So looking at that subgroup that value stream you have milestones. We talked about time box, which you can set the dates and time Start and end dates for that solution train that could be tracked via milestone labels as well Anything that aligns with that value stream You'll you'll create the labels that align with that. We'll see how that's done once we get into The demo here again, there's You can always have a project at a group level It's not isolated to that the lowest subgroup. It could be at different levels It could be at the highest group level serve group of that create project and what this does is it allows you to have a Board that is specific to that that group level That will you know if we have that portfolio board now we have this value stream board maybe moving into that program Level you can have your Kanban board there moving features and labels along that have been broken down from those portfolio epics And we can see that here at the program level there's Subgroups that are are making off of those value streams These are made up of a series of agile teams that are contributing towards an agile release train Maybe several scrum teams that make up for that agile team that are all working together to push Releases out at a regular and frequent cadence on that agile release train Pushing out working software making sure that they all work together Something that can be done at that subgroup to our subgroup level where we have an agile team as a whole that that may have another subgroup of Scrub teams that are contributing towards making that agile release train go Now we get to the team Team layer of safe. This is where we're gonna have Probably significant more amount of projects that are specific towards Dev and testing This is where your functional items are gonna be worked on. You're gonna have Issues and discussion here gonna have many many issues Specific around functionality building out Code and this is where we're gonna compile that all here at the project level. We'll be able to do backlog management We'll be able to do Our PI planning. I'm actually we'll do our PI planning at the program level and this is where From that PI planning will take our PI objectives break those down into issues and then and then start working on on those issues You have visibility into The boards when it comes to seeing, you know, what's in progress what's being worked on what's done. I could create Team boards saying who's working on what you can create that that PI objective board and start assigning Issues to sprints or doing our sprint planning or taking it from the product backlog moving it to the appropriate sprint and then doing that assignment of issues to That sprint where either if you have a self-organizing team they could pull those issues off they can assign them to themselves Or maybe you're an organization that has a scrum master or a product manager. That's doing the signing They can do that as well. This is where that repository we talked about it's gonna reside inside those projects That's where our merge requests can be done. You're gonna see changes You're gonna have reviews of discussion done at that so that collaboration piece is gonna be done here Where I have visibility into the changes that you've made the code I can comment on them We can collaborate and say hey, this looks good, but you know, this doesn't look good. What'd you do here? What I do here and it gives us that tie-in Around collaboration around all these code changes that we're making we could see The pipeline pass or failed. We can also collaborate on that Hey, this is what I saw on the coast why it failed and if you want to change that and then we have visibility again into the security part of the performance of Those pipelines and then you have a review app. You can see the changes and see how it looks on Your application before it goes to production something else that along the collaboration piece via email via Slack via what matter most You can also collaborate using those tools and add issues to the backlogs This is a very detailed View at at GitLab safe and you could see there's different At the highest level the portfolio group. It's a subgroup the program agile teams that are following as another subgroup of those value streams each each level has its own project where Issues can be created whether they're non-functional or functional More once you get towards the the team subgroups, this is where your projects are going to have more functional items that are being driven More along the functionality of the applications of the software that's being created This is just another quick snapshot into the portfolio looking at the value streams. It could be associated with it So now moving on This is the end of the slides real quick I hope I got through them pretty quickly here for you And we're gonna go ahead and jump into the demo and start looking at how you could structure your organizations agile planning or a scaled agile framework using GitLab I'm gonna go ahead and jump in here and if There are any questions Feel free to ask at the end of this or put it in the comment section of YouTube and we will be sure to respond as quickly as possible around any questions that you may have So what we're doing here is we're taking a look at What's a mock organization a mock company? We've created its healthcare provider incorporated This is a healthcare company that has different parts or different Value streams and safe terminology that make up the organization in this case. There may be a newer Healthcare provider once you see some of the issues that are built around but this is just for demo purposes but healthcare provider they are a very Experienced or they are experienced in agile. They are doing scrum planning Pardon me. They're doing scrum. They're using The GitLab backlog to do their backlog management and they've just started looking into Scaled agile framework are doing safe and they are now structuring The organization around the scaled agile framework for this Organization when they're going towards safe What they've done is you have a business leaders that agreed At a high level what these strategic themes are for that organization and those strategic themes for this hospital Or excuse me this healthcare organization is patient satisfaction revenue growth staff satisfaction and technology advancements And they've done this using labels with GitLab. So when I'm creating my portfolio epics or I'm creating my value streams They Pardon when I'm creating my portfolio epics. I can tie that to a strategic thing so if I were to go over and Take a look at the epics that were created from those strategic themes at the portfolio level I I'm going to be able to see that I've tagged using the strategic theme or using the specific strategic theme That's been assigned to them that we came up these six different portfolio epics at that pro at that portfolio level that we believe will drive Organization on what will happen is these portfolio epics being taken and breaking and broken down into Features or enablers and then thus broken down more into issues from there. They can be part of PI planning where we take those Features enablers we break them down like I just mentioned into issues and then we create PI objectives out of those Now again, this is just demo data So we have only a few listed here But if we were to look at a real organization to be probably quite a few more portfolio epics Going back and looking at the healthcare provider Organization instead of get lab we have groups and projects. That's how we structure So this is at the highest group level I could call this the parent group or the umbrella group the highest level where the health care provider Organization or enterprise sits and then following underneath those is a subgroup. So you have six different subgroups in this particular case These are what we consider value streams for a scaled agile framework These were determined by the leadership that these are the value streams that are going to drive this organization So we have primary care online experience specialist laboratory pharmacy in hospital The portfolio management piece. That's just a project that sits at that portfolio level So I can create some issues at that portfolio level that may be specific to that portfolio management Possibly non-functional items or issues that need to be created Diving a little bit more into one of the value streams here So we dive into the hospital value stream We can see that's a minute of a six different agile groups These are groups that are contributing towards that agile release train. That's part of that value stream for that hospital value stream these six groups or six agile teams all have scrum teams underneath them that are Contributing or working together Extribute towards that agile team. That's part of the agile release train And so we could look at billing here and see that we have several different scrum teams that we've put together Around employee payroll patient billing vendor billing and 501c3 billing and these are all groups that are working together to build out that that feature and capabilities around billing that are all going to combine together with the different ones that you see here inbound patient records staff scheduling and outbound When we go into billing I Could take a look at the epics that are part of billing and I could see that what we call Epics that get lab or these would be considered sub-epics because you've already seen those portfolio epics that sat at that healthcare provider Parent level these are sub-epics interchangeable with the feature terminology or enablers for our scale the agile framework framework But these are what we broke down from those portfolio epics and so you could see here that some of them are broken down into specific Insurance companies their specific Features their sub-epics around billing statements and adding payment methods and these are where you're going to have Groups take a look at these features these enablers And they're going to go into their PI planning sessions. They're going to break these downs They're going to get them they're going to get PI objectives out of these which are going to be Made up of issues or user stories if that's the terminology you're using inside of get lab we go by issues and so that will be part of that PI objective that is taken out of the PI planning sessions and When those those individuals that are Associated or part of that PI planning session are taking a look at these these features at the billing level From here, we can go over to issues and this is where we'll see issues that were determined from that that PI planning session That's part of us, you know specific PI objectives We have a running list here of the issues that were created. I can go to the board view and this is where I'm going to be able to see that there is a product backlog here or a PI Backlog that has been created with issues I have the ability to do rankings so I can drag and drop and this will rank these issues As part of this board as a higher priority if we went to a different board and want to see all the opens It would retain that that ranking system We also have technical risks that have been assigned to these So I do have a technical risk board that I could take a look at the high and medium low risk issues that have been determined and this would populate those based off of Which issues have which label shows associated with them This has a filter on it now for sprint one So we don't actually see any yet until we do go Assign issues to sprint one. Sorry. That's a scrum team board. I'll go back to the objective So that's where I can have a a product owner or product manager or scrum master They start assigning the specific and issues towards the sprints that they think are Excuse me towards that sprint that they believe it should be prioritized in this case We have a couple different issues that I want to put over to Sprint one These were created organically from get lab itself down here We could see we have a couple different issues that were created one was via a service desk so someone submitted a ticket verse with a service desk that's built into a get lab and a couple others one was done via maybe slack or Done via matter most and those issues appear on the backlog So as I'm assigning these issues here, it's moving over to sprint one These are all the priority or the issues that I think are top priority for sprint one I now have that sprint back log planned and I can go over to my dev board and Begin moving issues into progress and either Assigning those to individuals if you're an organization that's doing, you know product manager or a scrum master That's doing the assigning of issues or user stories that could be done or if you have a self-organizing team Doing scrum they can come in here and they could pick issues that they want to work on so if I were to come in here Probably as a patient I can view my billing statement. That's very important in order for someone to pay for that that bill that they have I'm gonna sign this to myself. So I've assigned it to myself and I knew move it to in progress and now I'm working on that Same could be done for a couple of years. Maybe Dan came in here. He assigned this to himself. He moves that to in progress Same thing for John Jeremiah. He now assigns that to himself and Moves that to in progress Built-in is though you have weights that you can associate with those Issues and so you can see here. There's a couple different weights 15 and 15 both for these issues that Dan and John have I have a as part of my weight For you know in terms of story points, maybe you're using a Fibronacci scale Or you have your own system built into your organization that you could do that using issues as part of Sorry, you could do that using weights as part of these issues and then later on We'll see that you could take out and a burn down chart where you are progressing with that issue weight and issues and Look at the anticipated Projection for what you were looking to have done as part of that that specific sprint Or time box, whatever you may call it So I'm working on this You know, I complete the I build up my code around my code as a patient. I could view a billing statement I think it's good for review now. You may be able to or your organization may Use different terminology around what stages should it should move in maybe there's an end testing You can build that out using labels and then edit these boards and Organize these boards using those labels for us. It's review. I've moved to review. There's a close over here Maybe my review it needs to have a successful pipeline and needs to pass, you know, certain tests Certain quality tests certain security tests or performance tests before it can be moved to closed But in the meantime, you know, we are an agile team So I should hopefully get that feedback rather quickly But I want to go ahead and just take another item or another issue off of that backlog That was assigned to sprint one assign that to myself and then I could begin that Work on that issue and it moves in in progress and progress tag is added there So maybe as a scrum master or product manager, I want a high-level view of What's going on the team or who's you who's working on what I can come over here to this team board view I could see what Dan's working on with John's working on I can see what ties Work on on he has one in review. He has one in progress. That's good. He doesn't have to in progress We rather have tie working on one Item in progress and not working on multiple. So that's in review and hopefully that moves to close We can now look at that technical risk board We could see that because I had a filter around sprint one and we did the assigning of these issues to sprint one I could see what is a high risk? What is a medium risk? We have no low risk in sprint one It just gives me a snapshot here based on that risk level that we've created via labels So heading over to milestones here This is where we get lab to find our time box and this particular case You know, I'm trying to look towards aligning towards the scale that don't framework So I've created four sprints in an event innovation and planning sprint as my fifth sprint Over two week increments. So adding up to 10 total sprints as part of a PI objective that we're working on And so you have the ability to change these names based on what your organization does And in the time box that you're labeling those but we do call these milestones at get lab That's a terminology that we use when you have that option available here on the left. I Could pop into sprint one. This is where I'm gonna have visibility into a burn down chart Because this is demo data and I've been moving stuff back and forth. It's gonna have a a little bit of a strange Graph to it line to it right now I can see the issues that I've created the issue weight that comes along with that I'm what I'm gonna do though is I'm just gonna cut over and we'll take an actual look into a real Real-life Burn down chart and board that our own dev team around verifies doing so we could see here the open and deliverable on close That's the way that they go about doing agile is using those are that terminology And I can go to the milestone here and see for the milestone of 11.7 What they've been doing and this one just ended but we could see that there's a certain amount of issues created We could see with the issue weight and the burn down chart that they've gone along with that a little bit of flatlining here but the ability to use burn down charts inside a get lab based around that that sprint or The milestone that you create and get lab so coming back here to the board view inside of issues Just want to kind of show that you can Maybe from the dev board even though we've probably hopefully worked out what issues are part of this Sprint backlog or what's part of this PI objective? Excuse me and I Can I can go ahead and just if I'm if for some reason I needed to add a new issue I can do that in line here or if I needed to add an issue I'd head over to the Project within billing so I'd find the different scrum groups probably inside of patient billing is what we're looking at I could see that there's two projects here Projects fall at any point could fall underneath the group and the way that we've set it up those projects That's a container for where the dev works being done This is showing that the billing statements and credit card payments those are two different projects at the scrum team around patient Billing is working on so I can go into billing statements here get inside that project take a look at the issues Go to the board See what issues are associated here. I can add an issue from this area Oops I Can add an issue Here from the list view and what's going to do it's going to take me over To the new issue creation page and this is where I can add a test I can give it a description I can assign to myself or I can assign it to a certain member That's part of the team assign it to a milestone. You can see several different sprints here and I can also Give it a label, you know if it's associated with an agile release multiple trains in progress Which you probably want to do unless you're moving that into progress on the board But you can see the different tags that are associated with there give it a wait And then also if you wanted to give it a due date you can do that as well Markdown and quick actions are supported inside of these so Which I click on to mark down it takes me a nice little kit lab help mark down area But you can do mark down inside of this description. There's a lot of different options and choices Available for doing markdown. You're just adding maybe an issue to an epic or Associating two issues together just using markdown that possibility is here I'm not going to submit an issue in this particular case so now we're here on The page of issues that are specific to the billing statements group what I'm going to do I'm going to see the next step and As moving along that agile planning of smoothing this issue that is maybe a problem or it's an answer request Something that we've created as an issue and now we're going to have That that dev team members begin working on it. They're going to create a merge request around this They're going to check out a branch to work on from the master branch. And so what they're going to do is they're going to go in and they're going to Create a merge request we can see that I've already created a merge request as part of this issue and They simply just create a merge request From that issue inside that issue. It's going to put the related merge request for that issue I'm going to click into this one that I've already created And it's going to show me a couple of different things here that I get along once they've created this merge request now I'm just going to give a quick high level view of merge request and the DevOps Pipeline there's many demos that we've created that dive a little bit deeper into How this pipeline works or maybe specific around the security or specific around Performance and those can be found on our YouTube channel But I'm just going to give a quick view as we started with agile planning. We've created those issues We've assigned them and what we're doing now is we have that dev person working on the Correcting the code or creating code. They've created that merge request taking a branch off of master and now in this particular case the Changes have already been pushed in this one They've been pushed. Sorry not pushed but these changes have been made and now we're running a pipeline and The pipeline is doing its Checks on these different stages. So it just did the build and pass and now it's doing a test We can see the different stages that are correlated with that. We'll dive in this and a little bit more here in a second Down here we can go and actually see what changes were made In this particular case, there's some text that was changed around the just the header there This is a very very very simple demo So Once we go in this pipeline We can now see laid out in front of us all the different checkpoints as part of these stages I can see code call code quality Container scanning dependency scanning license management Static security testing and then maybe just a unit or quality testing that we built in there Review app be built out So we'll be able to see the changes that were made before we push that to the master branch There's dynamic security that we have along with us a performance stage and then a cleanup at the end So this pipeline is going to take a few minutes to run here as it's doing all of its checkpoints Something that's going to happen, you know once once that hopefully passes if it fails it will have the ability to go in and see Why it failed it'll give us a Failed pipeline area where we could see Specifically what part of that pipeline failed that we can address that from there But if this does pass and I'm hoping it does It's going to give me that capability to merge into master branch in this particular case I have the Capability or the rights to do that merge myself if I needed approval I could add Or that maintain or someone can make sure that an approval is required before it's merged into master This if it passes, I'll be able to Resolve that work in progress and that will give me the capability to merge so What I'm going to do I'm actually going to go over we're going to check out a An open merge request actually not an open or I got one that was just merged and That is the one I did just a little bit ago updated the text color for the title page We could see that the pipeline passed. It gives me a pass on all the stages It gave me a security analysis. I get a view. I could view the full report of all the new vulnerabilities Again dive that deeper in a different demo. It gives me a full report on licensed management This one show who it was merged by the changes will merge into master and it gives me it gives me a Quick snapshot of what was done around this merge request in this pipeline. I've already clicked merging it You could see it's still working on deploying that to production right now So it's going to again go and run that pipeline and push that To that that master branch It should give me the result of Changing this title here to get lab purple on top of this already purple background If I wanted to see the changes that were made with this again, I could take take a look here I could see that there was a color change around the header from orange to purple Not the best choice. I may put again. This is the the most basic app How we can do just just for demo purposes so this Demo basically has gone through it's it started off with talking about agile planning. We've talked about How a company can use GitLab to do that agile planning how they can start aligning to that skilled agile framework Structure what we did here is we created issues. We did a lot of backlog management or PI debt PI objective Planning we did our sprint backlogs our PI objective backlogs and we assigned those to Members on the team that began working on those they went inside these issues They created merge requests around the code that they've either changed or added and then we see via these Pipelines that that code's getting tested. It's getting security testing down around. It's gonna be performance tested We're checking the licenses that are associated With that that branch is being committed and we're seeing several different things as part of that that DevOps pipeline if you have any questions, please feel free again to Go ahead and list them down in the YouTube channel comments there We'll get back to you. I appreciate you taking the time to take a look at GitLab and how you can apply this agile methodology or apply it safe using the GitLab tool