Titlebook: Broken Agile; Second Edition Tim Brizard Book 2015Latest edition Tim Brizard 2015 agile.software.development.programmer.scrum.essays.Java..

無(wú)動(dòng)于衷

失望昨天

Fundamental Misunderstandings,ding about Agile software development by managers harm Agile teams? Some of the best Agile projects I have been involved in were ones where the managers spent a lot of time learning Agile best practices and what works for other companies running Agile projects. On projects where this was not the case, we tended to have a lot of issues.

亂砍

Transparency,project, and the company. Having seen first-hand organizations that claim they want “openness” but then don’t listen or, worse, punish those who are open, I can say that true transparency is not easy. But it is critical to the success of Agile software development and worth the effort.

線

不成比例

Challenges with Estimations,m does, the less team members will think in terms of time and the more they will think in terms of points. The key is to understand why Agile uses points and to understand what goes into determining the points on a User Story.

Overstate

Specifications and Testing,s and keeping them synchronized. Quickly these get outdated and very rarely reflect what the software is actually doing. I think a better approach is to have what Gojko Adzic calls “l(fā)iving documentation.”

人造

Overstate

閑蕩

Aphorism