1 of 14

Slide Notes

DownloadGo Live

Copy of CROSS FUNCTIONAL TEAMS

Published on Nov 19, 2015

No Description

PRESENTATION OUTLINE

CROSS FUNCTIONAL TEAMS

 THE SCRUM WAY

sCRUM TEAM OBJECTIVES

  • Keep everyone working on the project in close contact and in sync
  • Work on a feature's different layers  in parallel
  • Create a close-knit team with a high level of trust 
Photo by WarzauWynn

Cross-functioning on a team

  • Not everyone needs to be a cross-functional member for the Team to be "Cross-functional"
  • A well balanced team is a proper team with proper velocity
  • Be open to changing circumstances
  • Be a Specialized Generalist

specialists

  • Deep expertise in one area
  • Sticks to the "comfort zone"
  • No pro-active attitude
  • Limited visibility of the work ahead
Photo by mojoey

t-shaped

  • Broad range generalist
  • Capable to step out of his/her role
  • Highly pro-active 
  • High visibility of the work to be done
Photo by JD Hancock

BENEFITS FOR THE TEAM

PROCESS

  • PBIs broken into smaller tasks = More manageable
  • Each task put into the Sprint Backlog = More control
  • Once the Sprint is agreed on, no changes can be made
  • All team members distribute work among themselves 
  • Flexibility is key!
Photo by Ikhlasul Amal

team

  • Higher visibility of the project (Vision) 
  • Higher visibility of their own work
  • Increased velocity of the Team
  • More control during the sprint (bottlenecks)
  • Becomes self-sustainable
Photo by chrismar

Real world scenario

  • I don't understand what I'm supposed to do...
  • This is NOT my job!
  • DA FUQ is this?!
  • I'm still waiting for him to finish so I could start (QA)

Boundaries & Limitations

  • Size of a team is defined by the "Two pizza rule" 
  • Team members support each other but don't over-reach all the time 
  • PO doesn't mess with the Sprint once started
  • Scrum Master protects the Team (ALWAYS)
Photo by DeaPeaJay

teams as Work cells

  • Each team holds 5-9 people ideally
  • One person belongs to only one team!
  • Each team acts as a single work cell on the project
  • The whole team is responsible for the outcome of the sprint they commit to
Photo by bgolub

One team consists of:

  • FrontEnd dev
  • BackEnd dev
  • Mobile dev
  •  UI designer
  • QA
Photo by [cipher]

Bottom line

  • Be a Specialized Generalist for your team
  • Be flexible whenever you can
  • Serve the common goal 
  • Rinse, wash & do it again!

q & a

Photo by Fey Ilyas