Creating a Project and Backlog

Creating a Project:

When you click on creating the project tab, you actually see two options pop there, Classic project and NextGen project

two-types-of-projects

To create a classic project we need administration permission but to create the next-gen project you do not need any administration permission.

before creating any backlog, we have to create our project first, Once we have done with creating a project the board has been created automatically.

Now the product owner will identify the use cases and start creating tasks and stories which we need to be done.

So I am creating a new project for demo purpose, go to the default page and select the project and on the right corner you will see the create project tab, just click on that, then in the next page enter the required path and click on the create project.

scrum-workflow-project

Creating the Next-Gen Project:

Next-gen project is the one which we can create this project without any administration permission and also there is an advantage in creating the next-gen project because of the entities and issues types statuses and workflow and the things that we create are only present in the Nextgen project.

And these are not global across all of jira like they are in the classic project and still you can invite your team members to work in the next-gen project,

You can work with them on the next gen project but the benefit of keeping the next-gen project from global is that it frees them up to be created by anyone and you don't have to have jira administrators permission or have them set everything up for you.

let create a next-gen project as Boats next-gen project and if you want to change the template means just click on the change template and select which one you need and click on the select button.

Below the name, you have an Access option just click on that, you will see the drop-down menu, here you can select who can access to your project.

choose-access

And if you click on the advance, you will see the project key as well and then click on create button

project-key

Once you created, by default it will take you to the Board and this is your agile board and one more important thing to keep in mind is that we have only one board in the next-gen for one project.

bngp-board

And also you can star this if you want to access it quickly later on in your start items, just go to the left corner and you will the star symbol and click on that, starred and the recent page will open, in that select the BNGP board and click on the star button.

starred-recent-board

You can also manage some rules here, so just click on the three dots (..), manage rules page will open and click on Add rule

manage-roles-page

Next, the add rule page will open, in that there are actually two options are there Assign an issue to someone and update an issue field, if you select the assign an issue to someone then it will notify you.

Assign-an-issue-to-someone

you can also chnage the column name by clicking on the three dots(...)

change-column-name

And also you can create a new column and exchange the columns by just doing the drag and drop.

And if you click on the project settings, in the details section you can change the project name, access and also project key.

project-details

And if you go to issue types, you can see some issue types and these are really going to live only in the next-gen projects.

issue-types-in-next-gen

If you want to create an issue there is one option on the left side as Add issue type, just click on that and create an issue.

create-an-issue

In the Feature part, you can turn this into backlog or sprints and reports, etc..

feature

Backlog:

The backlog is the one which contains the issues and task for our project, it also contains the sprints, epics, and versions, we can assign the issues and tasks to the sprint.

Here we can create issues, drag and drop the issues and update the issues according to there priorities.

So the backlog has been reflecting on the board immediately after creating the project is as shown below.

Backlog-page

Now you can start creating issues, on the down left, you will see a word Backlog, below that there is a green color drop-down menu is there just click on that, and select the stories or Task you want to create.

Backlog-drop-down

We can't create a Bug here because the bug can be visible only when any testers doing a test on particular build software then he will find a Bug.

Now I am going to create some stories as follow,

Story 1: As a user, he can view courses so that, he can view them.

Story 2: As a user, he can view the contact details, so he can call customer care if required. like that, you can write many stories as you need, but here I am writing for demo purpose, so I am just going to create some more stories just by giving them number instead of wasting the time.

backlog-stories

Now let us create some task now,

backlog-tasks

So we have created so many stories and Tasks over here, now the product owner will go through each and every issue and he will discuss them with the respective teammates and assign them accordingly.

Introduction To Agile Methodology

Time Estimation, Epic, and Versions

Time Estimation:

Once the backlog has been created the product owner will know what are the task needs to be done and he will arrange a meeting with related developers, tester and they will make an estimation of time for each task.

Let us open any stories which you have created and click on the SWP-1, you can see a time estimation if it is not there then the project is not configured for showing the time.

