Assess the Maturity of your Software Engineering function
Curious about the maturity of your engineering process? Taking this quiz and help you understand where your team is at with their practices in relation to the industry. The quiz is divided into 3 sections and should not take more than 10 minutes to complete. We've included "Other" across various questions, so you can include comments, e.g. if you feel a question may not apply to your engineering team.


We are GDPR compliant in how we handle your details. We will not share your details with 3rd parties or use it for marketing purpose unless you have explicitly provided your consent
2

Please share your email. This is so we can provide feedback in relation to your answers*

Clear selection

Are you are happy to be contacted regarding Tech Amigos consulting services*

Clear selection
Section 1/3 Continuous Integration
In this section, we explore the developer process, from working on code, to software being built and tested.
11

1.1 What proportion of source code for your engineering team's applications are under version control?*

Clear selection

1.2 What proportion of your engineering team's cloud/infrastructure configuration is under version control?*

Clear selection

1.3 Generally, what's the average CI pipeline duration for applications worked on by your engineering team?*

Clear selection

1.4 Do PRs for your engineering team's applications result in test/build/deployment?*

Clear selection

1.5 How reliable is your engineering team’s CI pipeline for building and testing applications?*

Clear selection

1.6 Generally, what is the test code coverage for the applications?*

Clear selection

1.7 What branching model is predominantly used for application codebase repos?*

Clear selection

1.8 How easy is it for your engineering team to run your primary application locally?*

Clear selection

1.9 If running connected services / distributed transactions - how easily can your engineering team identify sources of performance issues in Production?*

Clear selection

1.10 How easily can your engineering team onboard services? i.e. provision your application in a AWS cluster or in a AWS lambda service, with supporting infrastructure and CI/CD pipelines*

Clear selection

1.11 How quickly can your engineering team offboard services? i.e. appropriately teardown where your application has been set up in environments and decommission associated infrastructure and CI/CD pipelines*

Clear selection
Section 2/3 Continuous Delivery
In this section, we explore the deployment process to take locally tested software to the target deployment environment (like a EKS cluster in AWS)
7

2.1 How often does your engineering team deploy code to Production?*

Clear selection

2.2 How long does it take your engineering team to go from code committed to code base, to successfully running in Production?*

Clear selection

2.3 How long does it take your engineering team to restore a service running your application when a fault occurs?*

Clear selection

2.4 How often do production releases by your engineering team result in a degraded service, outage or rollback?*

Clear selection

2.5 How often to problems in Production releases result due to differences in test data? This relates to how representative test data is of data used in Production*

Clear selection

2.6 Are rollbacks for deployments reliably automated?*

Clear selection

2.7 How easily can you evolve APIs and functionality without impacting teams/users?*

Clear selection
Section 3/3 Observability
In this section we explore your organisation's observability setup and your ability to proactively monitor your services and react easily and quickly when an issue occurs with rich logging that aids debugging
7

3.1 Do you have deployment status tracking for your engineering team?*

Clear selection

3.2 Once applications are deployed, does your engineering team have access to logs in one place?*

Clear selection

3.3 Does your engineering team have access to distributed tracing? This refers to monitoring applications in one place, to easily pinpoint cause of failures*

Clear selection

3.4 Do you have alerting is place in relation to applications? e.g. notification on auto-scaling event*

Clear selection

3.5 Is anomaly detection implemented for your engineering team’s applications? This would help identify deviations from expected patterns*

Clear selection

3.6 Do you have custom metrics available in relation to your engineering team’s operations? This refers to bespoke KPIs, which may relate to CI/CD and other performance metrics.*

Clear selection

3.7 How established are security measures for your engineering team? (e.g. vulnerability detection, RASP - Runtime App Self Protection)*

Clear selection

get in touch

Contact Us

   London

Office 4123, Wework
2 Minster Court, London
EC3R 7BB

+44 203 488 8438

   Bucharest

Appartment 1, Number 7
Ipotesti Street, District 4
Bucharest

+40 373 78 44 98