Professional Documents
Culture Documents
We
have
multiple
teams
w orking
from
Can
same
person
play
dual
role
in
Scrum
different
locations
on
same
team?
Why
is
the
restriction
of
3
–
9
for
Product/project.
Is
it
fine?
Development
team
size?
This
would
be
normal
and
expected
of
a
At
least
t raditional
Scrum
(earlier
Scrum
cross-‐functional
Development
team.
Less
than
3
may
have
skill
deficiency,
Guides
v ersions)
p rovide
strong
guidance
Within
the
Scrum
Team,
as
with
a
decrease
in
interaction
whereas
more
than
9
may
have
too
many
that
teams
should
be
co-‐located.
member
of
the
Dev
Team
also
being
the
If
that
isn’t
possible
we
can
still
apply
Product
Owner
or
ScrumMaster?
This
is
communication
channels
and
too
much
Scrum,
but
we
are
likely
to
encounter
contextual
-‐-‐
for
example
with
a
very
coordination
and
may
lead
to
conflicts
and
defocus
and
the
complexity
challenges
which
result
in
non-‐optimal
small
Scrum
Team,
it
might
be
results.
We
have
to
do
the
best
we
can
appropriate
for
one
p erson
to
wear
t wo
increases.
hats,
Product
Owner
and
Dev
Team
while
maintaining
the
intent
to
move
This
3
–
9
is
like
a
rule
of
thumb.
At
t imes
member,
for
example,
but
under
most
continually
towards
optimal
states.
slightly
higher
than
9
also
may
work
normal
circumstances
the
roles
should
effectively.
But
too
higher
than
9
may
Scrum
Masters
should
focus
on
be
dedicated
to
a llow
the
Scrum
value
of
enhancing
transparency,
communication
lead
to
issues.
“focus”
to
be
best
realized.
The
Product
and
collaboration
in
this
scenario.
Owner
and
ScrumMaster
roles
should
Perhaps,
some
tools
may
b e
h elpful.
never
b e
shared.
Should
the
Development
teams
be
Can
tasks
be
added
to
the
Product
component
teams
or
feature
teams?
backlog?
How
Product
owner
orders
the
Product
Scrum
does
not
have
any
specific
Backlog
items?
recommendation
on
component
Vs
The
term
“tasks”
is
undefined
in
Scrum.
feature
teams.
However,
you
need
to
Scrum
identifies
Product
Backlog
Items
Ordering
is
up
to
the
Product
Owner.
I
have
a
cross-‐functional,
self-‐organized
(PBIs
–
represent
WHAT)
and
Sprint
recommend
ROI
(Return
on
Investment,
team
that
converts
the
PBI
into
Backlog
Items
(SBIs).
The
Product
Owner
considering
expected
return
vs.
the
cost
releasable
increment.
Component
teams
can
change
the
Product
Backlog
as
they
to
produce)
but
other
options
(Time
to
may
have
more
complexity,
less
see
fit,
including
adding
additional
market,
Learning,
Risk)
could
be
other
transparency
and
integration
issues
and
Product
Backlog
Items,
at
any
time.
factors.
Prioritization
is
different
than
feature
teams
will
have
less
complexity,
Sprint
Backlog
Items
are
not
part
of
the
ordering.
The
Product
Backlog
is
o rdered.
less
integration
issues
and
more
Product
Backlog,
and
are
owned
and
Prioritization
might
be
used
to
identify
a
transparency.
In
my
experience
feature
managed
by
the
Development
Team
subset
of
features
to
focus
on
for
teams
work
better
but
if
you
are
using
within
the
Sprint.
Usually
“Tasks”
are
ordering.
[NOTE:
be
careful
not
to
comp
teams
and
they
a re
working
f ine,
it
added
to
the
Sprint
Backlog
as
they
confuse
ordering
and
prioritization]
is
fine
to
continue.
However,
make
sure
represent
“HOW”
DOD
will
have
integration
included
in
it.
Can
we
use
JIRA/VersionOne
to
add
If
its
multi-‐vendor
Product
who
all
can
one
field
for
Definition
of
Done?
be
involved
in
formulation
of
Definition
of
Done?
One
vendor
wants
Scrum
doesn’t
prescribe
a
specific
Documentation
another
don’t
(Health
manner
for
specifying
or
maintaining
the
Can
the
Scrum
team
add
new
items
to
care
product
Honeywell
wants
DoD.
The
specific
approach
would
be
at
their
Definition
of
Done
every
sprint
in
Qualcomm
no
interest)
the
discretion
of
the
self-‐organizing
name
of
improvement?
Scrum
Team.
As
a
ScrumMaster-‐ If
multiple
Scrum
Teams
are
involved
The
DoD
is
d eveloped
and
maintained
by
consultant
I
might
share
my
experience
they
should
share
a
common
Definition
the
Scrum
Team.
They
can
change
it
as
with
virtual
tools
reducing
transparency
of
Done.
Individual
Scrum
Teams
might
they
see
f it.
However,
Definition
of
Done
and
effectiveness
when
compared
to
add
additional
items
to
this
DoD
for
their
does
not
usually
get
changed
during
the
non-‐virtual
tools.
As
a
ScrumMaster-‐ own
use,
but
they
must
meet
at
least
the
Sprint.
coach
I
might
work
to
make
issues
arising
common
DoD.
While
the
ScrumMaster
from
the
use
of
a
virtual
tool
t ransparent
might
be
the
facilitator
for
establishing
so
that
the
Scrum
Team
can
inspect
and
the
DoD,
other
members
of
the
Scrum
adapt.
Team
could
a lso
facilitate.
What
is
the
best
way
to
measure
How
much
is
the
standard
C apacity
of
a
Performance?
team
member
per
day?
What
performance?
If
product,
what
The
best
and
short
answer
is
“ask
the
Can
Definition
of
Done
be
an
input
for
about
clients
paying
for
it
(or
even
pre-‐ team”.
Sprint
Planning?
paying
for
it),
product
uptake/usage,
Individuals
and
Interactions
over
Process
stickiness,
etc.
Comparing
the
While
the
Development
team
forecasts
and
Tools
-‐-‐
focusing
on
Individuals.
Why
Development
Team
whether
within
the
the
functionality
for
the
Sprint,
they
would
you
want
to
know
standard
Development
Team
or
across
consider
Definition
of
Done.
So
yes,
capacity?
What
drawbacks
are
there
to
Development
Teams
often
leads
to
implicitly
the
Definition
of
Done
is
an
measuring
this?
What
options
might
be
disfunction;
I
would
be
curious
why
this
input
to
the
Sprint
Planning.
more
suitable
in
a
self-‐organizing
type
of
measurement
would
be
required
context?
and
help
discover
the
pluses
and
minuses
to
different
approaches.
Planning.
If
the
Development
team
is
not
able
to
Our
team
talks
every
day,
still
do
they
Can
some
members
not
attend
and
deliver
done
increment,
do
they
need
need
Daily
Scrum?
share
their
updates
via
e mail?
Sprint
Review?
Yes.
Each
event
has
a
specific
purpose,
What
is
Agile
p rinciple
number
#6
(face-‐ Yes,
they
still
should
go
ahead
with
sprint
and
the
purpose
of
the
Daily
Scrum
goes
to-‐face
communication)?
Ideally
all
review
in
order
to
increase
the
beyond
“everybody
talks”.
It
is
a
specific
Development
team
members
have
to
transparency
and
continued
t rust.
inspect
and
adapt
opportunity
and
a
way
attend
the
Daily
Scrum
in
normal
to
assure
that
everyone
has
The
Sprint
Review
is
a
key
inspect
and
conditions.
If
someone
is
sick
or
has
transparency
while
minimizing
breaking
adapt
point,
and
no
increment
available
some
personal
issue,
then
it
is
okay.
focus.
would
be
high
transparency
of
a
critical
Daily
Scrum
is
for
the
development
t eam
issue
that
needs
to
be
inspected
and
It
helps
increasing
the
probability
of
talks
to
d evelopment
t eam.
adaptations
made
to
prevent
meeting
the
Sprint
goal.
continuation
or
recurrence
of
the
issue.
Our
Scrum
team
is
distributed
across
In
my
company
we
have
Sprint
two
locations,
is
it
okay
if
we
have
Retrospective
for
every
2
Sprints
in
separate
retrospective
for
both
teams?
Our
team
is
doing
well,
do
we
still
need
order
to
use
that
time
to
improve
the
This
clearly
highlights
lack
of
retrospective?
productivity.
It
is
w orking
fine.
Is
it
fine?
transparency.
So,
Scrum
Master
must
Continuous
improvement
is
a
journey,
It
is
not
fine,
the
productivity
gain
you
get
identify
practices
that
will
help
to
bring
not
a
destination.
Hence,
retrospective
both
teams
as
close
as
possible
helps
Scrum
teams
to
identify
may
be
very
minimal
when
compared
to
the
loss
of
improvement
opportunity
you
improvements
which
help
them
to
I
would
be
curious
about
any
issues
that
lost
due
to
this
inconsistent
become
great.
have
surfaced
with
this
approach,
retrospective.
including
the
feeling
of
being
“one
team”.
Investigating
alternatives
might
also
b e
interesting.
www.learnovative.com