Story Points
1 Story Point is equal to _____hour of Work.
1
What is a Sprint? How long are our sprints?
A sprint is also known as an iteration – it is some specific interval of time (usually two weeks that is dedicated to a planned amount of work that has to be completed by the team and made ready for review.
For which Issue Type (Epic, Task, Subtask), is a business justification required?
Epic
How should we be filling out the "description" for our task/story?
For global data
We need to create a centralized place for team documentation.
So that we can easily find and access information and resources for our team.
TRUE/FALSE - an additional assignee to an issue type will also get credit for the # of story points logged.
FALSE - each individual should create their own task because they will not be getting credit for these story points even if they are an “additional assignee.”
If we underestimate or overestimate our story points, is it worth going back and changing it, or can we leave it?
What is an Epic? And how long do they typically last?
Epics are project level items that should have a major deliverable at the end, typically a quarter
Which of these fields are mandatory for an Epic?
Summary, Description, Buisness Justification, Log Work, Story Points, Due Date, Affects Version, Priority, Assignee
Everything EXCEPT log work and story points.
Why would we use subtasks? What are they for?
Subtasks are just breaking down the task into different subtasks and will allow you to log in story points for each of those separately. They can help you in terms of distributing your story points to multiple tasks under a big task.
TRUE/FALASE - Subtasks can be rolled over to the next sprint.
FALSE
When should we be logging story points when a Jira Issue is created? Does it matter?
The expectation is to being logging story points when a Jira issue is created or at the beginning of the sprint. This is beneficial for both yourself and team as it allows you to lay out the scope of your project and forecast how much work for both yourself and team we are projected to complete in the sprint.
What is a burn down chart? When does it make sense to use these?
This is a tool to visualize the story points completed throughout the sprint. Given this, in order for it to be effective, it requires people putting in their story points before the sprint begins and close them as they make progress. If you are interested in doing it for yourself, you are welcome to do so.
Which of these fields are mandatory for a Task?
Summary, Description, Buisness Justification, Log Work, Story Points, Due Date, Affects Version, Priority, Assignee
All except Buisness Justification
What does the option "Log Work" in the dropdown menu used for? Does it affect your reported story points?
Logging work can be helpful for you to keep track of what you’ve done for your task or project or even story pointing. This won’t affect the actual story points accounted but can be used to see how well you are story pointing and estimating story points.
TRUE/FALSE - you are able to copy and create an existing issue along with its details including fixed version, summary, and description.
TRUE - you can do this by utilizing the "clone" option, under the more drop down menu for an issue.
When logging in story points for a task/story with sub tasks, where do we log the story points? (in the actual task/story, in the subtasks, or both?)
Either the actual task/story, OR the subtasks. You don’t want to double count your story points. So if using subtasks, and you’re tracking story points there, do not also put in a value for “original estimate” in the larger task.
What is the backlog? Why do we use this?
The backlog acts as “a to-do list” and acts as a space to keep track of tasks that you want to do in the future.
You should use the back log to:
Which of these fields are mandatory for a Subtask?
Summary, Description, Buisness Justification, Log Work, Story Points, Due Date, Affects Version, Priority, Assignee
Everything except Buisness Justification
What are we allowed to put into Jira? What work is being captured other than what is in Jira?
Anything you spend 1+ hour on (including tickets that don’t get resolved in our bucket), that is not being captured through ADSK, SDSK, DRQS, JFLO and EQIX - these are things being captured that are NOT on JIRA.
TRUE/FALSE - When rolling over an issue, you still get credit for the work you've done for that issue in the sprint you're rolling it from.
FALSE - you will only be getting “credit” for it in the sprint that it is completed in.
When putting in story points, what # do we capture? (estimate, or changes to estimate after)
We are looking at the # of story points before the ticket is closed out.
Define what a Story/Task is? What is the difference between a task and a story?
Stories/Tasks define the actual work that needs to be done.
•Stories tend to refer to functionality that will be visible to end users
•Tasks tend to refer to the actual work that is done by one person
What are the team fields we should be filling in? (*hint there are 5)
Labels (e.g. EQ, FI)
Fix Versions
Original Estimate
Acceptance Criteria
Epic Link
What if we get a task/project in the middle or end of the sprint and we can’t complete it before the sprint ends? What should I do?
This is going to depend, you can roll it over to the next sprint, if you are pretty sure you are going to complete it in the next sprint. If you are unsure if you can complete it the sprint you are rolling over it over in, then create two separate tasks.
TRUE/FALSE - You can always change the # logged for story points.
FALSE - you can only change this up until you CLOSE out the ticket. After you close out the ticket you are unable to make any other changes.