Mentoring Scenarios

Scenario Observation Action(s) as a Why?

Mentor
Daily Scrum Takes longer than 15 My actions as a By addressing
minutes mentor would be the impact of
to address the the prolonged
impact of the daily Scrum, I
prolonged daily can highlight its
scrum and to negative
suggest the next consequences
steps that could to team
lead to positive members,
changes. explain why its
important to
keep this
activity within
the 15 minutes
timeframe and
also give
suggestions on
how to keep
this event
within the time
frame.
Sprint Planning Stories/Tasks are taken into My actions here The reason for
the sprint backlog without would be first to these three
sufficient detail establish a actions is to
connection with foster
my mentee by encouragement,
acknowledging to establish the
the level of work importance of
already done, detailing stories
then I’d go ahead during sprint
to address the planning and to
impact of an ensure a
insufficiently positive
detailed story in outcome during
the sprint backlog subsequent
 and then finally sprint planning
give suggestions events.
on the amount of
detail each story
requires.
Sprint Retro Actions are spoken about For this scenario, These actions
but not actioned during I would establish would
future sprints a connection with encourage my
my mentee by mentee to keep
applauding work up with their
done till this new successful
sprint event, then sprint events,
I would state my indicate the
observation on consequences
how already of not following
discussed actions through with a
are not being suggestion and
carried out in the further
new spirit and emphasize on
how this could how and why
lead to avoidable these
challenges, which suggestions
is the impact of can and should
my observation be
and then I will implemented.
suggest ways in
which this actions
can be
implemented in
the new sprint.
Sprint Review Work achieved is presented Here, I would This action
but stakeholders give state my guides the
opinionated feedback observation on stakeholders on
without much reasoning how the how to use
feedbacks being Agile
given are rather effectively,
opinionated and knowledgeably
not constructive inspect product
enough to bring increment and
about a positive backlog and
change. I would render
 then explain to constructive
the stakeholders feedbacks to
the impact of the team
such feedbacks members.
on team members
and suggest the
COIN effective
feedback
methodology
used in Agile
work
environments
Refinement The team wants the user Here I would This approach
stories to contain a lot of establish a ensures a
information to an almost connection by positive
prescriptive degree commending the outcome
team on the level because
of diligence they emphasizes on
have shown and the need for
then express the balance as an
negative impacts agile team.
of being
prescriptive and
then suggest
ways to balance
this by being
softer and
encouraging
creativity
General A team member asks why My initial action These actions
Scenario we are doing agile (scrum would be to provide a good
or kanban) in the first place. describe the opportunity to
“There are so many impact of this educate and
meetings in my day already team member’s encourage my
with a lot of overhead refusal to practice mentee on
required to create and track
Agile, focusing on adopting agile
work on a VMB. Can we
just get on with our work the negative methodologies.
without doing it in this ‘agile’ consequences Here I can share
way?” and how it affects my Agile
other knowledge and
mentees/team experiences to
 members, then I guide my
can establish a mentee on
connection by using Agile
sharing the effectively to
challenges I faced achieve their
while learning the goals.
Agile
methodologies
and finally I can
offer suggestions
on how this team
member can
actually
implement Agile
methodologies to
get best results.
General A senior manager views My actions here These actions
Scenario retrospectives as too costly would be to would enlighten
and suggests that the team indicate the the senior
skip them to focus on work impact of manager on the
instead skipping importance of
retrospective this sprint event
events by and educate the
focusing on senior manager
highlighting on agile
avoidable practices.
challenges in
future events by
identifying
improvement
opportunities
during
retrospective
meetings. I can
then suggest
steps that could
lead to less costly
retrospective
events.
Observations from the above scenarios: These scenarios are most likely
to be encountered during the Ha (detachment) stage in the Shu Ha Ri
learning concepts. I also observed that with the right kind of feedback
mentees are encouraged towards positive lasting change.

Themes: Like earlier stated these scenarios are mostly themed around
the Ha stage. That is, the detachment stage because the mentee is still
trying to become more self aware to fully understand certain aspects of
the framework and the best Scrum practices to suit their specific needs.

Overall Mentoring Strategy: This would be; Revisit competency mapping

because these scenarios require me to regularly assess my mentee
progress, skills and to adjust goals and strategies when needed.