The document discusses several key aspects of successful agile transformations, including focusing on culture change and individuals over process alone. It notes that the top reasons for agile adoption are to accelerate product delivery and manage changing priorities. However, it also finds that the top causes of failed projects are issues with company philosophy/culture being at odds with agile values, lack of management support, and inconsistent agile practices. The document advocates for emphasizing individuals and interactions over process and tools in agile transformations. It also discusses the importance of roles like the Scrum Master and Product Owner and having the right team structure to support agility.

1. 23-05-2018
1
Human Side of Agile
Jayaprakash Prabhakar
Founder, LeanSoft Consulting
…key to a successful & sustainable Agile Transformation
Reason for Agile Adoption?

2. 23-05-2018
2
59
56
53
46
44
40 40
38
62
56 55
47
44 44
40 40
0
10
20
30
40
50
60
70
Accelerate
product delivery
Manage changing
priorities
Increase
productivity
Enhance software
quality
Enhance delivery
predictability
Improve
business/IT
alignment
Improve project
visibility
Reduce project
risk
7th - 2013 8th - 2014 9th - 2015 10th - 2016
REASON FOR AGILE ADOPTION (%)
Source: VersionOne Survey Results
Engineering… engineering… engineering…
Sprint
Planning
Daily
Scrum
Sprint
Review
Sprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up
Chart
Story
Board
Refactoring
Plan-Do /
Say-Do
Lead
Time
Open
Defects
3C
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task
board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design Time
boxing
Release
Planning
BDD ATDD INVEST
JIRA
RTC
VersionOne
ZenHub TFS

3. 23-05-2018
3
Sprint
Planning
Daily
Scrum
Sprint
Review
Sprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up
Chart
Story
Board
Refactoring
Plan-Do /
Say-Do
Lead
Time
Open
Defects
3C
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task
board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design Time
boxing
Release
Planning
BDD ATDD INVEST
Engineering
Practices
Events
Backlog
Metrics
Guidelines
Techniques
Definitions
JIRA
RTC
VersionOne
ZenHub TFS
Tools
Process Changes Doing Agile  Doing Agile 
Do you succeed by following
process changes?

4. 23-05-2018
4
The Cat & the MonkThe Cat & the Monk
42
44
38
36 37
33 33
46
41
38 38 38
36
34
30 30
0
5
10
15
20
25
30
35
40
45
50
Company
philosophy or
culture at odds with
core agile values
Lack of experience
with agile methods
Lack of
management
support
Lack of support for
cultural transition
Inconsistent agile
practices and
process
External pressure to
follow traditional
waterfall processes
Ineffective
management
collaboration
A broader
organizational or
communications
problem
Unwillingness of
team to follow agile
2013 2014 2015 2016
CAUSES FOR FAILED PROJECTS (IN %)
CULTURESTRUCTUREPROCESS
Source: VersionOne Survey Results
PROCESS / PRACTICE ALONE DOESN’T
ENSURE SUCCESS

5. 23-05-2018
5
Individuals and Interactions
OVER
Process and Tools
Sprint
Planning
Daily
Scrum
Sprint
Review
Sprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up
Chart
Story
Board
Refactoring
Plan-Do /
Say-Do
Lead
Time
Open
Defects
3C
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task
board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design Time
boxing
Release
Planning
BDD ATDD INVEST
Engineering
Practices
Events
Backlog
Metrics
Guidelines
Techniques
Definitions
JIRA
RTC
VersionOne
ZenHub TFS
Tools
Process Changes Doing Agile  Doing Agile 

