...
- Anyone can create a Draft.
- A Dev Team Representative (up to the team – for example the Dev Lead, PO, Scrum Master or QA Lead) can change status from Draft to Submitted.
- The Dev Team Representative should be the person who will be available to answer questions.
- Should be submitted at least two weeks before it’s needed. Ideally four.
- See required information.
- AWS Cost Review Group can change status from Submitted to Approved or Denied
- See approval process.
- Kitfox or dev team (?) can change status from Approved to Active
- See activation process.
Monitoring Existing Environments
...
- Dev Team. Who will be using the environment?
- Purpose. Specific feature(s) being tested? One-liner.
- Modules. Primary module(s) related to the purpose of the environment.
- Expected Start Date
- Expected End Date. How long will the environment be needed, once available?
- Or perhaps, during what flower releases’ development will it be needed?
- Data Set / Size. Mark mentioned that we should know the data set in order to size the environment appropriately.
- Justification
- Cost Management Plan
Justification
- Expand on the purpose as necessary. Why is this new environment needed?
- Are there any existing environments serving the same team and/or modules? If so, explain why they are not sufficient for this need.
- Cost estimates: a) monthly and b) total for the life of the environment.
- Are there any past (or still existing) environments that were used in a similar manner, such that this environment would likely have similar monthly costs?
- Impact / risks if the request is declined.
...