Agile Anti-Patterns

Recommendations

Info

Brooks’ Law is a very common project management antipattern “Adding manpower to a late project makes it later.” – Fred Brooks, The Mythical Man-Month (1975) “Brooks’ Law” describes a bad situation that a lot of teams find themselves in. It’s one of the most common project management antipatterns. Even though it’s called a “law,” it doesn’t really apply to every project. But we recognize the basic truth in it from our own project experiences—that’s what makes it an antipattern. an • ti • pat • tern, noun An approach to a problem that is frequently used but usually ineffective
Other common project management antipatterns “Work expands so as to fill the time available for its completion.” – C. Northcote Parkinson (“Parkinson’s law”) “Failure is not an option (that we’re comfortable planning for).” Optimism bias: ignoring risks because of a project’s importance “The first 90% of the code accounts for the first 90% of the development time. The remaining 10% of the code accounts for the other 90% of the development time.” – “The ninety-ninety rule” (Tom Cargill, Bell Labs, 1985) “It’ll take about three weeks.” Said by every software developer at some point in his or her career
Page 1 and 2: © 2016 Stellman and Greene Consult
Page 3 and 4: About Jennifer Greene • Author of
Page 5: Let’s start with a few examples o
Page 9 and 10: Agile methods and methodologies use
Page 11 and 12: When the team “gets” the values
Page 13 and 14: Antipattern: a daily standup devolv
Page 15 and 16: Most team members focus on practice
Page 17 and 18: We’ll concentrate on antipatterns
Page 19 and 20: What better-than-not-doing-it resul
Page 21 and 22: Antipattern: Product Owner without
Page 23 and 24: Antipattern: CYA culture It’s not
Page 25 and 26: The values of Scrum and the Agile M

Agile Anti-Patterns

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?