6. 23-05-2018
6
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile
Leaders
Location
Stake
holders
End
Users
UX
Team
OPS
Team
Release
Mgmt.
Product
Manager
Agile
Coach
Leadership
Agility
ProcessStructure
SM Career PathSM Career Path
Coach / Mentor PjMsCoach / Mentor PjMs
EM – Role ClarityEM – Role Clarity
Cross-functional
skill building
Cross-functional
skill building
BA
Architect
Technical
Lead
Component
Teams
System TeamDevelopers
QA Team
Rotational
Proxy PO
Technical
Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
Available?
Shared
Product
Manager
WHAT DO WE NEED TO CORRECT?
• PgM != SM   Unique role in Scrum  Choose the right person, create a great career
• Dev Team != Dev Team + QA Team , its a Cross-functional team (of CF individuals)
• Co-locate them as much as possible
• Align Product Owner with clear Roles and Responsibilities
• Re-define the role of Manager – coach, facilitator, help technically, help in career, hiring…
• Agile Coach != Swamy-ji 
• Remove fear from Managers, PgMs – Educate and mentor them
• All Leaders = Agile Leaders (SM, PO, Managers, Leaders…). All own the success of AT.
• Senior Leader’s skin is in the AT game !

7. 23-05-2018
7
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile
Leaders
Location
Stake
holders
End
Users
UX
Team
OPS
Team
Release
Mgmt.
Product
Manager
Agile
Coach
Leadership
Agility
ProcessStructure
BA
Architect
Technical
Lead
Component
Teams
System TeamDevelopers
QA Team
Rotational
Proxy PO
Technical
Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
Available?
Shared
Product
Manager
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile Leaders
Location
Stakeholders
End Users
Business
Analyst
UX
Team
Architect
Technical
Lead
Component
Teams
System
Team
OPS
Team
Release
Mgmt.
Developers
QA
Team
Product
Manager
Part-
time
Agile
Coach
Senior
Leadership
Rotational

Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
ProcessStructure
CULTURECULTURE

8. 23-05-2018
8
Happens once a
year
Heavy & draining
on managers
More about
past, little about
future
Punishment /
Reward
Top-driven
feedback
Growth=Raise /
Promotion /
Bonus
Promotes
Individualism
Not aligned with
team value
delivery
Feedback not
actionable
Traditional Performance Management – Disruption Drivers
Knowledge
Workers

9. 23-05-2018
9
Team Performance
360 degree feedback360 degree feedback
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile Leaders
Location
Stakeholders
End Users
Business
Analyst
UX
Team
Architect
Technical
Lead
Component
Teams
System
Team
OPS
Team
Release
Mgmt.
Developers
QA
Team
Product
Manager
Part-
time
Agile
Coach
Senior
Leadership
Rotational

Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
ProcessStructure
High
Performance
CULTURECULTURE

10. 23-05-2018
10
TEAM STRUCTURE
TEAM STRUCTURE

11. 23-05-2018
11
TEAM STRUCTURE… with Manager?
1
2 3
1 Nuclear Submarine
1 Captain
135 Decision Makers

12. 23-05-2018
12
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile Leaders
Location
Stakeholders
End Users
Business
Analyst
UX
Team
Architect
Technical
Lead
Component
Teams
System
Team
OPS
Team
Release
Mgmt.
Developers
QA
Team
Product
Manager
Part-
time
Agile
Coach
Senior
Leadership
Rotational

Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
ProcessStructure
Decentralized
&
Empowered
CULTURECULTURE
High Performance

13. 23-05-2018
13
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile Leaders
Location
Stakeholders
End Users
Business
Analyst
UX
Team
Architect
Technical
Lead
Component
Teams
System
Team
OPS
Team
Release
Mgmt.
Developers
QA
Team
Product
Manager
Part-
time
Agile
Coach
Senior
Leadership
Rotational

Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
ProcessStructure
APPRAISAL
Team Performance
360 degree feedback
APPRAISAL
Team Performance
360 degree feedback
LEARNING & DEVELOPMENT
Align with Agile Team Learning
LEARNING & DEVELOPMENT
Align with Agile Team Learning
INNOVATION
Provide time / space / environment
Measure innovation
INNOVATION
Provide time / space / environment
Measure innovation
CULTURECULTURE
High Performance
Decentralized & Empowered
Team (We vs I)
" It was not a thousand attempts failed, was an invention of a thousand steps“ – Thomas Alva Edison

