1. Gemini resolutions in a 3 server setup environment Addition / ITU / Cohaesio Addition Ver 1.1 26.05.2010

2. Server environments setup Addition Dev env Cohaesio QA env Cohaesio Prod env Addition dev environment is the projects construction site and sandbox environment. Here solutions for issues are developed and their functional implementation is discussed with + verified by the productowner. An approved solution gets packed and made ready to deploy to QA and ultimately production The purpose of the QA environment is to verify that a developed solution can be reproduced 1:1 on the QA and without obvious side-effects to the rest of the website. When the installation has been verified by the product owner as a reproduction from development, the procedure is repeated finally on production

3. Resolutions in a 3 server setup environment Client side instructions

4. Descriptions defines the issue  Gemini basic properties –Description –Priority –Assignment  Basic status indicators –Unassigned: Issue needs attention –Assigned: Issue has been added to the queue –In progress: Issue is being taken of now –Closed: Issue is closed  Good descriptions improves development process –Accurate descriptions on how to reproduce an experienced problem is essential (text, screenshots etc) –Clear instructions on what solution is being requested for development is also a key factor in quick resolution to a problem  Priority –Is used to differentiate relatively between issues and their order of execution. –Priority should be set according to severity for the system / end user- value –Misuse of high priority status’s only decrease the usage of priority indicator as a tool for navigation  Correct assignment helps move issues along more quickly –An issue that has no assignment automatically draws attention to itself. –An issue that is wrongfully assigned can falsely seem ok on the surface and therefore go unattended for a longer period of time.

5. Resolutions for tasks in progress A task in progress can use various resolutions to communicate progress. The above illustration gives an overview of how to interpret when an issue is assigned to the Product Owner with a given resolution attached to it Issue is assigned to P.O Waiting reporter input I have a question… Can’t reproduce I can’t recognize the problem so I need help here Can’t / Won’t fix I understand the problem, but there is no solution for it Deployed on Dev server I have finished the problem and would like you to test and approve my solution Assign back to dev + update description + set resolution to ”unresolved” Or if unable to reproduce the problem close the issue Assign back to dev with answer + set resolution to ”unresolved” Dead end If no new info can change the problem then close/archive the issue Assign back to dev with: a) ”tested on DEV server” b) ”unresolved” with comment on why solution was rejected Quality assurance The issue is solved with the description provided in issue for approval

6. Deploy resolutions If a solution has been approved for deploy, a series of steps follows as described above Addition Dev env Cohaesio QA env Cohaesio Prod env 1. Deployed on Dev server 2. Tested on DEV server 1Deployed on Dev server Dev to PO: “Issue is ready for test on dev environment.” 2Tested on DEV server PO to Dev: “Issue has been tested + approved on dev environment.” -> Dev will then update issue with deploy instructions. 3For deploy Dev to TM: “Issue has been updated with deploy instructions and is ready to be deployed on QA environment.” 4aUnresolved TM to Dev: “Provided solution could not be reproduced on QA environment..?” 4bDeployed on test server TM to PO: “Issue is ready for your test on the QA environment.” 5aUnresolved PO to TM: “Solution not the same on QA as on dev / created a problem.” 5bTested on TEST server PO to TM: “Issue has been tested + approved on QA environment.” 6For deploy TM to all: “Issue has been send to Cohaesio for deploy to production.” 7Deployed on customer server TM to PO: “Issue is ready for your approval on Prod environment.” 8Tested on CUSTOMER server / Customer approval PO to all: “Issue has been approved and can now be closed!” 3. For deploy 4a. Unresolved 4b. Deployed on test server 5a. Unresolved 5b. Tested on TEST server 6. For deploy 7. Deployed on customer server 8. Tested on CUSTOMER server

7. ITU deployment If (when) ITU does development that is being deployed to cohaesio, Addition needs to update backwards to keep dev environment in sync Addition Dev env Cohaesio QA env Cohaesio Prod env 1. ITU deploys own development to Cohaesio QA 2.ITU requests Cohaesio to deploy own development to production servers 3.Using the same packages, ITU then requests Addition to do a backward deploy by supplying files and instructions. 4.Addition performs backward deploy on dev environment 4. 2. 3.

8. Summary, client side If an issue is assigned to me with resolution:  Waiting reporter input –It means someone needs my input  Can’t reproduce –It means that it’s not clear what the issue is about, or maybe it is no longer applicable  Can’t / Won’t fix –It means that a solution for the problem is out of reach  Quality assurance –It means that an answer or guide has been provided in the issue for my acceptance  Deployed on X server –It means that I should test an issue and verify that I want it moved up in the server food chain If I want to…  Indicate that I have answered a question / provided new info –Assign back to x with resolution ’unresolved’  Approve a solution assigned to me for testing –Assign back to x with resolution ”Tested on X server”  Reject a provided solution assigned to me for testing –Assign back to x with resolution ’unresolved’  Close an issue because it’s no longer valid or for other reasons no longer relevant –Close the issue with a comment as to why X = whomever is relevant at the time in question – usually the person who assigned the issue to you last