WEBVTT

00:00:04.590 --> 00:00:06.633 align:center
Hey there, my name is Rohit

00:00:06.653 --> 00:00:08.836 align:center
Mishra and I'm working with PECNC

00:00:09.016 --> 00:00:09.877 align:center
as a Scrum Master.

00:00:09.898 --> 00:00:12.221 align:center
I have been working with PECNC

00:00:12.241 --> 00:00:13.743 align:center
for the past two years with

00:00:13.803 --> 00:00:15.846 align:center
an overall experience of 12 plus

00:00:15.886 --> 00:00:16.106 align:center
years.

00:00:16.767 --> 00:00:17.729 align:center
Today we are going to talk

00:00:17.809 --> 00:00:19.251 align:center
about one of the projects that

00:00:19.371 --> 00:00:20.272 align:center
I have been working as a

00:00:20.292 --> 00:00:20.973 align:center
Scrum Master.

00:00:21.033 --> 00:00:22.856 align:center
The name is Beacon Research.

00:00:23.276 --> 00:00:25.480 align:center
Beacon Research is an annuity driven

00:00:26.000 --> 00:00:28.404 align:center
product which is having 7 plus

00:00:29.165 --> 00:00:32.169 align:center
solutions that actually helps the annuity

00:00:32.309 --> 00:00:32.850 align:center
market.

00:00:33.450 --> 00:00:35.813 align:center
brokers as well as the writers

00:00:36.094 --> 00:00:36.975 align:center
in the US market.

00:00:37.475 --> 00:00:39.979 align:center
The stakeholders at Beacon Research were

00:00:40.019 --> 00:00:41.501 align:center
facing certain set of challenges.

00:00:42.082 --> 00:00:43.784 align:center
They were facing challenges kind of

00:00:44.204 --> 00:00:46.708 align:center
having less quality control and version

00:00:46.748 --> 00:00:47.128 align:center
control.

00:00:47.489 --> 00:00:49.231 align:center
They were not having proper environment

00:00:49.291 --> 00:00:51.274 align:center
mapping where they can do testing

00:00:51.394 --> 00:00:52.015 align:center
and UAD.

00:00:52.456 --> 00:00:54.398 align:center
They were also having their code

00:00:54.619 --> 00:00:57.242 align:center
with an outdated tech stack and

00:00:57.683 --> 00:00:59.265 align:center
is approaching end of life.

00:00:59.986 --> 00:01:02.289 align:center
They also wanted us to approach

00:01:02.349 --> 00:01:03.170 align:center
with a process

00:01:03.320 --> 00:01:05.523 align:center
that allows them to do roadmap

00:01:05.903 --> 00:01:07.386 align:center
and vision planning.

00:01:07.706 --> 00:01:09.488 align:center
With a set of challenges that

00:01:09.568 --> 00:01:12.552 align:center
was provided, Backensea started with certain

00:01:12.593 --> 00:01:14.235 align:center
set of process and policies.

00:01:15.076 --> 00:01:17.399 align:center
I myself introduced the concept of

00:01:17.459 --> 00:01:19.902 align:center
version control and a process for

00:01:19.983 --> 00:01:22.065 align:center
having a QA at various environments.

00:01:22.546 --> 00:01:24.188 align:center
We brought in the environments of

00:01:24.308 --> 00:01:27.573 align:center
QA, UAD, and sandbox for respective

00:01:27.613 --> 00:01:28.073 align:center
purposes.

00:01:28.634 --> 00:01:30.076 align:center
That way it allowed with a

00:01:30.156 --> 00:01:31.939 align:center
proper quality check.

00:01:31.959 --> 00:01:32.900 align:center
We agreed to

00:01:33.130 --> 00:01:35.794 align:center
work with scrum process where proper

00:01:35.834 --> 00:01:39.979 align:center
roadmap based sprints and the iterations

00:01:40.380 --> 00:01:42.082 align:center
can be defined and that way

00:01:42.162 --> 00:01:44.866 align:center
a continuous delivery at regular intervals

00:01:45.167 --> 00:01:47.289 align:center
are reaching to the stakeholders of

00:01:47.370 --> 00:01:48.050 align:center
beacon research.

00:01:48.631 --> 00:01:49.613 align:center
In the due course of last

00:01:49.733 --> 00:01:51.575 align:center
one year beacon research have been

00:01:51.635 --> 00:01:54.539 align:center
gained various services from our team

00:01:54.980 --> 00:01:58.104 align:center
from development devops and qa and

00:01:58.144 --> 00:01:58.505 align:center
design.

00:01:59.086 --> 00:02:00.447 align:center
We have been providing them some

00:02:00.768 --> 00:02:02.290 align:center
cost effective services

00:02:02.390 --> 00:02:04.613 align:center
in infrastructure by the virtue of

00:02:04.673 --> 00:02:07.117 align:center
which they have better managed and

00:02:07.317 --> 00:02:09.180 align:center
cost-effective AWS services.

00:02:09.661 --> 00:02:11.003 align:center
At SSL level, we brought in

00:02:11.183 --> 00:02:12.525 align:center
a free service which is fully

00:02:12.605 --> 00:02:14.348 align:center
automated in today's state for the

00:02:14.388 --> 00:02:17.092 align:center
products that they are using by

00:02:17.112 --> 00:02:18.594 align:center
the virtue of Let's Encrypt.

00:02:19.296 --> 00:02:21.259 align:center
With the right product mindset approach,

00:02:21.359 --> 00:02:23.041 align:center
we are moving ahead with some

00:02:23.542 --> 00:02:25.385 align:center
better endeavors where we will be

00:02:25.425 --> 00:02:27.127 align:center
getting away from the technical depth

00:02:27.648 --> 00:02:28.870 align:center
and tightly coupled code.

00:02:29.140 --> 00:02:30.382 align:center
We are going to bring in

00:02:30.582 --> 00:02:31.704 align:center
rich user experience.

00:02:32.064 --> 00:02:33.887 align:center
We will be moving away from

00:02:34.167 --> 00:02:36.550 align:center
ROR to Angular for certain products

00:02:36.891 --> 00:02:38.012 align:center
in the roadmap.

00:02:38.453 --> 00:02:40.836 align:center
Certain pipeline endeavors, which is in

00:02:40.876 --> 00:02:42.639 align:center
roadmap right now, are kind of

00:02:42.739 --> 00:02:45.142 align:center
CI-CD services, as well as we

00:02:45.202 --> 00:02:48.627 align:center
are talking towards analytics by using

00:02:48.687 --> 00:02:50.590 align:center
NoSQL database architecture.

00:02:51.070 --> 00:02:52.672 align:center
So we are gladly moving ahead,

00:02:52.933 --> 00:02:55.496 align:center
working with Beacon Research and providing

00:02:55.576 --> 00:02:57.199 align:center
the best of our services.

00:02:57.659 --> 00:02:58.160 align:center
Thank you.

