I have a question about this as well. I am a software engineer. We have our department heads turn in technology requests forms with any changes, bug reports and enhancement requests. These get put on a spreadsheet (along with an estimate of hours to complete the request) and they are reviewed by our technology steering committee on a weekly basis. The committee decides what tasks fit the current priorities of the company. They then assign a list of "tasks" based upon the priorities for the company and the list of outstanding requests. These "tasks" must be completed by the following week's meeting. These "tasks" are generally projects (based upon the definition that a project is anything requiring more than one next action to complete it) while some of them are actually just next actions.
If I get a list like this:
(1) Possibility of e-mailing gift certificates.
(2) Group Ordering graphics and changes
(3) There needs to be a cash drawer check before the credit card authorization button is active
(4) Need to add AVS check
(5) Add check for invalid cc # and expiration date.
(6) Authorization button should be inactive until a $ amount is entered
(7) Error: conflicted with column reference FK_payments_gift ID
( Total adjusted if try to delete one of multiple gcs or should have to delete all
(9) Delete button should be inactivated after cc is run.
(10) Should not be able to print gcs until cc approved.
(11) set up automatic cash drawer linkage to gc screen
(12) ability to print GC from the listing screen
(13) ability to search by GC #/cust name/GC amounton the listing screen
(14) List Management for Lead Management
(15) Link to restaurant directly from e-mail push
(16) Group order invite after order has been sent
(17) Great Plains Installation
Now, items 3, 4, 5, 6, 8, 9 and 10 are all single step items (though they may be tied to a specific project) so they are Next Actions.
Items 1, 2, 11, 12, 13, 14, 15, 16 and 17 all require multiple actions to complete.
My problem in figuring out how to manage these has more to do with the fact that as a whole they are a "project" because they belong to "tasks that must be completed by the next Tech Steering Committee meeting" but at the same time, they belong to their own projects. I am concerned that they will fall through the cracks and not get done.
How should I be handling this situation?