I just had a little discussion about this with a few coworkers but we did not come to a conclusion yet. We have a bunch of projects that are actively maintained and developed using scrum, with fixed two week sprints, TFS backlog integration, etc.
We also have a separate project, called
Mobiltec.Framework, which is intended to be an extension to the default .Net framework (most of our projects are C# projects). This utility project is intended to support every other project in the company with general functionality not bound to any specific product, and is located in it's own TeamProject in TFS, independent of any other projects.
We are in the process of starting anew with this one, in a migration to TFS 2013, and I immediately wondered:
What TFS process template will I use with this?
This is obviously specific to TFS, but I think the question stands generic enough: what is the best method to use to develop such on-demand utility project? Scrum makes absolutely no sense to me for it. Features are rarely added to it, and it is quite stable. There is no concept of sprint, and we don't have a special team to handle the project at all (any developer in the whole company could theoretically add things to it, if they are not product specific).
I feel there should still be a backlog of sorts with tasks / user stories mapped to it to at least track what is being done, but I fail to see how I should integrate this in the whole agile pipeline. Should I just completely ignore the 'iterations' idea (both conceptually and in TFS) and just develop and release directly from the main source, creating user stories and bugs along the way?
Is there an example of a project like this, in which the functionalities are all on demand and there is no intrinsic concept of sprints or iterations, on which I could base our project on?