Strategic Portfolio Management | Getting started with Agile Development 2.0
getting started with Agile development in the service now strategic portfolio management application Agile development helps you manage product based or Project based efforts using the scrum framework you can also create your own hybrid approach for this video we'll use a product based example let's say you're a product owner and want to build three new features for an upcoming release for each feature we'll create an epic the epics are assigned to an agile team then within an epic stories are created stories are smaller units of work that are related to an epic and are usually assigned to an individual from the team these stories form part of a product or release backlog tasks are the smallest unit of work that must be executed to complete a story some examples of scrum tasks include analysis testing and coding let's see what this looks like in the application to use Agile development you'll need to activate the Agile development 2.0 plug-in from the application manager we need to create epics For an upcoming release in the Agile development application we're logged in with the scrum admin [Music] rooll then inside each epic we'll create stories and [Music] tasks next from the agile board landing page let's create a backlog we'll give the backlog a name and add the required conditions now we're ready to create a Sprint a Sprint is a defined period in which the stories are to be executed typically a Sprint is 2 weeks long in our case we'll create three Sprints to take place over the next 6 [Music] weeks we'll assign stories to the [Music] Sprints then we can estimate the level of effort it will take to complete each story through story points let's take a minute to add points to each of our [Music] stories [Music] the group capacity indicator reflects these story points if we assign too much work for the group the indicator turns red and we can simply reschedule one of the stories to a later Sprint when the Sprint Begins the product owner and the agile team can track the progress of the scheduled stories ideally at the end of a Sprint all stories should be complete in our case only one story was completed so when we Mark the Sprint as complete we are prompted to move the incomplete stories to either the backlog or an upcoming Sprint and when the next Sprint begins the process will start all over again for more information see our product documentation or knowledge base or ask a question in the service now community [Music] be
https://www.youtube.com/watch?v=oaSXJ4xlls0