A team is using a GitLab board and wants to make sure that work is not started before it is ready. They want to use the board to signal when an issue is ready to be picked up. What is the most effective approach?

Assign issues to developers as soon as they are created.

Use a 'Ready' list on the board and move issues there when they are ready to be worked on.

Use the issue description to note when an issue is ready.

Add a label called 'Ready' to issues that are ready to be worked on.

A support team uses a GitLab board to track customer requests. The team notices that issues often sit in the 'Doing' list for days without any visible progress. They want to use the board to identify this problem early. What is the most effective way to achieve this?

Set up an automation rule to move issues from 'Doing' to 'Done' after a set number of days.

Add a 'Blocked' list to the board and move issues there when they are waiting on a customer response.

Use board columns to represent the team's workflow and regularly review the board to spot issues that have been in 'Doing' for too long.

Create a separate board for each support agent so they can manage their own queues.

A team is using a GitLab board to manage a project. They want to ensure that the board reflects the current state of work at all times. What is the most important practice to adopt?

Let the project manager be the only person who updates the board.

Move issues to the appropriate list as soon as their status changes.

Review the board at the end of each week to summarize progress.

Update the board lists daily during a stand-up meeting.

A team is using a GitLab board to manage a project with a mix of bugs and feature requests. They want to visualize the flow of both types of work on the same board. The board currently has lists for 'To Do', 'Doing', and 'Done'. What is the most effective way to distinguish bugs from features on the board?

Add a 'Bug' list and a 'Feature' list to the board and move issues between them.

Add labels 'bug' and 'feature' to issues and use the board's label filter to toggle between them.

Use different colors for bug and feature issues by changing the issue title.

Create separate boards for bugs and features.

Which of the following is a key benefit of visualizing work in progress on a GitLab board?

It provides a clear view of the current workflow, helping the team identify bottlenecks and improve flow

It eliminates the need for regular team meetings

It guarantees that all tasks will be completed on time

It automatically generates performance reviews for team members

GitLabCertified Agile Portfolio Management Associate

Domain 3Objective 3

Visualize Work in Progress GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE Practice Questions (Page 2)

Part of the Visual Workflows with Boards domain, which makes up ~18% of our current practice bank.

16questions here

4free pages

1concept

Questions 6–10

6application · medium
A team is using a GitLab board and wants to make sure that work is not started before it is ready. They want to use the board to signal when an issue is ready to be picked up. What is the most effective approach?
Select an answer first
7application · medium
A support team uses a GitLab board to track customer requests. The team notices that issues often sit in the 'Doing' list for days without any visible progress. They want to use the board to identify this problem early. What is the most effective way to achieve this?
Select an answer first
8application · medium
A team is using a GitLab board to manage a project. They want to ensure that the board reflects the current state of work at all times. What is the most important practice to adopt?
Select an answer first
9expert · hard
A team is using a GitLab board to manage a project with a mix of bugs and feature requests. They want to visualize the flow of both types of work on the same board. The board currently has lists for 'To Do', 'Doing', and 'Done'. What is the most effective way to distinguish bugs from features on the board?
Select an answer first
10foundation · easy
Which of the following is a key benefit of visualizing work in progress on a GitLab board?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by GitLab. “GITLAB-CERTIFIED-AGILE-PROJECT-MANAGEMENT-ASSOCIATE” is a trademark of its owner, used for identification only.