The Grid: Blueprint for a New Computing Infrastructure by Dr. Ian Foster of Argonne National Laboratory and the University of Chicago, and Dr. Carl Kesselman of the Information Sciences Institute and the University of Southern California.
We have requests for software development come in via two avenues.
First, new projects are requested via a Notes database. It is the responsibility of a business liason group to prioritize the requests submitted to that database, and then we (development) just work on the requests in order of priority.
Second, enhancements to existing systems can come in a couple of ways. If a call to the help desk turns out to be something that requires a software change, the ticket (we use Peregrine Service Center) gets transferred to the development group where we copy it into our issue/bug tracking system (PVCS Tracker). If anyone notices a problem with a system under development, test, or pilot, the issue goes straight into Tracker. Tracker lets us assign the issue to different people or groups, track the change history, etc. (just typical bug tracking software). We have procedural checkpoints that make sure all open items associated with a particular project or system are addressed before moving on to the next phase/iteration of development or before elevating.
So in the end, we have one place to look for new project requests, and one place to look for enhancements to existing systems.
Slashdot Mirror
LOL...you've never had good beating, have you?
The Grid: Blueprint for a New Computing Infrastructure by Dr. Ian Foster of Argonne National Laboratory and the University of Chicago, and Dr. Carl Kesselman of the Information Sciences Institute and the University of Southern California.
Morgan Kaufmann, San Francisco; 1999.
I recommend the IEEE Computer Society as well as a subscription to comp.infosystems.www.authoring.*.
We have requests for software development come in via two avenues.
First, new projects are requested via a Notes database. It is the responsibility of a business liason group to prioritize the requests submitted to that database, and then we (development) just work on the requests in order of priority.
Second, enhancements to existing systems can come in a couple of ways. If a call to the help desk turns out to be something that requires a software change, the ticket (we use Peregrine Service Center) gets transferred to the development group where we copy it into our issue/bug tracking system (PVCS Tracker). If anyone notices a problem with a system under development, test, or pilot, the issue goes straight into Tracker. Tracker lets us assign the issue to different people or groups, track the change history, etc. (just typical bug tracking software). We have procedural checkpoints that make sure all open items associated with a particular project or system are addressed before moving on to the next phase/iteration of development or before elevating.
So in the end, we have one place to look for new project requests, and one place to look for enhancements to existing systems.