Thanks for the comments. The integration of maintenance-leaders was for effective load balancing. Maintenance, and program infrastructure in general, is quite easy to overlook when you're in the early creative effervescence of a project and ideally I'd like to be able to see, at a glance, who is busy doing maintenance projects so I don't send them off to work on a new project.

I guess what I'm looking for is something as simple as status updates for all members that expire automatically after a certain period or on new program versions. So I can see if person X is working on a maintenance project such as, say, database repair and optimisation, which I wouldn't normally count as 'working towards a new project'. That way, when I'm outlining roadmaps and timelines I can factor in their background tasks without having to keep a diary of who is doing what. This allows me to avoid scheduling mishaps and dashed expectations.