Use of Team foundation server for Task Backlog.
-
Ok, so TFS is not so good with huge team and different servers? I don't know I am asking, because that's what I need to do, choose a proper source control system. Have you ever used ClearQuest?
If you want a DVCS tool then you should in be considering TFS. Git is by far your best option.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare Home | LinkedIn | Google+ | Twitter
-
We investigated using it for our task tracking and after 15 mins of trying to make heads or tails of it I gave up. It feels like the process of doing sprints and cards and backlogs and burndowns and everything else in the various templates that are offered have completely taken priority over actually - y'know - managing your tasks. Anything that is harder to use than an Excel spreadsheet get's thrown in the bin for us. TFS / VSO has great potential, but not until they focus on the data (ie tasks) instead of the process (ie their overly complicated workflow and terrible UI)
cheers Chris Maunder
Have you had a look at Trello? It's the virtual version of sticky notes on a whiteboard. Perfect for kanban or scrum boards, also works with your phone.
Wrong is evil and must be defeated. - Jeff Ello
-
Have you had a look at Trello? It's the virtual version of sticky notes on a whiteboard. Perfect for kanban or scrum boards, also works with your phone.
Wrong is evil and must be defeated. - Jeff Ello
Jörgen Andersson wrote:
It's the virtual version of sticky notes on a whiteboard
Yes and it made me want to scream. Scrum boards are great when you need to focus on a small number of items for a given sprint. I need to manage a LOT of items across many different business units, and some of them are long (up to 2 years long) projects. I need to keep a list, somewhere, of everything we're involved in with the ability to expand/shrink my temporal focus. What are the 3 projects we'll do this quarter? What top 3 things each department has on their plate this week? Where's out TODO list and what's item #582?
cheers Chris Maunder
-
Jörgen Andersson wrote:
It's the virtual version of sticky notes on a whiteboard
Yes and it made me want to scream. Scrum boards are great when you need to focus on a small number of items for a given sprint. I need to manage a LOT of items across many different business units, and some of them are long (up to 2 years long) projects. I need to keep a list, somewhere, of everything we're involved in with the ability to expand/shrink my temporal focus. What are the 3 projects we'll do this quarter? What top 3 things each department has on their plate this week? Where's out TODO list and what's item #582?
cheers Chris Maunder
With those demands I wonder if you'll ever find something that will satisfy you. I'm having an idea though that I might throw at you, problem is that I'll never find time to do it I'm afraid.
Wrong is evil and must be defeated. - Jeff Ello
-
With those demands I wonder if you'll ever find something that will satisfy you. I'm having an idea though that I might throw at you, problem is that I'll never find time to do it I'm afraid.
Wrong is evil and must be defeated. - Jeff Ello
That's why we wrote Tasks ;) (I'm still thinking of resurrecting it!)
cheers Chris Maunder
-
Hello all, I am doing a small research in my company to switch from ClearCase(IBM's Source Control System) and ClearQuest(IBM's task/project/backlog management system) to Team Foundation server. I till now found out that TFS is much more fast in terms of checking out, checking in functionality and have great in-visual-studio interface, also that it's compare and code review functionality is great. As we use VS-13 and our project is completedly in C#. I want to know what you guys suggest about TFS' Task management. is it reach in features and also have you found out it's drawback? Thanks in advance.
The best feature of TFS is the ability to select a task from the planning side to associate with a check in And then ... you can stop working on one task, save everything (windows, breakpoints etc.) work on anther task, and then save that one, swap between them etc. Of course, we don't use these features because our source is on one TFS server and our planning stuff on another. :omg: :wtf: See text[^] Video[^]
PooperPig - Coming Soon
-
The group I'm in has been using TFS for the last few years and I like it. Previously we used Subversion (which is not suitable for use with code projects) and had no way of tracking work. I do not integrate TFS with my Visual Studio projects, because that's not how I work. I use the Web interface, the command-line, the shell extension, and some utilities I wrote against the API.
-
The best feature of TFS is the ability to select a task from the planning side to associate with a check in And then ... you can stop working on one task, save everything (windows, breakpoints etc.) work on anther task, and then save that one, swap between them etc. Of course, we don't use these features because our source is on one TFS server and our planning stuff on another. :omg: :wtf: See text[^] Video[^]
PooperPig - Coming Soon
Me too, and miss TFS (As I do not get to use it in my company-or rather in my project.) I miss the sheving the pending changes feature and code review work item feature. I belive if you make the tool easy to follow the processes. people we do it, and they will do it gladly.
-
Hello all, I am doing a small research in my company to switch from ClearCase(IBM's Source Control System) and ClearQuest(IBM's task/project/backlog management system) to Team Foundation server. I till now found out that TFS is much more fast in terms of checking out, checking in functionality and have great in-visual-studio interface, also that it's compare and code review functionality is great. As we use VS-13 and our project is completedly in C#. I want to know what you guys suggest about TFS' Task management. is it reach in features and also have you found out it's drawback? Thanks in advance.
Most of the answers so far seem to cover the source code control only. I'm using TFS for years now and never lost anything or had issues with it, but I have very low standards. However, since a few weeks I'm using the TFS ALM features the first time and I must say I like it very much. Working at a company that has no other tools to manage requirements and tasks than Excel, it didn't needed much to make me happy! Nothing against Excel, I still use it, but in a whole different way. TFS ALM allows you to get your Backlog dumped into Excel, update it and publish it back to TFS with the press of a button. Bug tracking etc. is also part of it. If you like to work in Visual Studio or through the web frontend, no problem at all. All the team members have access to it and can update their tasks, read the updated specifications, everybody can see what we are working on, with the product owner I can move user stories to other iterations and everything is updated instantly. Didn't got to the details of having a meaning full burn down chart but it's also a question how far you want to dive into adapting the scrum method. As a project manager my task of keeping the overview got a whole lot easier, developers can see what's next on their to-do, planning and estimation is transparent and my client is happy as he can see what is going on very easy. It's the first project we are doing this way (more than 80 user stories) and we certainly have to get better at everything but I'm sure I'll continue on this road. Drawbacks: Well' as every new tool you have a learning curve but it isn't too steep with TFS ALM. The tool is very powerful and sometimes you can get lost a bit in all the possibilities but I regard this as positive! Hope this helps. Rene
-
Most of the answers so far seem to cover the source code control only. I'm using TFS for years now and never lost anything or had issues with it, but I have very low standards. However, since a few weeks I'm using the TFS ALM features the first time and I must say I like it very much. Working at a company that has no other tools to manage requirements and tasks than Excel, it didn't needed much to make me happy! Nothing against Excel, I still use it, but in a whole different way. TFS ALM allows you to get your Backlog dumped into Excel, update it and publish it back to TFS with the press of a button. Bug tracking etc. is also part of it. If you like to work in Visual Studio or through the web frontend, no problem at all. All the team members have access to it and can update their tasks, read the updated specifications, everybody can see what we are working on, with the product owner I can move user stories to other iterations and everything is updated instantly. Didn't got to the details of having a meaning full burn down chart but it's also a question how far you want to dive into adapting the scrum method. As a project manager my task of keeping the overview got a whole lot easier, developers can see what's next on their to-do, planning and estimation is transparent and my client is happy as he can see what is going on very easy. It's the first project we are doing this way (more than 80 user stories) and we certainly have to get better at everything but I'm sure I'll continue on this road. Drawbacks: Well' as every new tool you have a learning curve but it isn't too steep with TFS ALM. The tool is very powerful and sometimes you can get lost a bit in all the possibilities but I regard this as positive! Hope this helps. Rene
I agree, and have to say, that the TFS is compelling to anyone who ever used it. I have used it in my previous company and fell in love with it, and now I cannot work in other environment. It's like going to Notepad after using VisualStudio :(. However the learning curve involve in this is very less compared to other similar tool, i.e ClearCase, Git, Subversion etc.
-
TFS is better than it used to be and it is more than source control, but that may be where the problem lies. My source control preferences in order are Git, SVN then TFS - unfortunately TFS seems to be the most commonly used in the companies I tend to be involved with. Git and SVN don't have tools built in for managing Agile projects but I wouldn't say that the ones in TFS are great. Many people install Telerik's TFS Work Item Manager to fill in some of the gaps. Personally I'd recommend finding a 3rd party solution (such as JetBrains YouTrack or JIRA) for managing projects - even better if you can get one that can be hooked into check-ins from TFS, Git or SVN. Just about every developer I've worked with dislikes using TFS - me included X|
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
Agreed. Once again, instead of solving a specific problem, Microsoft tries to solve a gamut of them, and doesn't do any piece of it great. That being said, TFS is improving; I haven't had the mystery "oh, the repository only sent me some of the modifications" in quite some time. I don't think the work tracking is very good, but I'm developing and don't have to worry about that much. It just seems cumbersome and not user-friendly to try to use as a time tracking tool. What I hear from the product management types is they don't feel it's great either. Recommend subversion + Jira or FogBugz, some tools which specialize in each problem space.
-
How can you use TFS and not use it? I mean
PIEBALDconsult wrote:
I do not integrate TFS with my Visual Studio projects, because that's not how I work.
VS comes with TFS support build in. How can you not use TFS in VS and use it from outside?
shrknt35 wrote:
VS comes with TFS support build in.
It has support for VB and F# too, but I don't use them.
shrknt35 wrote:
How can you not use TFS in VS
There are things I do with TFS from within VS, but not integrated with with my projects.
shrknt35 wrote:
use it from outside?
Commmand-line, shell extensions, API. Besides, this thread is about Tasks, not code. Tasks I maintain with the Web interface.
-
Hello all, I am doing a small research in my company to switch from ClearCase(IBM's Source Control System) and ClearQuest(IBM's task/project/backlog management system) to Team Foundation server. I till now found out that TFS is much more fast in terms of checking out, checking in functionality and have great in-visual-studio interface, also that it's compare and code review functionality is great. As we use VS-13 and our project is completedly in C#. I want to know what you guys suggest about TFS' Task management. is it reach in features and also have you found out it's drawback? Thanks in advance.
I have used TFS at work now for about 2 years. The task/work item management is OK, I guess. It appears to be quite flexible. The source code control, on the other hand, I find rather horrible. It is dog slow if you have "too many" mappings. Mappings are what TFS uses to associate your local code to a repository in what it calls a "Workspace". You can have server workspaces that are quicker but there are pros and cons either way. TFS seems to constantly check for local changes and *that* slows it down. Having fewer mappings helps but when you work on many bits you don't have much choice. The branching is also strange and the way it manages file versions internally is totally different from the usual SCC software options. It is rather "heavy". Merging between branches is not as simple either. Having used SVN/Git/Mercurial and other task-tracking software such as Jira I can honestly say I would *never* recommend TFS.
-
I have used TFS at work now for about 2 years. The task/work item management is OK, I guess. It appears to be quite flexible. The source code control, on the other hand, I find rather horrible. It is dog slow if you have "too many" mappings. Mappings are what TFS uses to associate your local code to a repository in what it calls a "Workspace". You can have server workspaces that are quicker but there are pros and cons either way. TFS seems to constantly check for local changes and *that* slows it down. Having fewer mappings helps but when you work on many bits you don't have much choice. The branching is also strange and the way it manages file versions internally is totally different from the usual SCC software options. It is rather "heavy". Merging between branches is not as simple either. Having used SVN/Git/Mercurial and other task-tracking software such as Jira I can honestly say I would *never* recommend TFS.
-
EbenRoux wrote:
Merging between branches is not as simple either
I might want to contradict with you about that. I find it rather simple, I wonder, what might be bothering you.
Firstly, let me just say I am not religious about these things :) I use TFS on a daily basis and only moan about it every second day :) Anyway. I used SVN for quite some time (also around 2 years) and the whole global version number, switching, and merging seemed so easy once I understood it. I am not quite on that level yet with git. TFS, however, requires all the mapping and file copying and tight branch coupling. It really just feels so heavy. But that is just my opinion.
-
Firstly, let me just say I am not religious about these things :) I use TFS on a daily basis and only moan about it every second day :) Anyway. I used SVN for quite some time (also around 2 years) and the whole global version number, switching, and merging seemed so easy once I understood it. I am not quite on that level yet with git. TFS, however, requires all the mapping and file copying and tight branch coupling. It really just feels so heavy. But that is just my opinion.