what possibly could go wrong?€¦ · what possibly could go wrong? with scrum… luiz “q”...

What possibly could go wrong?

With Scrum…

Luiz “Q” Quintela

Thirty years experience in multiple industries, including healthcare, financial services, oil and gas, government and energy.

Held positions of leadership including establishing and being responsible for the operation of a subsidiary in a foreign country.

Agile practitioner since 2007 and Agile Coach since 2012.

Lead projects in virtualization, product development, cloud, DevOps, Agile and scaling Scrum and has delivered cost effective and innovative solutions throughout his career.

Speaks multiple languages and has extensive experience in software localization.

What possibly could go wrong?

• Planning• Retrospective• Review• Daily Scrum• Scrum

05:00:00

Sprint Planning Troubles

Vision And Or Business Goals Do Not Exist Or Are Unclear.

Unavailable Or Non Existent Product Owner.

Too Many Product Owners.

Multiple Sources Of Funding And Stakeholders.

Team Lacks Domain Knowledge.

What Team Learned Increases Effort And Scope.

No DoD or Items Are Not Ready For Development.

Tasks Are Consistently Longer Than 2 Days.

Product Owner Has No Authority To Make Decisions.

Daily Scrum Troubles

Scrum Master:

• Managing Instead Of Leading.

• Daily Scrum Is Consistently Over The Time Limit.

• Not Facilitating The Meeting.

• Tasks Are Not Flowing Thru The System.

• Obstacles Not Identified Or Removed.

• Visitors Are Talking Instead Of Observing.

• Assigning Tasks To Team Members.

• Team Shows Dysfunctional Behaviors (Participation, Commitments, Performance, Etc.)

Daily Scrum Troubles

Product Owner:• Unavailable To Review Completed Items.

• Unavailable To Answer Questions, Discuss Assumptions And Thoughts.

• Telling Teams Members How To Execute A Task.

• Assigning Tasks To Team Members.

• Misrepresenting The Users And/or Stakeholders.

• The Sole Creator Of Backlog Items.

• Detached From The Team.

Sprint Review Troubles

• Team Demos Work That Is Not Done (By DoD).

• Team Does Not Demo From A User/Value Point Of View.

• Team Gets Defensive From Feedback.

• PO And/or The Scrum Master Is The Show Headliner.

• Product Owner Is Surprised By What Was Done Or Was Not Done.

• Stakeholders Not Present.

• Team Does Not Show Quality Metrics.

Sprint Review Troubles

• Feedback Is Not Going Into Product Backlog Because PO Dismisses It.

• Nobody Knows The Project Progress.

• PO Or SM “Diss” The Team.

• Team Members “Diss” Something or Someone.

• PO Acts Like They Are The End User.

• PO Prevents The Team From Interacting With The End Users.

• Team Demos With PowerPoint Or Screen Shots Instead Of Real Software.

Sprint Retrospective Troubles

• Team Members Are Absent.

• Team Members Do Not Participate.

• There Is No Mutual Trust So People Don’t Speak Up.• Social Loafing.

• Make Less Of An Effort When They Are Working In Teams.

• Social Anxiety. • Worry About Other Team Members Views Of

Their Ideas.

Sprint Retrospective Troubles

• Team Does Not Address Complex Issues.

• Ends With No Action Items.

• Action Items “Come Back” Next Retrospective.

• Teams Do Not Share Retrospective Learnings With Other Teams.

• “Most Of The Impediments We Identify Are Not Fixable By My Team!”

Sprint Execution Troubles

• Backlog Items Consistently Do Not Get Completed During The Sprint.

• Backlog Items “Come Back” From Production.

• By The Time Obstacles Get Removed, Most Of The Development Team Moved To Florida.

• Scrum Master Is Not Protecting The Team From Interference.

Overall Troubles With Scrum

• Resistance.

• Obstacles.

• Problems.

• Egos.

• Unrealistic Expectations.

• Difficult People.

• Lack Of Trust.

• Errors.

• Failures.