do you know what is the most common project management tool in IT? I tell you this is jira and
if you are an IT project manager you're going to be dealing with jira on a daily basis today let's
chat on how to quickly set a scrum project for your team in jira hi guys welcome to the project
management sandbox if you're new here my name is Kris and here on my channel i'm sharing tips and
tricks on it project management so if you're new make sure to subscribe and hit the notification
bell and meanwhile we are getting started so for today we're gonna be talking about the project
management tools and specifically i would want to touch base on jira this video is gonna be in
a kind of a new format for this channel and it's gonna be a tutorial so what i'm gonna do i'm gonna
share my screen and i will show how exactly i'm gonna create the project in jira how i'm gonna
set the workflow the issue types and statuses and everything else that is relevant and that
you would need to do before starting your work on a project okay let's have a look here is actually
my active project but we are not gonna look into this what we are actually gonna do we are going
to select create a new project and here we would need to input the project name and project key
let's just define let it be pm project okay and the key would be pmp that's just the abbreviation
of the project name that we are going to have now we're going to choose scrum and click create
so voila here is your project this is a really basic settings for the project that you will
usually see where the project has just created what we need to do
is to change the workflow so that it will comply with the requirements and the needs for the
particular project let's choose the workflow for our project the pmp one you will see the diagram
with all the statuses that you currently have but as long as this is a software project we
would need to have way more statuses and this is first of all would be needed for the convenience
of your team and for your convenience as well because status help to track the project
progress so we have the status to do we have the status in progress meaning someone is already
working on it let's add the status code review on software projects code review is
an important status because quality of code is vital when it comes to delivering
a good solution to the market another status that i would add is ready for qa this means
that the development is completed the code is reviewed and the feature is available
for the qa professional to have a look and to define if everything was delivered correctly
the tested status would help us to make sure that we have developed things as they were planned
and they are now available to be deployed to the environment i would also add the deployment one
meaning that we have verified everything on the dev environment and it is now
going to either stage if we are going to have the user acceptance
tests or directly to production depending on the delivery flow that is accepted on our project
basically you can also change the transitions meaning to permit or to restrict moving from
one status to another but for this particular test project i am not gonna add any additional
permissions okay the workflow is set and it is pushed to our project so we can already use it
so as you see the statuses were not updated yet because simply what you need to do is to go to the
board settings and to add the required columns and the statuses manually okay so click add column and
put the name of the column within and as you see having the same name of the column and
the same name of the status the status is assigned automatically okay let's also check the swimlanes
this is something that you're gonna see on the board it's already
story so i'm not gonna change anything another thing i would change is the
fields within the issues okay so here are all our issue types that are available by default
and here are all the fields that are possible to be used within story points is something that we
would definitely need on scrum projects because this is the major estimation approach that we
are gonna use during our sprint delivery by the way if you would want to know how to actually use
story points on scrum projects make sure to let me know in comments and i will create a separate
video on this As this is a project definitely you would need the team to work on something so first
what we're gonna start from is epic epic is the top level item within the hierarchy of tasks that
we're gonna have on a project let's just imagine that we're gonna have a webapp project this gonna
be an e-commerce project that we would need to build for a client using the wordpress platform
and based on this assumption we're gonna create the appropriate tasks within i'm gonna name the
project like webapp project proof of concept one i'm gonna assign the epic to myself and i'm gonna
set the priority to high i'm not gonna choose this sprint because this is applicable to one of other
projects that i currently have within my jira but for this particular project we're gonna create
a new one so our first issue with the id pmp1 is created now we need to build the hierarchy here
and within the epic we're gonna add stories and for this particular project we would need a few items
to be added in order to build our e-commerce web solution by the way if you can notice i prefer
to use this structure of items meaning first goes the name of the epic then goes the name
of the story and if we go deeper after the name of the story i would add the actual name of the task
now it's time to create subtasks and here is for setting up the environment we're gonna list the
actual task meaning activities list that the team would need to execute in order to get things done
when all the subtasks related to the story are done we could say that we have completed the story
another important thing is every task should have a description a really clear description
that would help the team to instantly define what is expected from them in order to deliver the task
in a proper way other items that i usually add to user stories are what actually is needed and what
is expected as the outcome another feature in jira is that it allows to set the dependencies among
the tasks for instance if some task is dependent or is blocked by another you can easily
add this information to the ticket and you will instantly see what actually should be delivered
first in order to start working on this particular item now what we need to do is to start the sprint
so as long as we are using scrum sprints are the measurable criteria across our milestones
and what we are going to do is to create the first sprint for our project once we have a
sprint created the next step would be to select the user stories for this first sprint let's pick
two from the ones that we have we can easily see the count of story points that were put within
every user story that we have selected for the sprint and not only this at the bottom line we can
also see the overall estimate for the sprint which is the sum of the stories estimates
and voila your board is full of tasks right now and here is where you can see those swimlanes
basically these are your user stories and when you're expanding the swimlane you can see all
these subtasks or subbugs if this is gonna be the case underneath and they're gonna be corresponding
across the statuses that would help you to define the current progress for every story
that was actually the basic actions that you would need to take in order to give your team an opportunity
to start working on a project without limitations or constraints along with that there are a lot of other
cool and handy tools in jira that would help you track the progress and make sure that your
project is on track if you would want me to tell you more about how to use jira and how to exploit
all the great features that you can use within as an it project manager make sure to let me
know in comments i hope that was helpful and if so don't forget to share this video with your friends
and don't forget to give me a like so that this video would help even more people chat soon cheers