Posted: Tue Mar 11, 2008 12:59 am Post subject: MS Access and Change Management
What's your policy for Changes in MS Access databases? We plan to make only big and new projects go as RFCs. Any small fix would go as an Incident. We thought that with the quantity of small fixes that are done every day (new functionalities requested by users, changes in layout, etc.) it would be more convenient to have only big and new projects go as RFCs. Here the word "big" is a bit arbitrary, big is any change that would need to go through a SDLC process (Analysis, Design, blah blah). "New" is any new MS Access database.
What's your opinion / How's it done at your organization?
Joined: Apr 01, 2008 Posts: 12 Location: Salt Lake City, UT USA
Posted: Wed Apr 02, 2008 1:04 pm Post subject: Re: MS Access and Change Management
What's your policy for Changes in MS Access databases?
Irrespective of the technology that an application is based on, I would think you'd want to base your change policy on things like criticality of the applications, number of users and the impact to the business if the application goes offline unexpectedly.
Since MSAccess is a desktop developer tool, the developers that use it generally don't have the same kind of discipline as developers that work with the more traditional development tools (C++, VB, .NET, etc...).
If I might suggest an idea, where an application is critical to the business and the users will get pretty upset if it goes offline, you might get them (the users) to agree to use a release mentality for their changes. Rather than just ripping them out as quickly as they can, bundle them up into a release of fixes/enhancements. Users of critical systems generally understand applying some discipline if they understand that not doing so will impact them getting their jobs done.
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