Jan 20, 2009 2
The only good way to create any kind of a reliable estimate is by using (your own) historical data.
If you are trying to create an estimate for a new project and are having a hard time, don’t lament your lack of historical data. The best thing you can do is to set up a system [...]
Jan 19, 2009 2
Do time tracking tools have a low uptake because it’s tedious to enter your activity data?
What do you use to enter time / activity data into your tracking tool?
If you don’t use time tracking, is there a specific reason or is it just not something you’ve considered?
What if you could enter activity data through twitter [...]
Jan 14, 2009 4
There are two kinds of great software development tools.
Read the rest of this entry »Jan 7, 2009 2
(Apologies to Stephen R Covey for the title…)
Through some odd coincidence these posts crossed my path recently:
Check In Early, Check In Often [comments here are especially good]
Best Practices for Version Control
5 SVN Best Practices
Continuous Integration is an Attitude, Not a Tool
What I got to thinking about is that version control is one of the foundation [...]
Read the rest of this entry »Jan 5, 2009 11
This is a round-up of continuous integration tools, in no particular order.
CruiseControl: Open source, Java-based. Focused on build.
Cruise: Commercial. Build/test/deploy/release. Works for most platforms and languages. Free for small and open source teams.
CruiseControl.NETOpen source rewrite of the original CruiseControl for Java.
Hudson: Open source, Java-based, runs as servlet. Supports build and test. Other processes supported via [...]
Dec 31, 2008 2
Yesterday I posted twenty reasons to do code reviews, and I promised a list of code review tools. Here they are, in no particular order. I have not used all of them, so I can’t comment on their relative merits. If there are some I missed, please leave a comment and I’ll update this list.
Codestriker [...]
Read the rest of this entry »Dec 18, 2008 3
Saw this post over at the Project Team Blog Our Projects Are Always Late. Newshirt asks (I’m paraphrasing) “Why would this person not use a time tracking tool?”
Two answers:
Because it feels like an extra step. If you want to change a behavior like time tracking, you have to make it automatic. Developers and other project [...]
Read the rest of this entry »Nov 21, 2008 1
It’s an amazing thing when your development tools work together.
In the bad old days, we thought it was cool when the editor could work in concert with source control. It blew my mind when we first had source control with integrated bug tracking. (Wow, you can see the changes that go along with each bug [...]
From The Peanut Gallery