foreign and welcome I'm Andrew McDonald from Glide fast Consulting and today I'm going to provide a quick overview of servicenow's agile story module in this video I'll explain how to create a brand new user story associate this story to Sprints releases and other related records as well as manage that story throughout its life cycle so without further Ado let's get started once you are successfully logged in type in agile in the application navigator to your left to find the Agile development application from there click on the stories module this will bring you to a list of the stories that have been created click the new button in the top left corner of your screen you will be taken to the story form here you can provide details of your story such as the theme the Epic the state more on that later the story points or level of effort the Sprint this story will be pulled into the product currently being developed or enhanced the release the story will be a part of the group and user the story will be assigned to the project the story might be Associated to as well as the Project's face the original task this story was created from whether the story is blocked and if selected the reason for blocking the story the short description description and finally the acceptance criteria for accepting the story as done note that while only the short description is required it is also recommended to complete the description and acceptance criteria if possible once you've filled in the appropriate details of the user story click save to stay on the form or submit to return to the story list now let's navigate back to the user Story You've created you'll notice certain tabs related links and related lists are now visible the notes tab allows you to post comments and work notes as well as view the activity of the story record over time the related records tab allows you to associate the user story to an existing defect or enhancement in the related links section you are able to add scrum tasks in bulk convert the story into an epic you can use to group additional stories create a copy of the story or split the story into two or more smaller stories the final section of the story is related lists this section allows you to create and or associate scrum tasks and any prerequisite or dependent stories to your existing story scrum tasks may be used to track analysis or development effort related to the story while any story predecessors or dependencies may be tracked using the prerequisite or dependent stories related lists now that we've covered the form in its entirety let's cover the story's life cycle by reviewing the state values the default state is draft which means the story has not been fully groomed and not yet ready for development once ready for development move the state to ready when development has started move the state to work in progress and when it has completed move the state to ready for testing when testing has commenced move the state to testing when the story has been accepted as done move the state to complete to signify the code is now ready for production if at any point the user's story becomes no longer necessary move the state to canceled a couple of things to note about the story States first you can move from one state to another such as from ready to cancel to draft at any time without restrictions second unlike an incident the story form does not become read only in canceled or complete state and can be edited at any time so that is a story module in a nutshell we learned how to create a user story Associated to other related records and manage it throughout its life cycle thanks for watching foreign foreign [Music]