My team is responsible for a specific type of database infrastructure in our large organization.
The team's work can be roughly divided into three categories:
This is work aimed at improving our systems, making the team's work or management easier, developing applications, tools and automations, reducing amount of problems in production infrastructure, etc. This category mostly consists of projects which would take a single person between two weeks and several months to complete.
Designing and building an infrastructure for a client inside the organization. Working closely with the client, understanding their needs and designing a suitable database infrastructure. This kind of work can also take a single person between two weeks and several months.
Incoming day-to-day events
Unplanned requirements from the team. This includes unexpected faults in production, requests for small changes in a production database, etc.
I would like the emphasis in the team to be on the first category - internal projects, because I believe that most of the pain in production and everyday work will be gone as a result of this work. And so, I would like us to be able to work consistently and effectively on such projects.
At the same time, we have to satisfy incoming requirements and long-running client projects.
Advice and thoughts on a suitable management framework for my team, and how it would be implemented would be welcome.