hi everyone we're going to get started in another or so just give folks a couple minutes to get on hi everyone we're going to start in about 30 seconds thanks alright we're going to go get started thank you everyone for attending hello and welcome to the webinar on agile development in ServiceNow master your scrum skills my name is Mark Calloway and I'll be your moderator for today's session today's webinar will cover three topics first we want to give you a quick overview of Cova stick and why we are uniquely positioned to be your partner for a ServiceNow ppm implementation second we want to give you an overview of the ServiceNow ppm suite and third will focus on scrum best practices enabled by ServiceNow the ServiceNow ppm suite is a set of powerful tools that can help transform your organization's PMO but starting too much to change too fast can cause severe organizational heartburn and worse stop the PMO transformation in its tracks almost as fast as a lack of sponsorship today we will continue to expand on our recommended approach for a ServiceNow ppm implementation the journey if you will as well as provide a live demo of detailed project planning features in Spurs now before we get started let me introduce the team as I previously mentioned my name is Mark Calloway and I'll be your host for today's webinar my role at Kadesh Tech is business development and helping our customers advance their service management and business goals getting more value from the ServiceNow platform in the past as a CSM and agile enthusiast I've worked with organizations to adopt and streamline their agile development processes joining me today is Len Reynolds he'll provide you an overview and demo of the ServiceNow project and portfolio management suite Len has over 18 years of public and private IT industry experience including project and vendor management and over eleven years of ITSM process design process improvement and delivery experience when is also ideal idol foundations PNP and scrum master certified as well as a certified ServiceNow implementation specialist as we go through today's session if you have any questions regarding what is being presented please feel free to type in your question in the question box located on your screen what are best to answer the questions at the end of the session but for some reason we're able to get to all the questions we'll follow up via email also the content of this webinar will be posted on our convective website at wwlp.com for playback or sharing with other members of your organization you weren't able to attend today's session with that let's get started Kovac is a full-service consulting ferm and silver service now partner headquartered in Kirkland Washington we employ over 200 senior level consultants averaging 15 years of professional consulting and IT operations experience and have been delivering service management solutions since 2001 Cove Essex expertise is organized into three practice areas first our IT operations services practice focuses on developing standardizing and operating IT operations functions including cloud and enterprise infrastructure security operations applications administration and operate Operations build and run second our project delivery services practice focuses on providing project leadership to deliver complex IT projects Cove estates experience in project management ensures compliance quality and timing of projects and deliverables aligned with our client lifestyle practices third our IT service Consulting practice focuses on assessing defining and implementing optimized IT Service Management solutions with ServiceNow being the only service management solution partnership with over a hundred successful ServiceNow projects Kovac is a unique partner in that we combine deep ServiceNow platform expertise with a specialized practice area focusing on creating ppm solutions and project delivery our people first practical approach and guidance to projects have allowed us to achieve an average sheet that score of over nine out of ten and hundreds of clients like you see here who love us with that I'll turn the webinar over to Lynn to talk about the ServiceNow ppm suite Kovacic scrum best practices overview and a live demo of part three of this transformation agile development thank you Mike welcome everyone and thanks for joining us today so what you see on screen is a high-level view of ServiceNow the IT Bobek of ServiceNow management suite it consists of eight modules focused on making organizations more competitive and innovative ServiceNow project portfolio management Alliance project investment and consolidates resource and project data into a single system this allows organizations to plan strategically and improve the effectiveness of their project management activities being a part of ServiceNow IT business management portfolio enables a seamless and interim process for initiating project requests and balancing the project portfolio it also gives organizations a single system to track ITSM and ppm work and allows you to spend more time using your tools rather than learning how to use your tool we'll focus on the agile development applications today the kinetics recommended approach to the PPF suite is to approach it in a three-phase manner unscreened UCI recommended three phase approach to evolve the PPS suite to get your business to a fully functioning portfolio managed organization which incorporates operational cost and enterprise resource demands how far you evolve the platform and which elements are activated is ultimately up to you and based on your business needs the goals of phase 1 are to collect ideas and demand from the organization and to have a repeatable way to decision demand and to create a portfolio of projects with enough information to support executive or high-level status reporting the goals of faith - are to introduce program management as another means of classifying and organizing project to introduce agile development and distinguish between agile and waterfall phases and to fully understand how to build and track project detail project schedules and to turn on individual project status reporting the activities in phase 3 close the loop on project budgets cost tracking resource planning and allocation across project and on project work and time tracking so the gentle there are 30 ppm webinar covered captured ideas from the business for potential new project decisioning ideas and creating demand records adding key information to the demand record to support prioritizing and qualifying demands creating projects from the prove demands adding waterfall agile or test phases and kima sends to a new project and building project portfolios and associating project records with portfolios our second and most recent TPM BPM webinar covered creating the project plan in more detail through imports and data entry building project activities project tests relationships in managing the wbf adding projects to programs and enabling status reporting both of those webinars are available in our Kovacic website this webinar will focus on setting up your environment and data to support scrum create a product scenes epics and user stories performing backlog grooming and sprint planning and using ServiceNow to support your key ceremony we'll also be looking at how to track burn down and velocity so with all that let's get started all right so here are done by development and of service now I have logged in as a product owner and I'll be working out of the agile development application for those of you that have been on the platform for a while the agile development application used to be called a PLC it was enabled to the FDIC's firm process pack plugin users that need to work in this application will need to have the roles of scrum admin and scrum user in order to see the application and active action those activities within the application one thing to note is the agile development application is a very data-driven application and there is a best order or a best sequence of events about how you set up your environment and set up the data so first you would start by identifying identifying your product that's an application model inside the system and identifying your product over here I'm using ServiceNow is an example from there you can begin to articulate those releases that you want to do to release any functionality to the environment for this particular project project I've identified one release but you can have as many as you like particularly if this is a Productivity in your organization for a while and you'll be enabling additional functionalities in a series of the leases you provided that more detail about this release and a way to categorize stories you have to articulate themes so here inside our ITSM core functionality release we've identified disease event management and knowledge management for an additional level of detail and then likewise you can identify epic again to classify or organize categorize like or similar stories to support reporting and calculations here we've identified the epic rib incident management core major incident management and knowledge management and those stories all aligned with ethics in theme and neck up to the product let's go ahead and take a look at Billy's you have the ability to set a default team the team that's going to be working on this release and we also have the ability to enable the team here or associated team with this release here these hundred points that show up with this team are actually calculated from the available capacity per sprint for each team member and this goes into calculating both your burn down your velocity and Q metrics for each sprint we have four Sprint's that have been identified she supports this release so far again organizations can work together to figure out if they want what type of cycle they want to do whatever they want to do weekly sprint cycle every two weeks every three weeks every four weeks and based on that you can begin to build your sprint schedule and start associating your stories with those sprints he activity is really to begin to build out your backlog typically that's going to you know often begins before a planned release you'll start collecting enhancement requests and defects from your users over time and as and then after review of those defects and enhancements you can articulate the stories that goes into your backlogs so this begins to formulate the the list of stories illicit activities that you want to do during table new functionality or correct bugs for this particular product before we go and look at a at a story pressure let's go a little bit that's right so the key of the story and this is kind of the primary records that you'll be working on the majority at the time and again you have the automatic ingenuitive number you've got the products here service now associated is our relief you could have a theme you've got the release associated with it and then this happens to be sitting in sprint number one you also have the ability to associate the epic the priority is a way again to prioritize the stories in your backlog and that will help inform you when you do ranking and sprint plan you also have a couple of types that are available to you primarily development and documentation a lot of the work that will happen inside these prints will be development and configuration work on the applications that you may also have documentation activities such as developing training materials developing testing materials documenting what got what you just were performed in the system and this is a way to distinguish between development and documentation stories very standard lifecycle associated with stories so I start off in a draft mode sort of a rule of thumb when they are ready to be worked and by that I mean when they have post identified confiscated of them as well as acceptance criteria soon they're typically understood to be ready to be picked up by a developer and then once the story is in progress or is in action is being actively worked in the developers knew that to work in progress when the development or configuration work is completed and it's ready for testing which ready for testing state can be used to let the tester know if this is a story that's ready for testing and then once the tester picked to fix it up the story community to the testing state to show that effectively being tested and then once that worked for this then remove it to complete so very very standard life cycle you track work over the course of the development cycle likewise you've got classification here again classification is a mechanism to distinguish between an advanced mobility effect or a feature in a defect some organizations will use story to capture defects post-production to get those those defects into the backlog they'll work there is also an enhancement as well as a defect both of those modules are instead of a agile development application of apocalyptic codes in the moment those are other mechanisms for tracking and have certain defect work but you can then turn into stories like life there's a blocked feature this is a way for the team like scrum master to show that a story is blocked but it needs some type of action say a decision or escalation to leadership or mortgage sources the story will stay blocked until the team they is ready to pick it up and work on it again until that issue has been resolved description is an area to provide some more detail about the story and then the accepted acceptance criteria of course is where you would specify what's your completion criteria what acceptance criteria will need to happen for this story to be considered complete and ready for testing ready to move on the front they're one of the key pieces of the agile development application is planning board actually I have it open over here the planning board first thing to do is you pick your release and it's got a left side on the right side so for this V where I have product backlog on the left side and scrum release backlog on the right this is the mechanism that you use to be product backlog grooming so stories that are sitting in the product backlog on this side are associated with the product but are not associated with their release so from here you see we have a story that is associated with the product but not associated it is release so in order to associate it with the reviews I simply grab it and I move it to the right so now it is in the release backlog and this will become important than we do sprint planning you also have the ability to move joy's up and down in the list to rank them you also have the ability to rank stories from the list view on the sprint which we'll see in a moment so now if I toggle this left side to the screen release backlog and the right side to the sprint backlog then I'll see all of my stories that again are associative it'll release but did not have a sprint identified and are available for sprint planning so here if I want to begin to populate my sprint floor for knowledge management I can grab this is knowledge stories that are in the release backlog slide them right and they will now be on this bridge okay so now let's go so the Sprint's that would just took a look at some notice we moved an additional story over into this print so now if I look in the list of stories I'll see that it's there here we also see our four team members with their available points these are the points that they are available to work on each sprint but that's what comprises the tun points that shows the capacity for this print the story points that are associated with the Sprint's are derived from The Associated stories so each of these stories were eight pointers so therefore we have 16 story points and complete a point that number will grow as you complete stories within this frame so this isn't a good view that you can use if you're a scrum master and you're running your daily standup and you want to have a quick look at the Sprint and the work that the stories that are actively being worked in that sprint you can use this tune to manage that stand up every day some scrum masters prefer to work out of the list of you and again can open up individual records and adjust the priority is needed move it from state to state adjust the points perhaps there is another and you also have the ranking available to you here another view if you prefer more of a card or a visual Kanban view you click the story progress board you and I see my two stories that are in this print I see their current state so again if I am mandating my daily standup I have the ability to move this story from one state to another the other things that you can do from this of you looking little circles with the line through it shows that this gives you the ability to block or unblock a story from this view you do see the point scenario associators of the story you also have the ability to add a task and we're going to take a look at what this tech look like in just a second so this is a nice review for scrum masters to use again it's one of the visual Kanban view but you always have a few available to you okay I need to open at the story so one of the other things that are available to teams is there are scrum tasks and scrum tasks allow you to create another record associated of the story for even more detailed work or perhaps if someone is helping you did the story say for instance you standard developers it's working then the primary place of the story that you need some help from either a QA tester or another person in the organization this is a way to assign that work to them I'm here rather than points we are actually tracking hours and so this allows you to plan the hours that we think this task is going to take in adding the new taxes you like to support that particular story and you can also show dependencies in between these stories again this is a good way to show if a particular story needs to have other stories finished before it can be worked because these dependencies here so the next the last thing of a note to move a story from a draft state into ready you will have to add or you need to add acceptance criteria will not be able to move it to a non draft state without adding acceptance criteria because that essentially says this doing is ready to rework to journey to be picked up in action now let's go to a completed square so a couple of reports that are available to teams and scrum masters are the burndown chart and the team velocity chart the burndown chart has three key pieces of information it has the total committed points in other words the estimated plans for this particular sprint which was 42 as the ideal burndown so this is a service now saying if I work if I spread my points evenly over the period time I would get to zero at the last day of the branch and the burndown would look like this which typically does not happen you also have the actual burn down which shows how the work was actually performed where perhaps you went along and not a lot by completing it and then suddenly a whole bunch of completed will work out completed over time so it shows how the progress actually happens within that sprint last their additional chart that is available after you have a couple of completed spending about you can look and see the velocity of the team you can see how that team is performing in are they able to complete more story points fewer story points it gives you some other data points to see how the velocity of the team is progressing so here we see in what ones we were able to complete 42 and then in sprint three major incident we've got about 20 points done for this for this period or for those fronts or again this is another data point that you can use to see well you know are we hitting road block are we not allocating the the team and funny as we might all their early over allocating them here or we simply just not Kitab able to complete stories as quickly over time so couple more things before we in the demo you might recall from our first two webinars that you do have the ability to add Sprint's and stories to agile phases within projects you can add princeton choice to agile sensitive in projects you can also enter in some stories here two releases and then the stories that are associated with projects are still able to be pulled into sprint planning and an added to your sprint so that they could be worked so again if you've got activities that are that are coming in from projects as well as activities they're coming from because you're able to see that work within the system and then lastly as I mentioned earlier a couple of the the applications we have enhancements and we have defects so again it's up to organisations to decide how they're going to interact with the tool if they left to use stories and designate them as people access one mechanism even Apple captured effectively from the environment here if you captured the effects on the environment you have the opportunity to create a story by simply right mouse clicking on the header and the same thing for enhancements so this again will create a story that you can pull into your backlog and pull into your sprints and work through your normal scrum practices and you'll have that association between the defect and the story okay the back completes our agenda on scrum and agile development the bet as a trait back over to you mark great thanks Lynn I've got a couple questions actually while you're in there the use of in your sprint planning to section the use of the blocked box does that suggest that all team members might use ServiceNow on a daily basis instead of a single administrator it does actually typically teams are in the system actively working their stories they're adding content to their stories their attic acceptance criteria they are very well could be progressing them across the various state and they can use the planning board or you know just updating the state's themselves to do that they don't have to wait until the daily it has scrum master do it they can be active participants in the tool great thankful Vanetta question as well in general will the ServiceNow tool provide hint as to what you might be missing if you cannot advance to another state for example draft to a ready state right one of the things you might have noticed is it was grayed out but acceptance criteria has an asterisk ayat that asterisk is bright red showing that it's a required field and it will prompt the person filling out the story records that they need to put some content in that acceptance criteria field and order correction the following likewise something that's across the ServiceNow system would you encounter required information will be prompted to fill in okay thanks and just remind everyone if you have any other questions please go ahead and submit those in the question box so we can answer those as many of those as possible if we're out of time we'll follow up answers with you know with you the final question I've got here well we wait for anymore it can I manage my projects my project tasks resources and dependencies and so us now yes and actually covered that in the a fair amount of detail in the second webinar you can set up portfolio records and four groups of projects and then articulate your individual projects drove out the WBS there's a really handy aspect to project couple planning console that allows you to not only add your project tests but put dependencies in between those tasks and you can also inherit agile and testing you didn't spend a lot of time on testing with webinar but you can also add testing phases to track your testing activities inside the project and life life that's an additional module is available inside the applications or detect your testing activities though your during scrim work so yeah there's a whole rest of the I TVM suite for a project portfolio management that was covered in addition to your scrum and fancy thanks Len another question here does the app allow or fill Susilo date joint team estimation as in planning poker join to destination is in planning poker a bit different it's definitely supports the ability to estimate your available capacity is to put the ability to estimate your story points for stories and then use those to support sprint planning and on the track your velocity that's kind of a to me yeah I think that was the gist any other questions don't see anything being submitted on pure will gets them after or so will definitely fall through email with you but hopefully today's demo allowed you to see the benefits of using ServiceNow ppm suite ServiceNow ppm can not only replace the spreadsheets you are using to track projects but it can also be the one and only tool to use an organization for both project and non project work lastly if you have any additional information or questions please feel free to send us an email at service now at cove st comm that will conclude today's session thank you for attending and remember to keep an eye out for upcoming webinars we have two that are slated for November one is an introduction to automated testing and service now with practical tips and tricks and actually the second would be in December CMDB and avoiding categorization sprawl and redundancy with the CMDB thank you again for attending and we look forward to working with you thanks Mike