My talk on HR in Agile in Scrum India meetup a Aricent on Feb, 25th.

1. Human Aspects
in
SCRUM
- A S Rawat;
Rawat.as@gmail.com
1

2. Agile Manifesto
• We are uncovering better ways of developing software
by doing it and helping others do it. Through this work
we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is,
while there is value in the items on the right,
we value the items on the left more.
2

3. Human Factor
• Individuals and interactions over processes and
tools
o Emphasis of individuals and teams and not on
systems, processes or tools
• Working software over comprehensive
documentation
o Emphasis on end result and core deliverable
• Customer collaboration over contract negotiation
o Emphasis on collaboration and mutual understanding
• Responding to change over following a plan
o Emphasis on adaptability rather than systems, processes or plan
3

4. Essence of Scrum
• The essence of Scrum is:
o The team makes a commitment to achieve a goals
o The team organizes itself for meeting its commitment
o The team delivers at regular interval the most valuable features
o The team strives to improve upon itself based on retrospective
and feedback
o The team’s performance is always visible in terms of progress
being made
o The team and management honestly communicate about
progress and risks
• This is based upon values of commitment, team spirit,
self-respect, respect for others, trust and courage.
• Scrum expects teams to do whatever necessary to fulfill
the commitment and deliver the desired product.
4

5. Core Values
• Values –
– commitment,
– team spirit,
– self-respect,
– respect for others,
– trust and
– courage
• Commitment to achieve
• Organizes itself
• Delivers at regular interval
• Strives to improve upon itself
• Performance is always visible
• Honestly communicate 5

6. Scrum is Simple
• The rules and practices for Scrum — a simple process
for managing complex projects — are
few, straightforward, and easy. But, Scrum’s simplicity
itself — its lack of prescription — can be disarming.
Scrum provides a simple framework of basic tenets to
solve complex problems and drive better results —
delivering more valuable software faster.
• Scrum is hard. It’s not hard because of the things you
do; it’s hard because of the things you don’t do. There
are no Gantt charts, no time reporting, and you don’t
assign tasks. Instead you learn the few simple rules of
Scrum and how to use its frequent inspect-and-adapt
cycles to create more valuable software faster.
6

7. Team & Roles
• Three roles –
– Scrum Team / Team Members
– Scrum Master
– Product Owner
• Manager ?
• Stakeholders ?
7

8. The Scrum Team
• The Scrum Team consists of the Scrum Master, the
Product Owner, and the Team. Scrum Team members
are called ―pigs.‖ Everyone else is a ―chicken.‖ Chickens
cannot tell ―pigs‖ how to do their work. Chickens and
pigs come from the story –
“A chicken and a pig are together when the chicken says,
“Let’s start a restaurant!”
The pig thinks it over and says,
“What would we call this restaurant?”
The chicken says, “Ham n’ Eggs!”
The pig says,
“No thanks, I’d be committed, but you’d only be involved!”
8

9. Do’s & Don’ts
• Initiate • Decide
• Volunteer • Control
• Collaborate • Direct
• Share • Assign
• Support • Monitor
• Interact • Oversee
• Participate • Measure
• Co-ordinate • Check
• Help • Report
• Communicate • Rectify
9

10. Challenges
• The Team –
o Adapt to new paradigm
o Honour the commitment
o Self motivated
o Self organized
o Self mananged
o Collectively responsible for the success
• The management –
o Confidence
o Hands off approach
o Encouraging
o Motivating
o Merntoring
10

11. ?Q&A?
• THANKS !!!
• AS Rawat
• Rawat.as@gmail.com
11