CHANGE ADVISORY BOARD - HOW TO MINUTE THE MEETINGS

[hamiltr]

Hello
does anyone have any guideline in terms of the format of the minutes of CAB should look like?
Say 10 changes have been reviewed, should details in basic text be written up for each change or should an export (eg PDF/Excel) from each change record be compiled?
I don't want to spend hours on admin work writing up reams of change detail but there again if the information is available from the change record itself could I not just refer everyone to the 10 change records in our service management tool?
Any advice would be most welcome
thanks
Robin

[UKVIKING]

Robin

IT DEPENDS.

I know it is a trite phrase but it works here

What I did was as follows

I prepare a spreadsheet with the list of changes and have key data baout them - that I want to track.

Then I add a couple of columns - approval, additional actions, conditions

Then I write in the spreadsheet the updates.

I dont takestengographer style notes, but topics or issues stated

Is change approved, Y/N
When to deploy - date / time
who - team named
any conditions - test results, business comms, business sing off
comments / additioanl actions

are the only notes taken,

that, list of participants, and then I update after the mtg all of the records and prepare my minutes report

that's about it
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[aballester]

I would agree with the short and sweet approach to minutes. Recently our organization streamlined multiple practices and reports into a consolidated format. Previous formats were quite verbose (40, 60, 80 page reports were not uncommon) to a single page or 2 at the most so that now most participants and executives can actually review and understand the information in the minutes. The key is to report on what you really need to report on (without all of the extra crap) and keeping the report as simple and readable as possible so that end users will actually WANT to read your report.
javascript:emoticon('')