0% found this document useful (0 votes)
4 views

DevOpsInfo

The document consists of a series of questions aimed at assessing the use of agile principles, automation tools, deployment processes, and collaboration between development and operations teams. It covers topics such as source code management, CI/CD integration, testing processes, and monitoring practices. The responses will help evaluate the organization's maturity in DevOps and software development practices.

Uploaded by

Gaurav Sharma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views

DevOpsInfo

The document consists of a series of questions aimed at assessing the use of agile principles, automation tools, deployment processes, and collaboration between development and operations teams. It covers topics such as source code management, CI/CD integration, testing processes, and monitoring practices. The responses will help evaluate the organization's maturity in DevOps and software development practices.

Uploaded by

Gaurav Sharma
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as ODT, PDF, TXT or read online on Scribd
You are on page 1/ 4

Planning/Automation/Execution

1. Do you follow agile principles?


 Yes
 No
Answer:

2. Are you using any source code repository?


 Git
 Git Lab
 SVN
 VCS
Answer:

3. Are you using any tools for static code analysis?


 Yes
 No
Answer:

4. Are you using any build automation tools?


 Yes
 No
Answer:

5. Are you using automation tools for functional testing, load testing, security testing, and mobile testing?
 Yes
 No
Answer:

6 .Do you use any Continuous Integration(CI) tool to orchestrate your builds?
 Sometimes but not everything is automated
 Critical processes are automated using a CI tool
 All builds are managed using a CI tool
 Don't use CI tool

Answer:

7. How quickly can developers see the results of the integration / unit testing?
 Immediately
 Nightly
 Once in week

Answer:

8.In general, how do applications perform once released into production?

© QASource Confidential
Seller Restrictions: This data shall not be duplicated, used nor disclosed in whole or in part for any purpose.

Page 1 April
9, 2025
 Always as expected
 Sometimes rollback
Answer:

9. How often do you deploy code to production?


 Daily
 Weekly
 Fortnightly
 Multiple times a day
Answer:

10. How do development and operations teams collaborate during a production issue?

 Production incidents are handled by operations staff. Only If all operational procedures have failed to restore
service level, then an escalation process may be started on an exception basis to engage developers
 Dev and Ops do a joint retrospective to review the root cause of an issue once it's resolved. They plan how
to prevent a recurrence
 They collaborate in real time.
Answer:

11. What is your branching policy?

 We keep new work in separate branches and merge only when finished, usually in weeks or months
 We have no branches and develop only in the trunk or master
 We use branches that live for a few days max and commit all changes to the master or trunk at least daily
 None of the above
Answer:

Deployment

12. Are you using on-premise infrastructure or cloud-based infrastructure?


 Yes
 No
Answer:

13. Are you using any configuration management tools or scripts for installing application packages or a runtime
environment?
 Yes
 No
Answer:

14. Are you using any automated scripts to deploy applications in prod and non prod environments?

 Yes

© QASource Confidential
Seller Restrictions: This data shall not be duplicated, used nor disclosed in whole or in part for any purpose.

Page 2 April
9, 2025
 No
Answer:
15. Are you using any orchestration tools or scripts for application life cycle management?

 Yes
 No
Answer:

16. Do you have a separate DevOps team in your organization?

 No
 Some engineers play the role of DevOps engineers
 Have a fully staffed DevOps team
Answer:

17. Are your build and deployment processes fully automated?

 No, neither of them are automated


 Build is mostly automated but deployment is not
 Both build and deployment processes are fully automated
Answer:

18. How would you describe the ability to scale your QA infrastructure?
 Dependent on IT teams for infrastructure needs
 Leverage basic virtualization but still dependent on IT
 Fully virtual independent testing infrastructure
 Leverage cloud based testing infrastructure
Answer:
19. Are your testing processes integrated with CI/CD pipelines?
 No CI Integration
 Basic integration. Leverage CI tool for triggering builds
 Auto triggered builds and automated tags and versioning
 Fully integrated including acceptance tests and performance parameters

Answer:
20. Do you use containers during your development, testing or deployment stages?
 Don't use containers
 Use containers in some stages
 Use containers extensively
 Infrastructure as code
Answer:

21. Quality in digital is all about speed. Are you able to deliver your business needs on time?
 Testing cycles are too long to deliver on time
 Deliver mostly on time but there is scope for improvement
© QASource Confidential
Seller Restrictions: This data shall not be duplicated, used nor disclosed in whole or in part for any purpose.

Page 3 April
9, 2025
 Always deliver on time
Answer:

22. How do you manage code dependencies across teams?

 We track them in a spreadsheet or document


 We use a work item tracking system
 We maintain an artifact repository with the latest binaries and all teams pull from there.
 None of the above/not applicable
Answer:

23. How do your Client roll out new features to users?

 We deploy when the appropriate manager approves.


 We run a full test suite in a production-realistic environment and then deploy
 We use progressive deployment with feature flags or exposure control to determine whether to continue
rollout
 All gets deployed continuously but we use feature flags to control which users have access to new features
in production
Answer:

Monitoring

24. When are developers notified of a broken build?

 When build is created for QA


 When the nightly build runs
 Soon after the code is committed
 No automated notification system in place
Answer:

25. Are you using any tools for application and infrastructure monitoring?
 Yes
 No

Answer:

© QASource Confidential
Seller Restrictions: This data shall not be duplicated, used nor disclosed in whole or in part for any purpose.

Page 4 April
9, 2025

You might also like