Version Control for MI

[UrgentJensen]

Guys,

I've got one this time...

The question is partly process and possibly technology specific, I'm mostly not sure about the latter of those two.

Scenario:

- A Crystal report development team doesn't have tight (if any) version control. The impact of this is that if they were looking to change a database then they wouldn't be 100% sure what reports might be affected. Yup, you read that right the first time!

- Reports are developed ad hoc and without business analysis having been done previously to structure the requirements. Therefore a new report is produced every time (creating hundreds).

- There is therefore enormous pressure on the team to churn out reports quickly and UAT is left solely to the customer to organise.

- Feedback from customers suggest the success reports being right first time is unsurprisingly very low.

What configuration/version data do I need to capture on change requests forms to make the team start addressing the versioning and structure of their back end management processes?

Is there anything Crystal specific I need to know or do generic principles still apply?

Look forward to your replies.

UJ

[UKVIKING]

When I used to write crystal reports formats for reporting

I would write a word document that would explain what tables, fields, and any formula that are used in the document

I would treat that as a CI (for reporting)

I would have a section for what the report produces and for whom as well
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

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

[UrgentJensen]

Thanks John, I'll have a think about those ideas.

UJ

[UKVIKING]

In addition, i would screen capture the table relationship structure to see the relationships
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

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