Skip to content

Instantly share code, notes, and snippets.

@durbon
Last active June 9, 2023 11:58
Show Gist options
  • Star 15 You must be signed in to star a gist
  • Fork 6 You must be signed in to fork a gist
  • Save durbon/5d896ef82c0c57765b0a11ce2086dd0a to your computer and use it in GitHub Desktop.
Save durbon/5d896ef82c0c57765b0a11ce2086dd0a to your computer and use it in GitHub Desktop.
Este listado de temas cubre un amplio abanico de asuntos que nos interesa evaluar dentro del equipo https://medium.com/@durbon/developer-survey-recopilando-la-opini%C3%B3n-de-los-desarrolladores-76384a0347bb

1. Development environment

  • How would you rate the development environment in team? (Use the [1-5] scale)
  • How would you rate the project Settings needed to start to work? (Use the [1-5] scale)
  • How would you rate documentation of the necessary tools? (Use the [1-5] scale)
  • How do you rate the team’s current onboarding process? (Use the [1-5] scale)
  • Do you think we have enough tools to work with? (Use the [1-5] scale)
  • What tools are you missing in order to be more productive at work?

2. Code

  • What is the level of satisfaction with the current codebase? (Use the [1-5] scale)
  • How do you feel the current code affects you in delivering work on time and with sufficient quality? (Use the [1-5] scale)
  • Which parts do you think need to be refactored as a priority?
  • What parts of our architecture do you think should be modified?
  • Any comments or further complaints?

3.Code Review

  • How satisfied are you with Code Review in team? (Use the [1-5] scale)
  • How do you value the benefits of code reviews as a piece of development within the team? (Use the [1-5] scale)
  • How would you rate the pace and flow of Pull Request review? (Use the [1-5] scale)
  • Please write any comments about the problems you have encountered in the PRs code review process.
  • Please write down any comments or suggestions you think we should apply to improve our Code Reviews and Pull Requests.

4. Testing

  • How would you rate the quality of the testing environment in team? (Use the [1-5] scale)
  • How would you rate the execution of our Unit tests? (Use the [1-5] scale)
  • How would you rate the execution of our UI tests (Espresso or whatever similar right now)? (Use the [1-5] scale)
  • What problems have you usually encountered with the test environment? Any problem with CI or your local environment?
  • Please write down any comments or suggestions you think we should apply to improve our testing environment

5. Staging

  • How satisfied are you with the test environment we have at company? (Use the [1-5] scale)
  • Can you trust that staging has correct data to test certain features? (Use the [1-5] scale)
  • What is the level of staging stability according to your experience developing in this environment? (Use the [1-5] scale)
  • What is your level of knowledge about…? (Use the [1-5] scale)
  • Please write down any comments or suggestions you think we should apply to improve our staging environment.

6. Continuos Integration

  • How would you rate the CI environment in team? (Use the [1-5] scale)
  • What’s your overall satisfaction level with Jenkins? (Use the [1-5] scale)
  • Any suggestions about current Jenkins implementation?
  • What’s your overall satisfaction level this tool…? (Use the [1-5] scale)
  • Any suggestions or problems that you have had to address with this tool..?
  • What’s your overall satisfaction level with Github Checkers before merging any branch? (Use the [1-5] scale)
  • Please write down any comments or suggestions you think we should apply to improve our Continuous Integration environment.

7. Release Process

  • How satisfied are you with the app release process? (Use the [1-5] scale)
  • How do you rate the time from when a PR is created or integrated until it is available in a release? (Use the [1-5] scale)
  • How would you rate the coordination between GL and PM/TL product teams? (Use the [1-5] scale)
  • Do you think the app release process is agile enough?
  • Please write down any comments or suggestions you think we should apply to improve our release process. Either at the product or technical operational level.

8. Tracking & Crashes metrics

  • How do you rate the tools we have for tracking ? (Use the [1-5] scale)
  • What is your level of knowledge about these tools? (Use the [1-5] scale)
  • How often do you consult any of these tracking tools? (Use the [1-5] scale)
  • Have you found it easy to follow up on a mistake in a production crash? (Use the [1-5] scale)
  • Please write down any comments or suggestions you think we should apply to improve our tracking tools.

9. Documentation

  • How would you rate the documentation we have right now in team? (Use the [1-5] scale)
  • How important do you consider the documentation in the team? (Use the [1-5] scale)
  • What problems have you usually encountered with the lack of documentation?
  • Any idea or suggestion in order to improve the documentation?

10.team

  • What is the level of happiness in the team? (Use the [1-10] scale)
  • Level of satisfaction with the work done by the team (Use the [1-5] scale)
  • Do you think team coordination is appropriate? Daily? Meetings? Sync? (Use the [1-5] scale)
  • Please write down any comments or suggestions you think we should apply to improve the team in the future.

11. Working remotely

  • How satisfied are you with working remotely? (Use the [1-5] scale)
  • Do you think we have the tools to work remotely efficiently? (Use the [1-5] scale)
  • Any comments? Trouble in meetings? Trouble in understanding?

12. Future Development

  • Choose 3 areas where you think we should improve
    • Transversal features.
    • Architecture & Code Standards
    • Design Standards
    • Tech Debt
    • Tooling
    • R&D: Tech Proof of concepts
    • Documentation
    • Open Source
    • Security
  • What technologies, libraries or framework would you like to integrate into the project?
  • What projects do you think the core team should tackle?
  • Any idea or suggestion for future developer surveys?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment