TWiki> Main Web>GridAdminInstructions>ChangeControl>ChangeControlComments (01 Jul 2008, RobertWoodcock)EditAttach

Change Control - Comments

Comments about the ARCS ChangeControl policy. Added here by the CommentPlugin.

Comment Signature Date/time
I'd like to see some changes to make the process lighter weight for changes with low impact, so such changes can still be recorded and reviewed, but made on a shorter timescale.

This is already mentioned in the proposal under Review: "the level of impact may affect how detailed this review should be", but needs to be developed and reflected in the Schedule/Notification section.

It may be useful to develop a set of Standing Change Authorizations to encourage people to use the process. If every change needs be announced, discussed and scheduled, either changes will take too long, not happen or the policy not adhered to. Probably no change will be made until it is an emergency and the procedure must necessarily be relaxed.

Perhaps the following is a good start.

Low impact changes
review - one (other) ARCS staff member
Approval - Manager or Team leader except for changes with Standing Authorization
Schedule/Notification - Change Logged to a visible area (ie make it discoverable)

Medium impact
review - two (other) ARCS staff members
Approval - Manager or Team leader except for changes with Standing Authorization
Schedule/Notification - Mail to developers, Change Logged to a visible area

Higher impact
As proposed (at r8)


Also the process should allow for unplanned changes to move from a broken state to a fixed state. The term 'critical' used near "Proposed Date" should probably be changed, given that elsewhere this refers to 'critical impact'. Perhaps what is needed is a measure of Priority with Urgent changes needing minimal up-front process but a strong review process after the fix. 		GarethWilliams 30 Jun 2008 - 15:36
As an NCRIS community leader it is good to see the ChangeNotes and the review process. It will be interesting to see how the Twiki workflow holds up when in use. We tried twiki for our iteration planning previously and the limited search and and reporting ability tripped us up as we got larger so we moved to Jira.

If a member of the community using the ARCS services has an important event coming up and can see a Change Note that impacts that, how do we communicate that back to ARCS to request a possible re-schedule or work around?

That's only happened a couple of times in the last 6 years in our area but its always handy to know, just in case. 		RobertWoodcock 01 Jul 2008 - 11:37
Edit | Attach | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | More topic actions
Topic revision: r3 - 01 Jul 2008 - 01:37:46 - RobertWoodcock
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback