Skip to main content

Software Project Management: Work Item Database

Hmph...Team System's work item database sounds awfully similar to SourceGear's SourceOffSite Collaboration Edition. You create a bug - when you check in code, you identify the bug number and can update the issue as fixed or not.

I, for one, wish that SourceGear would offer more in the way of their collab edition. It sounds like VS Team Edition is going to be way out of the market for many development teams.

Software Project Management

Comments

Game Geek said…
Team System is not designed for the small, independent developer (an updated Source Safe will be available for that), but for large, corporate dev shops.
Andrew MacNeill said…
True, Craig but it shows there's an awful large hole that will still need to be filled when Team System comes out (maybe another example of MS looking at one set of trees when they should be looking at the entire forest).

Do they think that small dev teams don't have a need for project management or bug tracking?

That Team System is based on MSF Agile goes completely against that process, because they have another formal framework for larger corporate teams (MSF Formal).

Eric's Sink had a great post when Team System was released about his thoughts on it. I think a company like SourceGear would do well to improve their own offering of SourceSafe Collab edition, price their Vault product (which does use SQL Server) for the low end, and come up with some better project management tools.
Anonymous said…
Andrew:

Thanks for the comments.

A quick teaser - Be on the lookout for SourceGear Dragnet. It is similar in concept to Collab except integrates with Vault.

A full release can be expected within the next couple of months.

Jeff Clausius
SourceGear
Anonymous said…
PS. SourceGear is always open to suggestions on product features.

Any concrete suggestions come to mind?

Jeff

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...