visual studio 2012 - TFS2012 vs Jetbrains TeamCity+YouTrack -
we have used tfs2012 on cloud , don't there's no reporting service we're looking move on-premise tfs2012. @ same time, we're starting git , we're thinking may make more sense tfs version control.
this requires research , developers "play admin" we're taking time evaluate whether jetbrains' highly-appraised solutions better fit.
given team of 6-8 people run scrum eager on "best practice" train agile , project combines .net technologies back-end , javascript (angularjs) on front-end, considering move tfs2012 teamcity/youtrack/git stack scrum planning, source control, continuous integration , quality control , issue tracking:
- what would/could miss tfs2012?
- what going enjoy new stack?
- is new stack falling short in respect tfs not , vice versa?
note: question specific tfs2012 - there several comparisons on , elsewhere previous tfs versions , teamcity, perhaps youtrack too.
here's brief account of two-week long experience git/youtrack vs 6 months of tfs.
the new stack feels lot more lightweight tfs. both installing (we tried on-premise tfs shortly) , using tfs gives sense of heavyweight enterprise suite no reason. partially illusion ui design gives seems youtrack:
- takes less clicks , less if learn shortcuts , how use commands.
- it's easier navigate between views - there less of them give better overview tfs. not because present more info - in cases present less info - because give key information in visually clean way.
- the ability run ad-hoc searches in youtrack makes such big difference! in tfs have create query ui tries makes easier ends making harder typing query params. mean, developers after all.
- i've enjoyed local commits of git , how pull requests work integrate work other people main branch vs merging on tfs.
- teamcity has been lightweight use - though have no experience ci on tfs. having said that, it's area didn't delve because spending lot of time managing tfs.
hiccups , things miss tfs:
- it's little harder manage releases youtrack or haven't figured out how effectively. management , separation of product backlog, release backlog , sprint backlog easier on tfs.
- there's no way plan sprint based on capacity of developers - believe jetbrains working on though.
- you gotta pay private git - though youtrack/teamcity free , full-featured few users.
i'll try , keep date go.
Comments
Post a Comment