So you need to configure it now, on the left-hand side there will be "+" mark just click on that, jira will display the create issue page, we can also create an issue through this method also but what I have shown you is the easy and shortcut method.

There will be a tab called configure fields, just select the where is my field under that by clicking on configure field.

Where-is-my-field
Once you click on the where is my field, a small dialog box will appear, so just enter your query as Time Tracking, you will get suggestions from the drop-down menu, just select.

time-tracking
Now you will receive a message with a suggested link to solve this problem, so just click on that, in a new tab called configure screen page will open, Enter Time Tracking in the below dialog box.

So that now your screen has been configured with the time estimation.

Configure-screen
To check whether the time estimation has been configured successfully or not, just try to create an issue and check time estimation has given to estimate the task.

time-estimation
Let us add the time estimation for each story, first click on the story and then the story will open on the right side and here you can add the time estimation as shown below.

entering-the-time-tracking

log-time

Epic:

An Epic is nothing but a group of narrative stories, let us see how to create an epic, go to your backlog page and on the left side, you will see a word which is mentioned vertically in that page, just click on that. Now you will see a small window called create Epic.

click on create epic and enter the required paths and then click on create, I have created an epic with the name Home Functionality.

create-epic

Once you create an Epic it will be displayed on the window

completed-epic

And also I created another one another epic with name contact us, once after creating the epics we can assign these stories to the respective Epics, we can just drag and drop the stories into the respective epics.

Assigneing-stories-to-epics

Versions:

Versions indicate the actual version of the software, here versions which are like releases which update to our project and also it represents when a particular version will be delivered to the client, similar to the epics we can also assign stories to the respective versions also.

Just click on the versions in the backlog page and enter the versions name and then click on the create version.

Creating-versions
Once after creating the versions, your backlog page will look like below.

backlog-with-versions-epic

Creating Issues in Jira

Creating a Sprint

Once we have done with creating a backlog and epics, versions, we are all set to create a Sprint, sprint is nothing but time estimation given to the development life cycle, hence the team has to complete the given work within the estimated time.

so depending upon the availability of the developers, we can prioritize and move the issues into the sprint, We can just drag and drop issues to the sprint depending upon the priority, which functionality should be completed first or which functionality delivered to the client first.

There will be a create sprint tab on the right upper corner of the Backlog page, just click on that and enter the required credentials.

Create-sprint
Now you can drop and drop the issues to the sprint and then click on the start sprint.

assigning-issues-to-the-sprint

Now it will ask to enter the sprint name, Duration, start date, and end date, etc..

entering-the-time-tracking

Once the sprint has been created, the backlog page will move to the active sprint and all the issues which we are assigned are in the to-do state.

active-sprint-to-do state
You can do some settings to the board over here, just click on the interface menu, you will see the drop-down options and click on board settings and once the sprint will complete, you can show it as a complete sprint.



Handling Global Access and Use Cases

Working On Sprint

Once the sprint has been created, the developer starts working on it by using the Ticket, currently, this sprint has not assigned to anyone because of it just a demo sprint and I am going to assign this to me itself.

Currently, in this project, we are working with only three flows, but in real projects, there will be more flows like Edit, comment. in progress, to do and after this, there will be one more flow called Deff Complete.


sprint-flow-page

Where Deff complete means, the developer has finished his task and QA can start now, and also Qa can change its status as testing is in progress and once the issues are resolved he will mark it as Done, If he or she may open the sprint, then again it will go to TO Do state

Let us create another story for sprint and add the new story, as soon as you create and add the new story to the sprint, you will see an error message as sprint scope will be affected by this action.


warnin-message

This is because you have already identified that this much section would be covered within this period, so it will show a warning like this, that means it will need more time to complete it.

Search in Jira

Closing Sprint

Let us see how to complete the sprint once we are done with resolving the issues, for demo purpose consider the nine days are over and we are completing the sprint and just click on the complete sprint.

Sprint will show the warning, In the warning message it will list how many issues were completed and how many issues were incomplete and also it will ask us where it has to move the incomplete issues, so just select from the drop-down menu as Backlog and click on complete.

