Team Standards for Work

Development, Infrastructure & Applications Group (DIAG) Policy

Reviewed for FY22


This document elaborates the general framework of common, core expectations of work at Columbia in the Libraries; it describes the team's consensus standards and expectations for work within the DIAG portfolio. This document should provide clarifying detail to what generalized expectations from the organization, e.g. Quality of Work and Teamwork, mean in the specific contexts of the team and department. These standards & practices are referred to in our job descriptions as "work within team standards".

Columbia University Common Expectations

Columbia University sets out a Core Competencies framework to characterize professional expectations of all employees.

  • General Columbia Policies and Guidelines

  • Columbia Core Competencies

    • Adaptability

    • Business Acumen

      • "using one’s understanding of major business functions, industry trends, and own organization’s position to contribute to effective strategies and/or tactics"

    • Collaboration

    • Effective Communication

    • Continuous Improvement

    • Customer Focus

    • Effective Decision Making

    • Drive for Results

    • Facilitation of Change

    • Initiative Towards Action

    • Innovation

    • Effective Planning & Organizing

    • Quality Orientation

Columbia Libraries Common Expectations

In addition to the Columbia University expectations for all employees, the Libraries identifies a set of core skills and professional expectations that form the basis of our professional evaluations.

  • Job Knowledge

  • Teamwork

  • Initiative & Innovation

  • Effective Communication & Interpersonal Skills

  • Adaptability & Flexibility

  • Problem Solving Skills

  • Focus on Patrons & Colleagues

  • Operational Efficiency

  • Quality of Work

DIAG Team Standards and Expections

Viewing the Libraries' core competencies through the lens of our portfolio establishes the team's standards for our work.

  • Collaborative development, including revision control and constructive code review

  • Cross-training and support within the team, department, and with systems administration

  • Automated testing and deployment where possible

  • Style conformance & paradigmatic/idiomatic code (object-oriented, functional, etc) appropriate to project; project documentation and work/issue tracking

  • Ability to diagnose and remediate performance issues, using benchmarking and tuning tools as appropriate

  • Ability to develop requirements and work within received project management paradigms, such as agile or waterfall