News for hackers. Stuff that matters.
Re:Doing the Board: A simple daily planning exercise is our ... by davidedicillo on Sunday September 26, 2010 @10:01PM (#1730487)
I wonder how good this would be as web application... maybe I should give it a try.
Re:Doing the Board: A simple daily planning exercise is our ... by dotBen on Monday September 27, 2010 @02:37AM (#1730929)
I have used Pivotal Tracker in the past for this, blending non-technical tasks in with tech tasks so that all team members have tasks assigned and velocity can be tracked.

Not sure whether a whole new piece of software is necessarily needed.

Re:Doing the Board: A simple daily planning exercise is our ... by maxcameron on Monday September 27, 2010 @08:16AM (#1731416)
We hesitate to put non-technical tasks into pivotal and assign them point values. We've found that changes our development velocity, which is not desirable.

The other big issue is that our process is about setting out two or three things we want to do in a day, and seeing if we can meet our goals.

It would not make sense to click the "start" button on three features/chores/bugs at the beginning of the day, because again it would skew the pivotal data.

Re:Doing the Board: A simple daily planning exercise is our ... by dotBen on Monday September 27, 2010 @04:02PM (#1733136)
Arhh yes. For the sake of brevity I didn't get into more detail on how I've done this in the past.

I've experimented with both using a separate project for non-engineering (to avoid the skew) but also simply including non-dev work into the velocity with the same rigor that items that offer true value get points and 'cost of doing business' (pay server bill, write documentation) are non-point-accruing chores.

Both work for me.

Re:Doing the Board: A simple daily planning exercise is our ... by maxcameron on Monday September 27, 2010 @09:45PM (#1734283)
I see where you're coming from. If you're tracking tasks at all, you're doing something right. However, if you use pivotal for task management, you can't estimate how much you'll get done in a day. It's not like a developer can press the start button on three features, even if they want to complete three features in a day.

Our technique is about setting out a good amount of work for the day, and trying to meet those goals. We pull few chores/bugs/features from pivotal and throw them on the board all the time.

Re:Doing the Board: A simple daily planning exercise is our ... by wvenable on Monday September 27, 2010 @01:48AM (#1730847)
I was thinking the same thing, but not as something public -- something internal for the company.
Re:Doing the Board: A simple daily planning exercise is our ... by maxcameron on Monday September 27, 2010 @08:17AM (#1731418)
Why would it matter if it wasn't private? It's not like you're putting mission critical info on the board - there's not enough space to write out anything detailed.
Re:Doing the Board: A simple daily planning exercise is our ... by souperhearo on Sunday September 26, 2010 @10:05PM (#1730505)
I was wondering the same thing. Let us know how it turns out.