This document profiles Heitor Roriz Filho as an Agile coach and trainer with over 17 years of experience in software development and systems analysis. He provides training in Scrum, user stories, estimation, and Agile coaching. As a coach, he focuses on empowering teams and ensuring continuous improvement through aligning expectations and reducing the impacts of measurement.

1. Heitor Roriz Filho, MSc, CSM, CSP
Agile Coach and Trainer

2. Distribution and use
license

3.  17+ years experience in market
 Software developer
◦ Natural, Cobol, Clipper, Delphi, Java
 Systems Analyst
 ScrumMaster, Product Owner
 Training and coaching since 2007
 Agile Coach and Trainer, Massimus
◦ English, Portuguese, Spanish and German
 Coach and Trainer Partner, Rally Software
◦ Latin America and Brazil
www.massimus.com

4.  Trainings
◦ Scrum for PMPs (Agile PM)
◦ Mastering User Stories
◦ Scrum Introduction (CSD track)
◦ Agile Estimation and Planning (CSD track)
 Agile Coaching
◦ A Scrum Coach not only has stories to tell and
answers to give, above all he has the right
questions for each occasion. He is very good in
recognizing potential.
www.massimus.com

5.  Regularly measures and monitors progress in
order to identify variances from the plan
 Also allows corrective action to be taken
when necessary to meet project objectives

6.  Some words from the traditional world do not
sound nice in Agile
 In huge projects the good practices found in
a compendium like the PMBOK are a helpful
extension
Development

7.  Focus on people
 Agile Manifesto
 Train and be a companion to the team
◦ Make sure they understand the process
◦ Warranty continuos improvement
◦ Decrease measurement impacts
 Align expectations

8. 1 2 3 4 5
Stakeholder satisfaction
1 2 3 4 5
Deliver on time
1 2 3 4 5
Deliver on budget
Deliver all planned scope 1 2 3 4 5
Meet quality requirements 1 2 3 4 5
Team satisfaction 1 2 3 4 5

9.  Observation
 Comparison
 Take a step back: define metrics
◦ What will be measured
◦ How will be measured
◦ Who will measure
◦ Effects of measurement
 Hawthorne Effect: we impact what we
measure

10.  Size: something that can be counted and
measured.
 Effort: the actual hours needed to develop a
software or piece of product.
 Duration: the time in the calendar to get
something done.
 Cost: strongly correlated with effort.

11.  To plan - When we have to do something?
 To Program - In what order we do things?
 To contract - Do we need more people to do
the job?
 To quote - What will it cost?
 To guide investment - Are we doing
something worthwhile?
 We estimate to approximate the real,
right?

12.  It feels good
 Answer “boss” requests
 I am used to do that way
 Fool ourselves and others: when will the
project be finished?

13. Einstein’s Wisdom

14. Measuring outcome, not
activity.
Measuring everything
necessary and nothing
more.

15. By Dave Nicollette
“Our highest priority is to satisfy the customer
through early and continuous delivery of
valuable software.”
and
“Working software is the primary measure of
progress.”

16. Running Tested Features
Running Tested Features
12
10
8
Features
6 RTF
4
2
0
Iteration
Graphic from Dave Nicolette

17.  Principle
Working software is the primary measure of progress.
 Informational
Direct measure of delivered results.
 Diagnostic
If flat or declining over time, a problem is indicated.
 Motivational
Team members naturally want to see RTF increase.

18.  Principle
Our highest priority is to satisfy the customer through early
and continuous delivery of valuable software.
 Informational
Direct measure of customer-defined value delivered.
 Diagnostic
Trend should be an S curve; otherwise, problems in
prioritization or valuation are indicated.
 Motivational
Team members like to deliver value because it makes them
feel they are contributing to the success of the organization.
Stakeholders are motivated to pay attention to the business
value of incremental releases.

19.  Revenue
 Cost savings
 Market share
 Customer relations
 Reputation

20. As a Team
As a CSM, I want As a CSM, I want As a Product As a CSM, I want As a CSM, I want
Member, I want to
to have a senior to have a senior Owner, I want to to have a senior to have a senior
work in a great
Team. Team. the best ROI. Team. Team.
team
As a Product
Backlog, I want to
As a Team As a Team
As a CSM, I want change all the As a CSM, I want As a Product
Member, I want to Member, I want to
to have a senior time that is need, to have a senior Owner, I want to
work in a great work in a great
Team. to be able to Team. the best ROI.
team team
become a great
product.
As a Team As a Team
As a Product As a Product As a Product As a CSM, I want
Member, I want to Member, I want to
Owner, I want to Owner, I want to Owner, I want to to have a senior
work in a great work in a great
the best ROI. the best ROI. the best ROI. Team.
team team
As a Product As a Product
Backlog, I want to Backlog, I want to
As a Team As a Team
As a Product change all the As a CSM, I want change all the
Member, I want to Member, I want to
Owner, I want to time that is need, to have a senior time that is need,
work in a great work in a great
the best ROI. to be able to Team. to be able to
team team
become a great become a great
product. product.
As a Product
Backlog, I want to
As a Team
change all the As a Product As a Product As a Product
Member, I want to
time that is need, Owner, I want to Owner, I want to Owner, I want to
work in a great
to be able to the best ROI. the best ROI. the best ROI.
team
become a great
product.
As a Product
Backlog, I want to
As a Team
change all the As a CSM, I want As a CSM, I want As a CSM, I want
Member, I want to
time that is need, to have a senior to have a senior to have a senior
work in a great
to be able to Team. Team. Team.
team
become a great
product.

21. Quick registration The objective represents 40%
process of a client’s requirement.
0.4
User account Account Registration
registration processing represents 70% of the
0.7 0.3 objective.
As a financial analyst I
As a user I can enter As a user I can enter
need to check on user
my data to get payment data to have a
data to release
registered valid account
payment
0.4 0.6 0.1
The story implements % Delivered Value:
60% of registration
0.4x0.7x0.6 = 16.8%
value

22. Mesuring velocity

24.  Principle
Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
 Informational
Empirical observation of the team’s capacity for work; useful for
projecting the likely completion date of a given amount of scope;
useful for estimating the amount of scope that can be delivered by a
given date.
 Diagnostic
Patterns in trends in velocity indicate various problems; provides a
baseline for continuous improvement efforts
 Motivational
Team members take pride in achieving a high velocity and keeping it
stable.

26. Burn-down Chart
2000
1800
1600
1400
1200
Scrum Team Alpha
1000
Scrum Team Beta
800 Scrum Team Gamma
TOTAL
600
400
200
0
l
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
tia
i
In

27.  Gantt chart
 Percent complete
 Time per team member per task
 Actual time vs. estimated time

28. Heitor Roriz Filho, MSc, CSM, CSP
Agile Coach and Trainer
hroriz@massimus.com
http://www.massimus.com
@hroriz
http://br.linkedin.com/in/hroriz