Moving-issues-to-backlog

So it has moved seven incompleted issues to the backlog again.

As soon as sprint completed, it will generate a chart, which contains the list of completed issues and Incompleted issues, below showed chart is having 2 completed issues and 2 incompleted issues.

sprint-chart

sprint-status-report

Ans also jira will represent the issues with an asterisk which we are added to the sprint after the start time.

ssprint-after-start-time

Handling Global Access and Use Cases

Jira Reports

Jira reports helping you to track and analyze the teamwork through the chart of there respective projects.

And it also contains several charts like Burndown charts, Burnup charts, Sprint Report, velocity chart are commonly used charts.

Burndown chart is the widely used chart, this chart is commonly seen in the execution of the sprint, and it will track our activities throughout the project, it will show you the chart against how many amounts of the task estimated in the sprint versus how the time is going.

As soon as the time increases and the duration of the issues increase and the task will decrease

burn-down-charts

Velocity Chart is generally seen by the manager to identify how many tasks our team can do in a sprint. Velocity chart shows the bar graph which shows how much issues we are committed to complete in the given time estimation is represented in the gray color and how much we are completed will be represented in the green color

velocity-chart

As this was a demo project and you may not be able to see the graph structure in the chart.

Reports for Scrum projects

Chart Applies to Purpose
Burndown Chart Sprints

Tracks the total work remaining, and projects the likelihood of achieving the sprint goal.

This helps your team manage its progress and respond accordingly.

Burnup Chart Sprints

Provides a visual representation of a sprint's scope, as well as its remaining work.

This helps your team stay on track.

Sprint Report Sprints

Shows the work completed or pushed back to the backlog in each sprint.

This helps you determine if your team is overcommitting or if there is scope creep.

Control ChartControl Chart Projects, versions, or sprints

Shows the cycle time for your product, version, or sprint.

This helps you identify whether data from the current process can be used to determine future performance.

Cumulative Flow Diagram Any period of time

Shows the statuses of issues over time.

This helps you identify potential bottlenecks that need to be investigated.

Epic Report Epics

Shows the progress towards completing an epic over time.

This helps you manage your team's progress by tracking the remaining incomplete and unestimated work.

Epic Burndown Epics

Similar to the Epic Report, but optimized for Scrum teams that work in sprints. Tracks the projected number of sprints required to complete the epic.

This helps you monitor whether the epic will release on time, so you can take action if work is falling behind.

Release Burndown Versions

Similar to the Version Report, but optimized for Scrum teams that work in sprints.

Tracks the projected release date for a version. This helps you monitor whether the version will release on time, so you can take action if work is falling behind.

Velocity Chart Sprints

Tracks the amount of work completed from sprint to sprint.

This helps you determine your team's velocity, and estimate the work your team can realistically achieve in future sprints.

Version Report Versions

Tracks the projected release date for a version.

This helps you monitor whether the version will release on time, so you can take action if work is falling behind.

Reports for Kanban projects

Chart Applies to Purpose
Control Chart Projects, versions, or sprints

Shows the cycle time for your product, version, or sprint.

This helps you identify whether data from the current process can be used to determine future performance.

Cumulative Flow Diagram Any period of time

Shows the statuses of issues over time.

This helps you identify potential bottlenecks that need to be investigated.

Reports for next-gen software projects

Chart Applies to Purpose
Burnup Chart Sprints

Provides a visual representation of a sprint's scope, as well as its remaining work.

This helps your team stay on track.

Velocity Chart Sprints

Tracks the amount of work completed from sprint to sprint.

This helps you determine your team's velocity, and estimate the work your team can realistically achieve in future sprints.

Reports available in Confluence

If you have connected Jira to Confluence, you can create the following reports in Confluence:

Chart Purpose
Change Log Displays a list of issues from Jira. This list can be static or dynamic, automatically updating as the status of your issues change in Jira.
Status Report The Status Report displays the progress of a Jira project and fix
Comment / Suggestion Section
Point our Mistakes and Post Your Suggestions