You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- 4I think it's dangerous for teams to blur the distinction between things that are directly valuable to the user and things that hopefully provide indirect value. In particular, a "everything we like is valuable" approach encourages developer gold-plating and infrastructure for infrastructure's sake. I strongly encourage people only count stories with direct business value toward velocity, because that's the only thing that customers will pay cash money for.William Pietri– William Pietri2011-03-24 17:19:41 +00:00Commented Mar 24, 2011 at 17:19
- 3Waltzing with Bears. Everything you do that's truly valuable is mostly valuable because nobody has done it before (otherwise there are other, cheaper, ways of getting it done). Most of what we do that's valuable is about learning how to do the new things. The infrastructure tasks help us get feedback on the new things, and learn more quickly. I'm with @Kristo if it helps us learn more quickly.Lunivore– Lunivore2011-03-25 02:10:58 +00:00Commented Mar 25, 2011 at 2:10
- 1@Lunivore - The difference is that nobody pays you for learning. They pay you for what you do with the learning. Teams should always take some time to improve their tools and their knowledge. But counting it as velocity confuses it with the kind of work that the team is there to do.William Pietri– William Pietri2011-03-26 00:29:35 +00:00Commented Mar 26, 2011 at 0:29
- It's not just about tools and knowledge. Thought experiment from Ashley Johnson: Think about the last project you did. Think about how long it would take to do it again with the same people, same requirements, same technology, but having learnt everything you learnt. Quotes from PMs run at about 25% to 33% - the rest is how much learning we do in software projects. Read Dan North's post on Deliberate Discovery: dannorth.net/2010/08/30/introducing-deliberate-discoveryLunivore– Lunivore2011-03-26 11:59:44 +00:00Commented Mar 26, 2011 at 11:59
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you