The goal of this issue is to keep the number of issues in
Short term milestone ideally under 100 tickets.
As part of our effort to focus on Reliability, Security and Performance we want to keep our Short Term milestone under control with a limited and realistic number of issues. This will help maintain our small team agile going forward. There are several problems with long backlog such as inefficiency going through the backlog, triaging, and general lack of focus. This must be changed before it becomes too big an issue.
Short term milestone as of 2014 Oct 13th:
Major(click to see the list) that could be moved to Mid or Long term?
Short term milestone has 242 issues, 121 of which are bugs and 121 are enhancements/tasks. I will go through the list and see how many can be moved to Mid term or longer...
there are also 40+ issues that haven't yet been processed and don't have milestone.
went through 121 enhancements/tasks which is now down to: 94
went through 121 bugs which is now down to 79
Total: 174 opened issues - that's almost good (still have to process those 40+ issues)
After looking at those fifty pending issues we have a total of 204 issues in
Out of those 204 issues we have 44 marked as
We are making progress in our effort to stabilise Piwik
quick update: somehow we can't get down to 100 issues in Short term - 3 months after my last comment here we still have 216 open issues still in Short term.
we need to do something about this: having a realistic
Short term backlog is very important for the product engineering team.
As a first step, I will go through the backlog and move as many issues as possible out of
Short term - for example, for the first time I will move
Mid term. This will be the end of our "no bug policy" but it wasn't fair anyway to announce a No-bug policy and then not actually do it.
there were 216 issues, I did a first pass over moving the least important issues out to Mid term, and we now got 125 issues in Short term
Plus there 110 ungroomed issues with no milestone and likely a few more for Short term.
I'll take another look later how we can make it under 100
Maybe split "Bug" into two section? Critical or not. First should be fixed as soon as possible, second can be moved to "short term bug list".
yes we use
Critical labels for marking important and occasional critical issues.
we made it: 100 issues in the
Short term backlog!!
Out of those:
Job done - this will help a lot users, team members, and product manager, to know/plan for what to work on next :+1: