11 / 31
4th. WEEK
3th. WEEK
2nd. WEEK
1st. WEEK
4th. WEEK
3th. WEEK
2nd. WEEK
1st. WEEK
No planned cutdowns during work hours
MONTHLY
1
UPDATE
0
CUT DOWN
realized. It integrates the whole process from determining
requirements and planning project to code development and
management and also from managing the targets during
coding to deploy releases automatically. With the new
structure, we focus completing the deployment processes
with zero-downtimes.
By this means, our target is to manage the requests of the
people, institutions or insurance companies who use our
services better and to meet these more rapidly, more reliable
and free of errors.
the release plan. If there are any improvements that can be
made as a result of these evaluations, we apply them to the
software development life-cycle.
With all this work, we develop software applications that
are better tested and have more stable releases with less
inaccessibility. When we review the SBM service availability
reports, it is stated that systems are ready and accessible
over a rate of 99%. These results give us enjoyment as we
are rewarded for our efforts and our team gets excited to do
better.
We aim at managing life of a software application through
governance, development and maintenance. With applica-
tion life-cycle management project that has been started
and is planned to finish this year, an end-to-end solution
3rd–10th of each month at 19:00 p.m. and the same
release is deployed to live production environment on the
first Wednesday between the 17th–24th of each month at
22:00 p.m. We announce release plans to the institutions
and insurance companies that use our services at minimum
three days before. This gives them opportunity to make their
plans if they have any work that can be impacted. Deploy-
ment processes is monitored with a process management
application which has been developed as an in-house
project. It allows planning new releases or bug fixes. Many
statistical reports can be taken from the application, such
as number of deployments, new requests or errors that are
We have determined delivering continuous and reliable
services as our primary purpose. With this purpose, we have
rearranged our deployment processes that are a part of the
software development life-cycle. Now we deploy software
releases twice a month, once to the stage environment and
once to the live production environment.
In the previous process, we used to deploy the releases
twice a week and this caused services to be inaccessible
while updating applications although they were planned
releases. The possibility of errors that occurs in these
releases was higher and the cost also increased if the error
was critical.
Along with the new process we deploy the new release to
stage environment on the first Wednesday between the
We Improved SBM Software Development Processes
PMP,
Software Development
Manager
Cüneyt
GÜL
ARTICLE 11