Overview

This is a set of ground rules to follow when developing for Yale's ServiceNow.

Yale runs on a weekly release cycle. Any dev work given to Fruition will be for the next cycle(s) (i.e. 2+ weeks ahead). We need developers to use the description field in update sets to make work traceable; see details below.

Contact david.backeberg@yale.edu w/ any questions.

Process

• Yale tech lead makes enhancement request via Fruition's SN instance
• Yale tech lead will schedule weekly meetings for follow-up/questions.
• Fruition will develop in yale's dev instance https://yaledevelopment.service-now.com/

Policy

• Fruition should let Yale know if anything will take more than 2 weeks of development time.
• Yale should provision any new accounts for Fruition developers.
• Follow update set naming convention: YYYY/MM/DD - #
• Follow update set description convention for first line: [R|D]### - FRU####### - [Module]: [summary]
• You must close your update set on the same day you opened it; fulfillment of a requirement can span multiple update sets.
• Any manual updates that go with one or more update sets must be communicated in the enhancement request.