How we run our agile dev process using only Trello and Google Docs

Re:How we run our agile dev process using only Trello and Go... by adrianhoward on Wednesday April 18, 2012 @03:31AM (#3856919)

If you're not getting a pretty constant velocity (if you're going the sprint route) or cycle time (the kanban/flow route) then no tool is going to make that happen.

I confidently predict that if Pivotal is not helping you now, Jira will not help you in the future. What needs to change is how the team works, or maybe management's expectations of the team. Not the tool.

[ Parent | on HN ]

Re:How we run our agile dev process using only Trello and Go... by productmanager on Wednesday April 18, 2012 @12:43PM (#3858846)

agree.. technically the velocity should be constant and more or less is.. but the story estimates still establish the building blocks for this.. a story seems to need tasks and task estimates to make the overall story estimate more accurate. Tasks help to break up activities. alternative is to groom the story of course, then you're left with a larger list of stories to manage however, and taking care of that in turn eats into our PM team's velocity :)

[ Parent | on HN ]

Re:How we run our agile dev process using only Trello and Go... by adrianhoward on Thursday April 19, 2012 @03:59AM (#3861881)

It sounds like your spending a lot of effort on estimating. I'd guess (I'm not there so probably incorrectly :-) that you've got some combination of:

a) stories being too big

b) stories having to much variation in size

c) doing time based estimation rather that relative estimates or story counting.

[ Parent | on HN ]