14. 23-05-2018
14
Fail.. Fail.. Fail... Celebrate
TUCKMAN’S MODEL
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile Leaders
Location
Stakeholders
End Users
Business
Analyst
UX
Team
Architect
Technical
Lead
Component
Teams
System
Team
OPS
Team
Release
Mgmt.
Developers
QA
Team
Product
Manager
Part-
time
Agile
Coach
Senior
Leadership
Rotational

Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
ProcessStructure
APPRAISAL
Team Performance
360 degree feedback
APPRAISAL
Team Performance
360 degree feedback
LEARNING & DEVELOPMENT
Align with Agile Team Learning
LEARNING & DEVELOPMENT
Align with Agile Team Learning
INNOVATION
Provide time / space / environment
Measure innovation
INNOVATION
Provide time / space / environment
Measure innovation
CULTURECULTURE
High Performance
Decentralized & Empowered
Team (We vs I)
Fail & Learn

15. 23-05-2018
15
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile Leaders
Location
Stakeholders
End Users
Business
Analyst
UX
Team
Architect
Technical
Lead
Component
Teams
System
Team
OPS
Team
Release
Mgmt.
Developers
QA
Team
Product
Manager
Part-
time
Agile
Coach
Senior
Leadership
Rotational

Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
ProcessStructure
APPRAISAL
Team Performance
360 degree feedback
APPRAISAL
Team Performance
360 degree feedback
LEARNING & DEVELOPMENT
Align with Agile Team Learning
LEARNING & DEVELOPMENT
Align with Agile Team Learning
INNOVATION
Provide time / space / environment
Measure innovation
INNOVATION
Provide time / space / environment
Measure innovation
CULTURECULTURE
High Performance
Decentralized & Empowered
Team (We vs I)
Self-organized

16. 23-05-2018
16
Sprint
Planning
Daily
Scrum
Sprint
ReviewSprint
Retrospective
Backlog
Refinement
Definition
of Ready
Definition
of Done
Code
Review
Unit Test
Automation
Sprinting
Burn down
Chart
User
Stories
Exploratory
Testing
User
Persona
User Story
Map
Velocity
Burn Up Chart
Story Board
Refactoring
Plan-Do / Say-Do
Lead Time
Open Defects
Continuous
Integration
Test Driven
Development
Story-point
Estimation
Capacity based
Planning
Incremental
Development
Acceptance
Tests
Task board
Scrum Of
Scrum
PO Sync
Shorter
Iteration
Pair
Programming
Automated
Builds
Collective
Ownership
Technical
Debt
Emergent
Design
Usability
Testing
Time-boxing
Release
Planning
ATDD/BDD
INVEST, 3C
Engineering
Manager
Project
Manager
Agile Leaders
Location
Stakeholders
End Users
Business
Analyst
UX
Team
Architect
Technical
Lead
Component
Teams
System
Team
OPS
Team
Release
Mgmt.
Developers
QA
Team
Product
Manager
Part-
time
Agile
Coach
Senior
Leadership
Rotational

Scrum
Master
Scrum
Master
Product
Owner
Product
Owner
Development
Team
Development
Team
ProcessStructure
Innovative
Continuous
Improvement
Intrinsic Motivated
APPRAISAL
Team Performance
360 degree feedback
APPRAISAL
Team Performance
360 degree feedback
LEARNING & DEVELOPMENT
Align with Agile Team Learning
LEARNING & DEVELOPMENT
Align with Agile Team Learning
INNOVATION
Provide time / space / environment
Measure innovation
INNOVATION
Provide time / space / environment
Measure innovation
CULTURECULTURE
High Performance
Decentralized & Empowered
Team (We vs I) Self-organized
ProcessStructure
CULTURECULTURE
Structure & Culture
is connected with
HUMAN
Agile Transformation
cannot sustain
without Human focus
Educate HR Agile &
these aspects
Culture-focused,
process and
structure driven

17. 23-05-2018
17
Questions?
JP@LEANSOFT.CO.IN
http://leansoft.co.in
Questions?
JP@LEANSOFT.CO.IN
http://leansoft.co.in