Care *ok*
Building custom software is expensive. To ensure that your investment pays off for as long as possible, you must take good care of it. Over time, minor functional changes are likely to occur, as well as small bug fixes, protection against new security threats, and so on. Our care package handles this for you. For companies, government administrations & organisations who want to maintain their software solution, the Care Package is a Kunlabora service that keeps your software solution in good shape and extends its life cycle, unlike other services that do not take end-to-end ownership, work less purposefully and are less time oriented. *review*
Title of body section *in te vullen*
Building custom software is expensive. To ensure that your investment pays off for as long as possible, you must take good care of it. Over time, minor functional changes are likely to occur, as well as small bug fixes, protection against new security threats, and so on. Our care package handles this for you.
For companies, government administrations & organisations who want to maintain their software solution, the Care Package is a Kunlabora service that keeps your software solution in good shape and extends its life cycle, unlike other services that do not take end-to-end ownership, work less purposefully and are less time oriented. * to be reviewed* deze zin "unlike other services that do not take end-to-end ownership, work less purposefully and are less time oriented." staat zowel bij Launcher, Amplifier en Care beschrijving; ik ben niet zeker van de waarde van de zin, zeker niet op de 3 services. Het lijkt ook op kritiek op onze competitie ipv een focus op onze positieve punten of onze waardes.
Zoals suggestie bij Amplifier bv ... --thanks to our deeply embedded sense of propriety, goal-orientated mindset and collaborative approach. ( -- en eventueel link naar cultuur pagina?)
Timeline & details
Our maintenance team takes your software solution under its care. *to be reviewed* Our maintenance team takes care of your software solution. (under care is eerder supervision van mensen)
The team is cross-functional. *to be reviewed*
Product deliverables
Together with you we look into small functional changes and bugs that may occur. *to be reviewed** In collaboration we analyse/look into issues and possible refinements
We monitor and implement the technical updates your application needs. *ok*
To ensure we stay aligned with your business needs and constraints, regular interaction with a representative from your organisation is maintained. *ok* "we maintain regular interaction..." is better
Care *ok* benefits
In good shape. *ok*
Our care package keeps your software in good shape with the latest framework & security updates. ***or: Our care package maintains your solution with with the latest framework & security updates
Extended Lifecycle. *ok*
While your application is being used, new insights arise and the world around your organisation evolves. Small changes in the application may enable you to keep your solution aligned with these changing requirements. *ok** or simply: ...can keep your solution aligned..instead of may enable you to keep your solution aligned
Phasing out. *ok*
When the application reaches the end of its lifecycle, decommissioning strategies are investigated and pursued by the maintenance team. *ok*
How it works
Step 1. Intake *ok*
We present our way of working and adapt it to your organisation. In addition, we make the maintenance context of your application more concrete: how are users experiencing the application at the moment? Do they run into issues? Are small functional changes to be expected? And so on. *ok*
Step 2. Organise *ok*
Your application comes under the wings of the maintenance team of experienced software development experts with complementary skills. Together we determine how we will collaborate, how issues are reported, when and with whom service meetings are held, etc. *ok*
Step 3. Maintain *ok*
We carefully keep your software solution in good shape, fix bugs that may occur and implement small changes, aligning the business value of your application with what your users need. We maintain a clear and transparent communication flow with you so you know how we are keeping your software healthy. *ok*
Step 4. Next Steps *ok*
While the life cycle of your software is extended, at some point you may want to expand or replace it with a new application. Take a look at our Service Blueprint, Demonstrator, Launcher or Amplifier services. We are happy to help. *ok*
Extras *ok*
- Taking external software under our care: we can also maintain software which was not developed by our teams. During the intake step, functional and technical knowledge about the application is shared and transferred. If it is not yet the case, we automate the build and deployment pipelines, as well as the infrastructural setup. The intake report documents an application assessment, the risks and may suggest some efforts to increase maintainability, e.g. introducing or extending the automated testing framework, refactoring pieces of the code, or updating functional, technical or operational documentation. It may be useful to install application monitoring tools and follow up on application performance, or conduct health checks of the application. These activities may be registered in the maintenance backlog of the application and taken up during the maintenance phase. - Independent quality assessment: when taking software under our care, certain quality conditions need to be met. Sometimes it may be valuable to have this quality assessed by a third, independent party: we can refer you to a suitable evaluator. *ok*
