Change management
Contents
ART-DECOR Change Management
Overall process
Intro
The central activities around ART-DECOR, its concepts and methodology, development and practice are done by the ART-DECOR Expert Group (ADEG). On a constant pace new features and functionalities are realized into ART-DECOR to meet current and future demands of the ART-DECOR user community.
Process and statuses overview
To capture new feature requests, a structured process is designed. It’s main purpose is to manage expectations and be transparent in the steps to be taken to get from a feature request to working ART-DECOR functionality. Below you’ll find a blueprint of the process and the applicable statuses.
Further explanation on the most important process steps follows below.
Intake request
Submit request
The submitter should register the request. See: Reporting issues
Initial impact analysis
ADEG will make a first estimate whether the request can be processed within the applicable boundaries (functional/technical) of ART-DECOR. If needed an expert is consulted.
Analysis
Decide how to solve
ADEG decides what the appropriate and possible solutions are for the submitted request. Optionally an external supplier can be consulted.
Describe impact
ADEG will add the impact per possible solution needed for the decision making process.
Decide and prioritize
Decide per impact analysis
ADEG decides whether a change is accepted in a expert groupmeeting. Here you’ll find who’s part of this expert group: ADEG
Prioritize
Based upon the perceived importance of the request and it's impact on ART-DECOR , the request will get a position on the ART-DECOR backlog. In general, items that are higher on the list will be part of a release sooner.
Inform submitter
After a decision is made by ADEG, the submitter will be acknowledged.
Publish backlog
Since we think it’s important to be transparent and to manage expectations we make our backlog publicly available. You can find our backlog in our Ticket system.
Plan
Make release proposal
Based upon the available resources and the current backlog a proposal for releases is made. This proposal is presented within ADEG. Per request an indication will be given whether the request can be part of regular maintenance or extra budget is needed.
Regular maintenance or extra budget
ADEG will decide which requests will be part of a regular maintenance release and which requests need extra funding. If extra funding is required the submitter will be asked for additional budget.
Compose release
Based upon the proposal and the committed extra funding, the release is finalized and composed by ADEG.
Publish release overview
Besides every individual request submitter, the ART-DECOR community is informed that a new release is planned. Overview of our releases can be found at: Release_channels.
Build & Test
Build, Test and Deploy Test Environment
Based upon the composed release and the impact analyses per request, developers will build, test and deploy new functionality. If needed (to be decided by ADEG) an external supplier can be contracted to deliver.
Optional: Involve submitter in Testing
In some cases it’s desired that the submitter is involved in testing the requested new functionality. This to be decided by ADEG.
Approve release
After testing is finished and based upon the reported results, ADEG will decide what requests will be deployed to production. If requests cannot be deployed into production, ADEG will inform the submitter and the specific request must be rescheduled into another release.
Production & deploy
Pre-release communication
Once a release is approved, ADEG will inform the ART-DECOR community when the scheduled release will be built and which issues will be included into the release. The backlog will be updated. On overview of our releases can be found at: Release_channels.
Pre-deployment communication
ADEG maintains the following ART-DECOR instances:
- art-decor.org
ADEG maintained instances will show information on scheduled release deployments on their main website. Note that this will only affect ART-DECOR instances that are maintained by ADEG itself. Any other instances are outside the scope of this communication.
