Your team uses Story Points for estimation and tracking.
You performed several actions in the active sprint.
Which two actions are reflected as scope change? (Choose two.)
Answer : C, D
The two actions that are reflected as scope change are dragging an estimated story from the backlog to the sprint and modifying the estimate value on a committed story. Scope change is a measure of how much work was added or removed from a sprint after it started. It is calculated by comparing the total story points committed at the start of the sprint and the total story points completed at the end of the sprint. If you add or remove issues from a sprint, or change their estimates, you are changing the scope of the sprint. The other actions mentioned in the question do not affect the scope of the sprint, as they do not change the amount of work planned or done in the sprint.Reference: Viewing the Velocity Chart, Scope change
You want to create a new Scrum board with the following requirements:
* Show all issue types from project BERT but do not show sub-tasks in the backlog
* Show only epics from project ERNIE
* Do not show issues from any other projects
Which board filler query meets these requirements?
Kim needs a single dashboard gadget that displays the following information for issues in her project:
* the total count of all issues
* the total count of each issue type
* the distribution of each issue type as a percentage
* a graphical chart display of that percentage
Which gadget meets this need?
Answer : E
The gadget that meets Kim's need is theIssue Statisticsgadget. This gadget displays the collection of issues returned from a filter, broken down by a field. Kim can configure the gadget to use her project as the filter, and the issue type as the field. The gadget will then show the following information for issues in her project:
the total count of all issues
the total count of each issue type
the distribution of each issue type as a percentage
a graphical chart display of that percentage
The other gadgets are not suitable because:
TheHeat Mapgadget displays issues from a project or filter, grouped by a statistic type, in a heat map format. Issues can be grouped by any statistic type (e.g. Status, Priority, Assignee, etc). However, this gadget does not show the total count of all issues, nor the distribution of each issue type as a percentage.
TheTwo Dimensional Filter Statisticsgadget displays issues from a filter in a table format, where each cell shows the number of issues for a given combination of two statistics types (e.g. Status vs Priority, Assignee vs Issue Type, etc). This gadget does not show the total count of all issues, nor a graphical chart display of that percentage.
TheFilter Resultsgadget displays the results of an issue filter on the dashboard. This gadget does not show any summary or breakdown of the issues by any field, nor a graphical chart display of that percentage.
TheIssues in Progressgadget displays all issues that are in progress and assigned to the user viewing the dashboard. This gadget does not show any information about other issues or issue types in the project, nor a graphical chart display of that percentage.
Some issues in your project have labels and others do not.
Some tasks in your project are identified by a distinct label: daily_business. You need to prevent these issues from being displayed on the team's Scrum board
Which solution meets this requirement?
Your team failed to meet their last sprint commitment and you want to investigate further. You need an agile report that:
* shows you a list of the incomplete issues in the sprint
* allows you to quickly view that list in the Issue Navigator
Which report meets this need?
The team requests that you update the name of your project. What impact will this have on Jira?
You need to assign team members to view code commits in the DEV project. An excerpt of the DEV permission scheme is shown.
Which two project roles must they be granted? (Choose two.)
Answer : B, C
Two project roles that must be granted to view code commits in the DEV project are:
Developers
Administrators
According to the image you sent, the View Development Tools permission determines which users can see development information from tools such as Bitbucket, GitHub, FishEye, and Crucible. This permission is granted to the Project role (Developers) and the Project role (Administrators) in the DEV permission scheme. Therefore, users who are assigned to these roles will be able to view code commits in the DEV project.
The other options are not correct because:
Users do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.
Sprinters do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.
Managers do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.