Your team works in a project that uses only one workflow, a simplified workflow. The configuration of the corresponding Kanban board is shown:Which statement is definitely true?
Answer(s): A
The statement that is definitely true is that bugs can be dragged from "In Progress" to "In Test" on this board. This is because the board configuration shown in the image has two columns: "In Progress" and "Done". The "In Progress" column has three statuses mapped to it: "To Do", "In Progress", and "In Test". The "Done" column has one status mapped to it: "Done". Therefore, issues can be moved from one status to another within the same column by dragging them on the board. However, issues cannot be moved from one column to another by dragging them on the board, as this would require a workflow transition that is not available in a simplified workflow. A simplified workflow is a default workflow that allows any user with the Edit Issues permission to add or remove statuses on the fly. To move an issue from one column to another, you need to use the workflow button on the issue detail view and select a transition that matches the status of the destination column.
Configuring columns, Using a simplified workflow
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(s): 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.
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 projectsWhich board filler query meets these requirements?
Answer(s): C
The board filter query that meets these requirements is (project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic). This query will show all issue types from project BERT except sub-tasks, as well as only epics from project ERNIE. It will not show issues from any other projects, as it uses the OR operator to combine two conditions that specify the project names. The other queries do not meet all the requirements, as they either include sub-tasks from project BERT, exclude epics from project ERNIE, or show issues from other projects.
Configuring filters, Advanced searching - fields reference
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?
Answer(s): D
The solution that meets this requirement is to update the board filter and add: AND (labels !=daily.business OR labels IS EMPTY). This will exclude issues that have the label daily_business from the board filter, which determines which issues are displayed on the board. It will also include issues that have no labels at all, as some issues in your project may not have labels. The other solutions do not meet this requirement, as they either do not exclude issues with daily_business label, or exclude issues with no labels.
Configuring filters, Advanced searching - operators reference
You are reviewing the Velocity Chart for your team and notice that they completed more story points than they committed in their last sprint. You are definitely the only person who can add issues to sprints in your project. How did your learn complete more story points than they committed?
The reason why your team completed more story points than they committed in their last sprint is that someone increased the story point value on an issue mid-sprint. This will increase the total story points completed at the end of the sprint, but not affect the total story points committed at the start of the sprint. Therefore, it will result in a positive scope change. The other reasons mentioned in the question do not explain why your team completed more story points than they committed, as they either do not affect story points at all, or affect both committed and completed story points equally.
Post your Comments and Discuss ATLASSIAN ACP-610 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the ACP-610 content, but please register or login to continue.