Agile Anti-Patterns

Recommendations

Info

<strong>Anti</strong>pattern: Command-and-control Scrum • Command-and-Control project managers feel like they create and “own” the schedule by themselves • They get estimates from the team and create the plan on their own • Team Leads assign work to the team members to do exactly what’s required by the plan • This can lead to “water-Scrum-fall”: the project is planned up front, and iterations are just project phases This is a better-than-not-doing-it result. It gets the job done, but the team could be much more effective.
<strong>Anti</strong>pattern: Product Owner without authority You want to include that feature in the sprint? Wow, that decision’s way above my pay grade. I’ll have to check with my boss, and maybe his boss, and… Product Owner If the Product Owner doesn’t have the authority to make product decisions, the team can’t plan effectively. The better-than-notdoing-it result is that the team still produces some work, but users and managers aren’t happy and team has to tear out and redo features. The Product Owner decides what items go into the product backlog, and which of those items the team will work on during each sprint. At the end of the sprint, the Product Owner accepts the completed items on behalf of the company. This depends on the Product Owner having the authority to make those decisions. That authority is compromised if: • The team elects a Product Owner from within their own ranks who does not have any special authority • Senior management chooses a Product Owner but doesn’t stand behind his or her decisions • The Product Owner role is replaced with a committee
Page 1 and 2: © 2016 Stellman and Greene Consult
Page 3 and 4: About Jennifer Greene • Author of
Page 5 and 6: Let’s start with a few examples o
Page 7 and 8: Other common project management ant
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: What better-than-not-doing-it resul
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

Create successful ePaper yourself

Delete template?

Save as template?