Loading Profile...
How big should a project's scope be?
My first inclination was to break out projects according to the areas of our web app: reporting, import widget, profile page, support ticket system, signup process.... however, some have suggested that we should instead have one project for, basically, everything.
I’m undecided
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hi...generally, we try to align "projects" with stable teams, in order to have predictable velocity. Flip is the potential for projects to get very large, and hard to manage. One approach is to maintain a Tracker backlog for a few months out only (or the next couple of releases), and keep longer-range plans outside, for example in a shared spreadsheet, which allows you to react more easily as business priorities change. Also, labels can be very helpful to keep track of related stories - we use them quite extensively.
EMPLOYEE
