Responsible go no go decisions

Quality gate is the approach to make transparent and semi-formal decision to go to next stage of the project or to complete the current one. Before a build will be shipped to customers team follows simple checklist:

  • Do we have a testable build of our great software?
  • Was code reviewed?
  • Were unit and automatic tests passed?
  • ...

Avoid of information overload

DevOps board do it's best and tries to deduplicate the same issues, thus you will get a single issue with high "Times repeated" value found on the same environment and product version. But there is a possibility to get huge flow of incidents when using proactive errors and exceptions handling.

  • Build with a bug can affect many...

Get focused on unhappy customers

Environments are used to execute an application could be very dissimilar. Different browsers for web-apps, different OSes for server-apps, specific plugins or addons could incite your application be unfriendly.

You can't find it during testing locally, but fortunatelly you can simply identify unhappy customers with help of the following:

Kanban for Self-management DevOps Teams

Finally you did it, you made a technical launch of your service and now your team is in transition to support stage. You had launched well tested minimum viable product and now it is time to listen to your customers, evolve and implement required features, fix issues your team didn't find before.

You find that...

Making Technical Debt Visible to your Team

The common reasons of every software has bugs are complexity and uncertanity. It doesn't matter were user requirements not clear enough or 3rd party component was used. It is hard to predefine how your software will behave on production with real data, how your software will interact with the environment and what will be impact of real...

Tracking Is Better Than Notifications

Usually your team use hardware of software monitoring tools. They send notifications when something goes wrong, e.g. CPU level is very high or memory level is very low. These alerts are sent by emails or SMS to make the responsible person aware of trouble with hardware...

DevOps for SaaS Developers

When implementing a service it is not about code only, but more about code execution on production. You deal with dozen of scripts, middleware, operating systems and servers. Usually a service consists of many components and every of them should be checked for availability, unhandled exceptions, errors and any kind...

Technical Support is Part of DevOps Activities

What kind of issues does your team meet when the service is launched? Most likely there are alerts like lack of CPU or memory resources, performance issues or broken components. Also you have bugs and exceptions reported from exception monitoring tools. All this happenes because of scripts and exception handlers your team built into monitoring infrastructure...