How to Quality Gate Software?

While measuring the software quality of 8.000+ projects daily for large multinationals, TIOBE has helped many organizations configure and maintain software quality gates in their development processes. With that experience, they have created a set of best practices when it comes to setting up quality gates in your organization:

1) What quality metrics to gate?

2) Where to gate in the software development process?

3) Should you gate against an absolute or relative baseline?

4) Should you go as far as blocking deliveries when quality gates fail? (the answer is yes, but only under certain conditions!)

This presentation will provide insights for anyone looking to introduce quality gates in their organization or improve their existing ones.

Nutzen für den Teilnehmer:
This presentation will give hands-on advice for software managers or team leads who wish to introduce quality gating in their organization or want to improve their current quality gating procedures. Quality gating is one of the best-automated ways of preventing bugs from slipping into the field, and is a best practice for any company that takes the reliability, security and maintainability of their product seriously.

Behandelte Problemstellungen:
How do I introduce software quality gates in my organization?

What factors should I take in mind when configuring them? Think about metrics, but also where in the processes gates should be placed.

How do I ensure I have buy-in from the rest of the organization if I want to start quality gating? Gates help increasing quality, but can have an adverse affect on release times in the short run. How do you make sure that engineers are OK with that?

Vortragssprache: Englisch
Level: Fortgeschrittene
Zielgruppe: Software Development Managers and other stakeholders that determine a companies software quality strategy

Unternehmen:
TIOBE Software BV

Drs. Paul Jansen