Can anyone shed some light on best practices of when / where/ how to establish the scope of the Release in the Agile Development Lifecycle model?
Our problem seems to be that we can never get to the point when we can nail down what the scope of the release is. When we do, it seems to be last minute and I am sure that this is not the best method for testing.
I have installer experience and currently working on build tool like Buildforge for carrying out daily builds and further creating installers using installshield.
In my organisation we have a separate group SCM which comes under our team BRT but have different responsibility to manage SCM tool. We use clearcase and clearquest in our organisation.
I have been offered to work in IBM Rational admin role for build and release. I am confused between admin task and build engineer job to create build script for different project and managing build tool such like build forge. In SCM admin task, we have responsiblity like project creation,VOB Migration,multisite,Managing rational server and other task related to SCM admin.
Can any one suggest scope of what role is more preferable?
Input from the people on this forum would be really valueable for me.