Posted: Fri Feb 22, 2008 11:05 pm Post subject: Version Control for MI
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.
- 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?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum