You Manage three team-managed Scrum projects. You want to create a single board that displays the progress of the active sprints in all team-managed Scrum projects and their burndown. Identify the correct board type to use.
A. Team-managed Scrum board
B. Company-managed Kanban board
C. Company-managed Scrum board
D. Team-managed Kanban board
The correct answer is:
A. Team-managed Scrum board
Explanation:
If you manage three team-managed Scrum projects and want to create a single board that displays the progress of the active sprints in both projects and their burndown, you should use a Team-managed Scrum board.
Team-managed Scrum boards in Jira Cloud are designed for Scrum projects and offer a collaborative approach to project management. They allow you to manage backlogs, plan sprints, and track progress using Scrum practices. Team-managed Scrum boards also provide the flexibility to include multiple projects on a single board, making it easier to view and manage work across different projects.
In summary, a Team-managed Scrum board is the correct board type.
Question #2
In Jira Cloud, you manage Software project and a board that is used by 3 teams.
The teams present new requirements:
Team Alpha wants the ability to see only issues where status is scoping
Team Bravo wants the ability to see only issues where the label is Audit and status is Review
Team Charlie wants the ability to see only issues where the component is Legal.
Which configuration change meets the requirements of all 3 teams?
A. Create swimlanes
B. Create quick filters
C. Modify the board sub-filter
D. Modify the board colums
E. Modify the board filter
The correct answer is:
B. Create quick filters
Explanation:
In Jira Cloud, the best configuration change to meet the requirements of all three teams is to create quick filters.
Here's why:
Modifying the board filter: This wouldn't be ideal because it would force everyone to see the combined filter, mixing all teams' issues. This might not be desirable for team clarity and focus.
Modifying the board columns or sub-filter: Neither offer filtering capabilities based on multiple criteria across different fields like the teams need.
Creating swimlanes: This would only group issues based on a single field like component or assignee, not a combination of fields like status and label.
Creating quick filters: This is the most efficient and user-friendly approach:
Create three quick filters:
Filter 1 (Alpha): JQL: status = "Scoping"
Filter 2 (Bravo): JQL: label = Audit AND status = "Review"
Filter 3 (Charlie): JQL: component = Legal
Share the filters with the relevant teams: You can share them directly with team members or make them public depending on your security preferences.
This solution offers several benefits:
Individual views: Each team has their own filter, maintaining focused views.
Flexibility: Users can easily switch between filters based on their needs.
No board modification: The board remains unchanged, preserving its layout and configuration.
Dynamic solution: You can adjust the JQL queries in the filters as requirements evolve.
Remember to name the filters clearly and share them accordingly for optimal team accessibility and ease of use.