Teams using Project A and B currently use their own respective Scrum boards.They must now work together on the same products and issues and in the same sprints.You created a new Scrum board based on this filter:project in (A,B) ORDER BY Rank ASCYou must also check two settings to make sure the teams can access and use the new board.Identify the two settings. (Choose two.)
Answer(s): E,F
Sharing on the board filter: The board filter must be shared with all users who need access to the board; otherwise, they won't be able to view or use it.Project permissions: Users must have the necessary permissions (such as Browse Projects and Manage Sprints) on both Project A and Project B to view issues and manage sprints on the new shared board.
Your team needs a new board that:only shows issues that are actively in progress allows a separate area to prioritize incoming work allows them to release issues from the Done columnIdentify the correct solution to meet these requirements
Answer(s): E
A Kanban board with the backlog enabled meets all the requirements: it shows only in-progress issues (via column configuration), provides a separate area to prioritize incoming work (the Kanban backlog), and allows for releasing issues from the Done column (via version management or Kanban releases).
A team needs a board that meets these requirements:All issues can be moved across the entire workflow on a single view of the board.Issues can be worked in a continuous flow without start and stop dates.Which board configuration meets the requirements?
Answer(s): A
A Kanban board without backlog displays all issues on a single view and supports a continuous workflow without start and stop dates. This setup is ideal for teams using a continuous delivery process, allowing issues to move freely across the entire workflow.
Newly created issues start in the to Do column of your Kanban board. The column has grown too full.Additionally, the team is unable to focus on the prioritized issues they should be working on.Which configuration change will help alleviate both problems?
DEV is a company-managed Kanban project with many statuses.Users should never see issues in Cancelled or Rejected status when viewing their project board.You want to remove the issues from the board but still have them counted in project reports.Identify the approach that satisfies this requirement.
Answer(s): B
Adding a board sub-filter to exclude the Cancelled and Rejected statuses removes those issues from the board view while still including them in project-level reports. This approach hides them from the board without deleting or modifying workflow data.
Post your Comments and Discuss ATLASSIAN ACP-620 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-620 content, but please register or login to continue.