You manage a Scrum project with two development teams.
Issues are associated with each team using a custom field called Jean.
Parallel sprints have been disabled.
Which setup will provide each team with an individual Burndown Chart?
If you manage a Scrum project with two development teams and want to provide each team with an individual Burndown Chart, you can create two Scrum boards using the Team field in their board filters. A Burndown Chart is a report that shows the amount of work remaining in a sprint, based on the issues that are included in the board filter. By using the Team field in the board filter, you can ensure that each board only shows the issues that belong to a specific team, and thus generate a separate Burndown Chart for each team. The other options will either show a combined Burndown Chart for both teams or not use the Team field at all. Therefore, the correct answer is D.Reference: [Creating a board], [Configuring filters], [Viewing the Burndown Chart]
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?
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.
Quang can transition issues from Resolved to Done using the workflow button on issues in his project. However, he cannot drag then from Resolved to Done on the project's Kanban board Identify a possible reason why.
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?
A team currently uses a single project to track both features and tasks. They will be adopting aqile practices, as follows:
* Features will be developed during three week iterations.
* Tasks will be handled based on priority and rank and released incrementally as needed.
they want to use agile boards with minimal disruption to their current configuration. Which solution will meet their requirements?
The solution that will meet the team's requirements of using agile boards with minimal disruption to their current configuration is to use a Kanban board for tasks and a Scrum board for features in the current project. This way, they can use different agile methodologies for different issue types without creating a new project or changing their existing configuration. They can use a Kanban board for tasks to handle them based on priority and rank and release them incrementally as needed. They can use a Scrum board for features to develop them during three week iterations with sprints and backlogs. The other solutions are either not feasible or not optimal for their needs. Therefore, the correct answer is E.Reference: [Creating a board], [Using a Scrum board], [Using a Kanban board]
Devora
6 months agoBurma
7 months agoMichal
7 months agoIzetta
9 months agoMatilda
9 months agoScarlet
11 months agoThomasena
1 year agoAllene
1 year agoLeota
1 year agoAntione
1 year agoRonna
1 year agoPedro
1 year agoGearldine
1 year agoNana
1 year agoAnnita
1 year agoYuriko
1 year agoKrissy
1 year agoHelene
1 year agoFidelia
1 year agoGlen
1 year agoShayne
2 years agoLucy
2 years agoDonette
2 years agoJoseph
2 years agoCelestina
2 years agoMagnolia
2 years agoVallie
2 years agoDalene
2 years agoPage
2 years agoMerilyn
2 years agoHortencia
2 years ago