Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Short term backlog is too full -> how to keep number of issues lower eg. 100 issues #6430

Closed
mattab opened this issue Oct 13, 2014 · 9 comments
Assignees
Labels
Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Oct 13, 2014

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:

  • 222 issues
  • 48 issues Major
  • 114 issues Bug
  • 46 issues Task
  • 64 issues Enhancement

Proposed steps

  • for issues Bug:
    • Triage all Bugs (click to see the list) and assess whether they are still valid, reproducible, whether they are really important (all our bugs are in Short term)
    • We shall schedule the remaining Bugs to be fixed in next 3-5 releases. Ideally we will come back to our beloved "No bug policy" in Piwik.
  • for issues Task and Enhancement
@mattab mattab added Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. labels Oct 13, 2014
@mattab mattab added this to the Short term milestone Oct 13, 2014
@mattab mattab changed the title Short term backlog is full -> we need to keep number of issues lower eg. 100 issues Short term backlog is too full -> how to keep number of issues lower eg. 100 issues Oct 13, 2014
@mattab
Copy link
Member Author

mattab commented Dec 1, 2014

today the 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.

@mattab
Copy link
Member Author

mattab commented Dec 1, 2014

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)

@mattab
Copy link
Member Author

mattab commented Dec 1, 2014

After looking at those fifty pending issues we have a total of 204 issues in Short term

  • 95 bugs
  • 109 tasks / enhancements

Out of those 204 issues we have 44 marked as Major

  • 10 major bugs
  • 19 major enhancements
  • 15 major tasks

We are making progress in our effort to stabilise Piwik

@mattab mattab modified the milestones: Short term, Piwik 2.11.0 Dec 18, 2014
@mattab mattab modified the milestones: Piwik 2.11.0, Piwik 2.12.0 Jan 6, 2015
@mattab
Copy link
Member Author

mattab commented Feb 19, 2015

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.

@mattab mattab modified the milestones: Piwik 2.13.0, Piwik 2.12.0 Feb 19, 2015
@mattab
Copy link
Member Author

mattab commented Apr 7, 2015

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 bugs to 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.

In Short term will be the most important bugs as well as 1-3 features from our Roadmap (see also #7624)

@mattab mattab self-assigned this Apr 7, 2015
@mattab
Copy link
Member Author

mattab commented Apr 7, 2015

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

@Globulopolis
Copy link
Contributor

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".

@mattab
Copy link
Member Author

mattab commented Apr 8, 2015

yes we use Major and Critical labels for marking important and occasional critical issues.

@mattab
Copy link
Member Author

mattab commented Apr 9, 2015

we made it: 100 issues in the Short term backlog!!

100 issues

Out of those:

  • type breakdown: 42 bugs, 28 enhancements, 26 tasks, 4 pull requests
  • 18 Major issues

Job done - this will help a lot users, team members, and product manager, to know/plan for what to work on next 👍

next step: create the public Roadmap page: #7624 and also related: release a document explaining our vision and values: #7376

@mattab mattab closed this as completed Apr 9, 2015
mattab pushed a commit to matomo-org/developer-documentation that referenced this issue Apr 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

2 participants