Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile antipatterns webinar august17


Published on

Agile anti-patterns real-life dysfunctions and what to do about them?

Published in: Technology
  • Hey, the slides are very useful and informative. I liked your approach very much, and it has all the details related to the topic! I just wanted to share this link so you could find some other great resources for scrum and Agile through this FREE Book on SCRUM, download here
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Agile antipatterns webinar august17

  1. 1. Raj Kasturi, • 25+ years of IT experience with eight plus years of enterprise level Agile Experience • Adjunct faculty at Pennsylvania State University, Pennsylvania, USA • 18+ years of teaching experience on Scrum, Project Management and various technology courses • Started my career as a programmer; worked as App. Dev. Manager • Agile experience as an Agile Coach, Scrum Trainer, Scrum Master • Leading and helping large-‐scale Agile project transitions • Speaker, volunteer at agile conferences, user groups • Group Leader – Agile World, User Group, Scrum Alliance 2 MBA, CSP, CSM, CSPO, PMP Speaker Introduction My Website/Blog: @AgileRaj
  2. 2. What is an anti-pattern? RARE, a mnemonic! Scrum has….. Anti-patterns Fixing dysfunctions Summary Q & A
  3. 3. What is an anti-pattern? Heard the phrase Scrum smells?..... • An anti pattern is a frequently used, but largely ineffective solution to a problem. The term was originally used to refer to a pattern gone wrong. • As Scrum practitioners, we all know that Scrum has events, artifacts, roles and rules. Or dysfunction? • If the core principles, foundation ideas or the agile manifesto is 'tweaked' hoping they would provide benefits because teams are not seeing immediate results, this may result in an anti pattern. • This in turn may become an ineffective solution to a problem.
  4. 4. RARE- a mnemonic
  5. 5. Scrum has… Scrum has three roles The Development Team The Product Owner The ScrumMaster Scrum has four events Sprint Planning Meeting The Daily Scrum Sprint Review Sprint Retrospective Scrum has three artifacts  Product Backlog  Sprint Backlog  Product Increment And an activity: Back-log refinement  Rules  Artifacts  Roles and  Events or meetings
  6. 6. Sprint anti-patterns  Not always the same length  Changing dates  Break between Sprints  Sprint Zero  Hardening Sprint  How do we fix it?
  7. 7. Sprint Planning anti-patterns  Not checking team member availability  No capacity planning  Not validating if the product backlog is refined  Too detailed/too little of planning  Spending too much time on tasks, estimation  Not coming up with a Sprint goal at the end  Product Owner dictating the ‘how’  Over committing  How do we fix it?
  8. 8. Daily Scrum anti-patterns  Going over the time-box  Non-scrum team talking  Team members missing  Team members late  Status update to the ScrumMaster  How do we fix it?
  9. 9. Sprint Review anti-patterns • Key stakeholders missing • Doing multiple review meetings • Extensive power point presentations/preparation • No credit to the development team • Delayed acceptance of user stories • Making big changes soon after receiving feedback  How do we fix it?
  10. 10. Sprint Retrospective anti-patterns • Just a formality – finish quickly • Repetitive discussions • Recording the retrospective • continuous complaining session • Not reviewing the previously identified improvement items • Not coming up with any improvement ideas • Not creating a safe environment for team to express freely • Same folks contributing to the retro  How do we fix it?
  11. 11. ScrumMaster anti-patterns • Directing and assigning work to the development team • Not protecting the team • Handling multiple teams or roles • Not paying attention to impediments • Not serving the Team or the organization • Not helping the Product Owner with product backlog refinement (techniques)  How do we fix it?
  12. 12. The Development Team anti-patterns • Not asking the right questions of the PO • Not able to say ‘No’ (?) • Pushing technical debt to future sprints • Not following the definition of done • No respect for other team members • Don’t understand the Scrum frame- work • Not helping others when done • Spending less than or more than 10% of capacity on product refinement  How do we fix it?
  13. 13. Product Owner anti-patterns • No or very limited availability • Not sharing the product vision with the Scrum Team • Skipping the Scrum meetings • Telling the team how to create a product increment  How do we fix it?
  14. 14. Product Backlog anti-patterns • Entire backlog refined, ordered • PBIs Sliced horizontally instead of vertically • Creating water-fall like user stories – design, code, test, etc. • No acceptance criteria defined • Standard format As a User…not followed, no business value defined  How do we fix it?
  15. 15. 16
  16. 16. Attributions • This presentation and deck derived from:  Scrum Guide – 17 • • • Scrum anti-patterns guide – Stephan Wolpers • References, some ideas, content derived from: