2 ms·
Isn't pretty much that caveat right under the title? "Notice: Below represents my PERSONAL beliefs about agile and team organization. Your results may vary."
by antris 8y ago
Isn't pretty much that caveat right under the title?
"Notice: Below represents my PERSONAL beliefs about agile and team organization. Your results may vary."
- munchbunny 8y agoNot quite. I think there's an important distinction. That caveat says: "I think you should do things this way, it might work for you." But what I'm asking for is: "I think, under these conditions, you should do things this way." But you're right to point this out. I think I phrased my post badly. The caveat isn't the important part. The second point is the really important one. The decision framework for when to take any specific piece of advice is more important than the advice itself. In general (and this is definitely true with development process advice), advice is plentiful and often conflicting, and most of it gives you ideas of what to do, but doesn't tell you when it's applicable. The really good books, courses, and blog posts I've found do exactly that.