| || |
Process to capture defered work
Im new and hope you can give me some advice. I work within a development group and currently the way we work means that to deliver a release on time we sometimes take the quicker route to deliver. We intend to pick these things up later, and usually react as and when we need them, but worse, we only remind ourselves of them when we need them as we uncover the same things we already knew about!
Id like to setup a process for capturing these pieces of work and the associated info so that we can always plan to incorperate them in the next applicable project.
Im not sure how best to capture this info, and what info to capture...also are there any free tools to capture this sort of thing?
Re: Process to capture defered work
Well when I'm working on a project and am creating my BR/FS I have a section for Future Requirements and Deferred Items.
Also, our company has a system for enhancement requests and post project the future requirements and deferred items get entered into that so that they can be included in the prioritization meetings that occur with IT and business.