You're struggling to align database engineers and agile teams. How can you foster seamless collaboration?

Most of the database work (except regular maintenance) can be included in sprints so that DB work is aligned with other deliverables and application teams.

I have seen this play out in many ways, but the most effective I have witnessed lies in the strictest sense of cross-functionality. Having database engineers who can review code, write unit tests, documentation, or otherwise participate in software engineering activities. It can be very light-weight stuff. Then have software engineers who can write basic stored procs, etc. This allows for the most flexibility and, combined with reduced user story sizes, can be a highly effective approach. Once implemented, all of the work can flow naturally within the sprint.

Aligning database engineers with agile teams has been a challenge I’ve faced more than once. From my experience, open communication is key. Regular joint meetings where both teams discuss goals, timelines, and potential bottlenecks help everyone stay aligned. Encouraging database engineers to participate in sprint planning and retrospectives can integrate them into the agile process. Using shared tools for tracking tasks and progress also helps create visibility. Most importantly, fostering a culture of respect and understanding for each team's expertise can turn collaboration struggles into success.

El éxito de un proyecto depende de una comunicación efectiva, un seguimiento adecuado de tareas, reuniones ágiles y claridad en los requerimientos. La integración de los ingenieros de bases de datos en el equipo ágil es crucial, permitiéndoles participar en reuniones diarias y sprints para anticipar problemas y contribuir con su experiencia técnica. El seguimiento de tareas mediante herramientas como Jira. permite que todos los miembros del equipo tengan visibilidad del progreso y detecten riesgos. Debemos tener claridad en los requerimientos. Si los requerimientos no están bien definidos desde el principio, el equipo podría malgastar tiempo en construir algo que no cumple con las expectativas. .

Invite DB team to daily stand-up meetings. Include respective DB team members in meetings, chats where DB related stories are discussed. Idea is to keep DB team about ongoing and upcoming work, architectural changes and get their inputs where needed.

Database work should be includes in sprints as user stories, This would bring the DB team on agile board and they will visibility to overall ongoing dev work as well as others will have visibility of DB work. This would help to get DB side perspective in designing application features or enhancements like performance, storage optimization etc.

To be in line with agile teams, DBAs should communicate well and know what sprint goals are. Rather than working in isolation, it may be helpful to involve DBAs in sprint planning sessions. This gives them an opportunity to learn about every requirements in advance and deal with possible problems concerning databases. Thus, during a sprint aimed at enhancing customer onboarding experience, schema alterations or optimizations for fresh data fields could be planned by the team responsible for databases. Such a proactive method prevents sudden blockages and encourages cooperation among different units thus ensuring that database changes are considered at the beginning of projects.