Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Atlassian Exam ACP-610 Topic 4 Question 39 Discussion

Actual exam question for Atlassian's ACP-610 exam
Question #: 39
Topic #: 4
[All ACP-610 Questions]

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?

Show Suggested Answer Hide Answer
Suggested Answer: E

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]


Contribute your Thoughts:

Kallie
12 days ago
I hope they don't end up in a Kanban-dango trying to figure this out. Keep it simple, folks!
upvoted 0 times
...
Brittni
21 days ago
I'm just glad they're not using a Ouija board to decide this. That would be a real horror show!
upvoted 0 times
...
Lorita
25 days ago
D is the way to go, hands down. Separate projects for tasks and features is the cleanest solution. Why make it more complicated than it needs to be?
upvoted 0 times
...
Ruthann
27 days ago
Option C with the quick fillers could work, but I'm worried it might get a bit cluttered. Better to have dedicated boards for each issue type in my opinion.
upvoted 0 times
...
Victor
1 months ago
Hmm, I'm not sure about separating the boards. Keeping everything in one project with minimal disruption seems like the best approach to me.
upvoted 0 times
...
Marge
2 months ago
But with option A, they can still track both features and tasks separately.
upvoted 0 times
...
Tanesha
2 months ago
I think option E is the way to go. Kanban for tasks and Scrum for features sounds like the perfect balance.
upvoted 0 times
Aretha
5 days ago
It's important to find a solution that meets the team's requirements while minimizing disruption to their current setup.
upvoted 0 times
...
Felicidad
22 days ago
Using a Kanban board for tasks and a Scrum board for features seems like a practical approach.
upvoted 0 times
...
Breana
23 days ago
I think option E is a good choice as well. It allows for flexibility in managing different types of work.
upvoted 0 times
...
Shannon
1 months ago
I agree, having separate boards for tasks and features will help with organization.
upvoted 0 times
...
Isadora
1 months ago
It's important to find a balance that works for the team, and option E seems to offer that.
upvoted 0 times
...
Dacia
1 months ago
Using a Kanban board for tasks and a Scrum board for features seems like a practical solution.
upvoted 0 times
...
Fidelia
1 months ago
I think option E is a good choice as well. It allows for flexibility in managing different types of work.
upvoted 0 times
...
Denise
1 months ago
I agree, having separate boards for tasks and features will help with organization.
upvoted 0 times
...
...
Malcolm
2 months ago
I disagree, I believe option B would be more efficient.
upvoted 0 times
...
Marge
2 months ago
I think option A could work well for them.
upvoted 0 times
...

Save Cancel