Use of Gemini to manage product development
We are looking to use Gemini to manage both new software versions and manage requests for existing versions.
Product project structure sample Technology.1 release A work package 1 work package 2 release B work package 3 Technology.2 etc.
We would need a page where anybody could log a request/feature/fault but a separate process looks at the issue and decides which version it is allocated to.
Has anyone had any experience in doing this - do we need separate projects to manage the two requirements?
Thanks
Simon
simonw
· 1 |
|
Friday, September 3, 2010, 5:04:16 PM |