Agile Collaborative Team (ACT)

An Agile Collaborative Team (ACT) is a cross-functional team charged with exploring a critical strategic challenge that will transform the way we work and/or deliver services.

What an ACT does:

  • Provides a mechanism that allows us to continue to transform our organization.
  • Intentional vs. ad hoc.
  • Embeds cross-functional thinking by design.
  • Informs or transforms strategy (vs. a project, which operationalizes strategy).
  • Offers opportunities for collaboration and professional development.
  • Breaks down organizational silos.
  • Creates opportunities to share processes and learning across One IT.

Agile Collaborative Teams: High-Level Process Map

ACT high level process map

Details of this process are still be finalized but here is the high-level portions of the process:

  • Ideas are submitted to the Executive Leadership Team (ExLT).
  • Topic selected by the ExLT via a defined prioritization process.
  • Creation of 2-3 ACTs per year that are:
    • Strategic
    • Timely
    • Impactful
    • Relevant to the campus strategic goals
  • ACT team formed, deliverables set and budget allocated by the ExLT.
  • Team selected via a combination of nomination and selection.
  • Work entails ideation, data gathering, analysis, benchmarking, and possible use of pilots and consultants.
  • ACT provides recommendations to the leadership team about organizational change, technology change, and/or investment.


How will ACTs be formed? Approximately how many people do you see on an ACT team? Will they involve people outside our organization?

It will depend on the topic but we will want to be sure SMEs (Subject Matter Experts) for all facets of the topic are present to provide their knowledge and experience to the group. Formation of teams will be determined for each topic to intentionally include line staff. ACTs may involve individuals who are seeking professional development on a specific topic, or could include people outside our organization (campus partners, stakeholders, or customers/end-users) for additional perspectives.

How will we integrate our DEIB focus into ACTs?

We will work to ensure that our ACTs are balanced and have diversity of all kinds included. Throughout our ODP work, we have been intentional about considering DEIB impacts as we design our new organization. Last year we integrated DEIB best practices into our hiring processes and we are committed to continuing to build and nurture a diverse and inclusive culture. This includes building DEIB into our ACTs as well. 

Are ACT teams permanent, semi-permanent, or are they temporary, task-oriented teams?

ACTs are temporary, for a defined period of time. The length of time will depend on the topic being explored.

What sort of expenditures would be budgeted for during the ACT and will the budget be IST funded?

The budget will depend on what the ACT is and will be funded by IST.

When do you anticipate the rollout of ACTs?

We plan to start the creation  of our first Agile Collaborative Team (ACT) in the fall, although the work of the team may not begin until the new year.

ODP Process Advisory Committee (ODP PAC)

This committee advises the CIO on the project’s process but does not make decisions about the future organization or personnel assignments.

Jenn Stringer

AVC for IT and CIO

David Greenbaum

Project Consultant

Liz Marsh

Executive Director of Strategy & Partnerships and Chief of Staff

Liz Marsh

Executive Director of Business Operations

Gert Reynaert

Project Manager

ODP Project Team

This team supports the project through phase two to gather and analyze information about organizational strengths and weaknesses and campus IT services and functions.

David Greenbaum

Project Consultant

Gert Reynaert

Project Manager

Rita Rosenthal

Communications Manager

Clarissa Fermin

Administrative Officer

Stephanie Dunn

Executive Assistant

Isaac Mankita

Business and Finance Analyst


If you have questions not already addressed in the FAQs, please send them to Gert Reynaert