TEACHERS
GALLERY
PRICING
SIGN IN
TRY ZURU
GET STARTED
Loop
Audio
Interval:
5s
10s
15s
20s
60s
Play
1 of 14
Slide Notes
Download
Go Live
New! Free Haiku Deck for PowerPoint Add-In
Copy of CROSS FUNCTIONAL TEAMS
Share
Copy
Download
0
263
Published on Nov 19, 2015
No Description
View Outline
MORE DECKS TO EXPLORE
PRESENTATION OUTLINE
1.
CROSS FUNCTIONAL TEAMS
THE SCRUM WAY
Photo by
e r j k p r u n c z y k
2.
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
3.
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
Photo by
SuperFantastic
4.
specialists
Deep expertise in one area
Sticks to the "comfort zone"
No pro-active attitude
Limited visibility of the work ahead
Photo by
mojoey
5.
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
6.
BENEFITS FOR THE TEAM
Photo by
Iztok Alf Kurnik
7.
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
8.
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
9.
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)
Photo by
William Brawley
10.
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
11.
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
12.
One team consists of:
FrontEnd dev
BackEnd dev
Mobile dev
UI designer
QA
Photo by
[cipher]
13.
Bottom line
Be a Specialized Generalist for your team
Be flexible whenever you can
Serve the common goal
Rinse, wash & do it again!
Photo by
Armando Maynez
14.
q & a
Photo by
Fey Ilyas
Friend of Haiku Deck
×
Error!