Loading Profile...
Recent activity
Subscribe to this feed-
Steve C started following the question "Colors for labels!" in Pivotal Labs.
-
Steve C replied on November 21, 2009 02:49 to the question "Override velocity after restarting stalled project" in Pivotal Labs:
Could we maybe just have a way to enter in a velocity number and have velocity be that? i.e., "set velocity to X" and you enter the number in the box. In fact you could just add another button to velocity override to "make the override permanent" - that would be a fairly elegant way to accomplish it. -
Steve C replied on November 15, 2009 21:55 to the question "Override velocity after restarting stalled project" in Pivotal Labs:
I agree. This goes for coming out of weeks with a bunch of bug-fixing. We know for a fact that we can execute at "normal" velocity, so we have to cook the books with Team Strength to make Tracker a reliable planning tool once again. -
Steve C shared an idea in Pivotal Labs on October 28, 2009 05:51:
I'd like a project setting to replace points with average # days spent on stories, and use that as the prediction mechanismThis would hide the estimation capability / points stuff, and instead count days elapsed since clicking start. I need a place in project settings to say how many parallel story slots I have - let's say for example "1.5". A rolling 3- or even 6-week average of days-to-complete-a-story is computed, and that tells me how many stories I'm likely to get done in the next iteration and out into the future...if my average-days-to-complete is 3, and I have 2.5 story slots, that's 2.5*5 slot-days = 12.5 / 3 = 4 stories predicted to be finished this iteration.
So you have yesterday's weather prediction, and people clicking start and finish and accepting, etc - using a lot of the core parts of tracker just without up-front estimation and all the stuff about points.
I can't imagine this would be hard to accomplish and is well within the spirit of Tracker. -
Steve C replied on July 01, 2009 18:58 to the idea "Expose all releases, even those in collapsed future iterations" in Pivotal Labs:
I have a follow-on idea. Instead of showing collapsed future iterations - which I argue are not that interesting at all - instead collapse on future releases. -
A comment on the idea "enhanced feedback widget, per page?" in Get Satisfaction:
Which is probably the way to go, I may take a shot at doing this with the api (when I get some time). – Steve C, on April 16, 2008 20:42 -
A comment on the idea "enhanced feedback widget, per page?" in Get Satisfaction:
Let's say I'm a beta user of something like gmail. I always expect the Sign Out link to be on the top left part of the page, but it's actually located at the top left. I might go to the beta feedback section at the bottom of the page (let's say it's a link in the footer that, when I click, expands to show a comment thread, and a place to post feedback). I can see what other people have said about this page, and post my own comment.
That example might be overly specific. If I had something like the topics widget, that allowed posting and replying, I think we'd be really close. – Steve C, on April 16, 2008 20:40 -
Steve C shared an idea in Get Satisfaction on April 16, 2008 16:42:
enhanced feedback widget, per page?I'd like to allow my users to give feedback on each page of my site, so that when people are using a page they have a consistent place to give feedback (a little toolbar in a footer, for example).
I was considering putting this together myself (maybe some sort of threaded discussion per page), but it seems like it has strong getsatisfaction potential - I'd love it if I could drop this kind of widget straight into my app.
Any thoughts? Is there a way to take an existing GS widget and repurpose it in this way?
