You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
So in Agile/Scrum its considered bad to have bugs, and production bugs are killing some of my team's velocity. We've recently started using portfolio to plan out several things, and we are starting to put all items in that the teams are working on, but they will not show up in the plan (yes in the sprint backlog) unless they are estimated which leads me to the question of..
In Agile/Scrum.. Do you estimate bugs? Or how do you treat them efficiently from a planning (and portfolio plan) standpoint? Any different than the Product owner prioritizing them? Do you estimate them?