Олександр Щедров та Альбіна Тюпа — magic button. can production...

Happy Ever Afters With

CI Workflow

hello!

I am Albina Tiupa

I am a PM at FFW

You can find me at: https://www.facebook.com/albina.tiupa

hello!

I am Alex Schedrov

I am a Team Lead at FFW.

You can find me at: http://www.facebook.com/schedrov

@sanchiz

420+ people11 countries

15 years

Formerly Blink Reaction, Propeople, Bysted, Chainbizz & Geekpolis

WE WORKREMOTELY

Long-long time ago we realized that using

CI workflowin our projects

is 90% of success

Do you know why?

We want all releases to go to production seamlessly and on

time

1.

We want releases to be of a high quality with minimum

post production bugs

2.

We want easily maintain multiple independent

environments

3.

We want development team to be in sync with each other

4.

We want releasing to become an automated routine or a one-

click action

5.

We want to be sure that everything is under control!

6.

Don’t you dream about it all for your

projects??

WE NEED TO CHANGE OUR PROCESS,

IT’S SH*T!

When this book is your team’s guidance

When your team doesn't understandwhat’s going on.

When your team have no code review

When you have lack of QA

When your team members do not follow processes you agreed about

When deployments depend on one person and manual workarounds

So, don’t you want to get rid of that finally?

Caution! Addictive content goes next!

What does CI workflow mean from technical

perspective

1.Environments

● Development/QA environment resemble the production environment

● Isolated features on every build

2. Specifications

● Functional specs for client

● Technical specs for dev team

● Functional/Technical specs developed in advance

● Protect your team

3. Knowledge exchange through code review

● Development techniques and approaches of problem solving

● Quality of the code

● Responsibility for reviewed code

4. Code Driven Development

● Everything in code(configuration, DevOps scripts, updates and etc.)

● No manual steps during deployment

● Responsibility for own code

5. QA

● QA is done before code is merged to ‘master’

● Steps for review in each task

● Manual and automated tests

Even more, steps for review!!!

6. Automate everything

● Anyone can deploy

● Deploy any time and more frequently

● Team members are forced to follow the process

Release/QA process

PM Dashboard

Our lives have been divided into 2 parts:

before CI workflow and

after CI workflow

And guess what?

WE LOVE OUR JOB!

Happy PM has better feeling of completed task or milestone

Happy PM is more collaborative during development cycle

Happy PM can respond quickly to problems and bugreports

Happy Client spends less time bumping into and reporting bugs

can expect deliverables on few versions simultaneously

Happy Client

experiences a short cycle time between idea and usable software

Happy Client

Happy PM works with a highly disciplined and productive team

We decided to share the setup we’re using:

CIBoxhttp://bit.ly/ffw-cibox

thanks!

Any questions?You can find us at:

https://www.facebook.com/albina.tiupa

http://www.facebook.com/schedrov