3 votes

pivotal tracker chore: At what rate velocity should increase

It depends vastly on several different factors, perhaps most importantly on which stage the Team is in in the 'Forming, Storming, Norming, Performing' process. If the Team is in the Performing stage (...
Sarov's user avatar
  • 14.8k
2 votes

pivotal tracker chore: Should chores be picked regularly or one complete sprint should be dedicated to it? At what rate velocity should increase

Call me a purist but I would say neither. There should be no accumulated technical debt if you are doing Scrum right. Remember: Individuals and interactions over processes and tools. Regardless of ...
Muhammad's user avatar
  • 854
2 votes

Should we create multiple stories for same thing to be replicated at code level?

What you've created is technical debt, and it needs to be refactored. Do not create duplicate stories, and try not to duplicate code as you just end up paying for things multiple times. A user ...
Jon Luzader's user avatar
2 votes

What could be potential harm of giving points to chores or technical debts?

I'll share some potential downsides, but I'd be hard-pressed to say this approach is wrong if it's working for you. There are some reasons that I wouldn't do it, but that's different than wrong. So ...
Daniel's user avatar
  • 16.9k
2 votes

pivotal tracker chore: At what rate velocity should increase

In reality most teams go slower over time. This because the bigger the product becomes the higher the complexity becomes. This as more and more parts are depended on each other. To keep a high ...
Niels van Reijmersdal's user avatar
1 vote

Should we create multiple stories for same thing to be replicated at code level?

If you have to do it in 2 places, I see 2 tasks. Remember that what you estimate and track is the time a task takes, not how much value is got by the client. And... yes, that duplicity is a problem ...
A Bravo Dev's user avatar
1 vote

What can be the effective use of "story cycle time" in PivotalTracker

It can be used to identify long feedback cycles to shorten, impediments to be addressed, need for more shared understanding of items, large scope items that could be sliced more thinly, etc. Cycle ...
Alan Larimer's user avatar
  • 1,624
1 vote

pivotal tracker chore: Should chores be estimated or not?

There's a school of thought that says: Don't estimate bug fixes, chores and spikes. This is because points should only be awarded to work that adds value to the business. Developers should be ...
Will Sheppard's user avatar
1 vote

pivotal tracker chore: Should chores be estimated or not?

The simple answer would be if the team is working on an item then it should be estimated. As an example if the PO decided to run a technical debt sprint, addressing no new features, at the end of the ...
Andy L's user avatar
  • 616

Only top scored, non community-wiki answers of a minimum length are eligible