representatives, not authorize changes, but to schedule and sequence. f. ENABLE PEER REVIEW OF CHANGES i. Require peer reviews, not external board approval ii. Peer review help improve overall quality, provide their fellow team members to identify issues 3. Define changes which qualify as high-risk and require SME review 4. If a change is too large to reason about, split it up g. POTENTIAL DANGERS OF DOING

is to find the error as early as possible, in the fastest category as possible ii. Later stages require more scarce and complex environment to detect and reproduce issues iii. When an error is found Release – when a feature is made available to customers. 1. Release of functionality should not require changing our application code iv. By separating the actions, release becomes a business decisions

following an established process; can be pre-approved 2. Normal changes: higher-risk changes that require review or approval from change authority. Often times this a board which lacks the required expertise