Šī prezentācija ir par to, kādas būtiskas lietas ir jāzina, slēdzot jebkuru līgumu, kādas ir tipiskas programmatūras izstrādes līguma daļas, kas ir mainījies līdz ar agile programmatūras izstrādes pieejas parādīšanos un kā sagatavot programmatūras izstrādes līgumu, kas atbalsta agile izstrādes pieeju.
Workshop on Agile estimation techniques including Planning poker, Affinity estimation and relative estimation. First prez at Trasys during a lunch seminar
This presentation tells what things are essential for any contract, what information has to be included in typical software development contract, what has changed after agile software development approach emergence and how to prepare your own agile software development contract.
Agile Contracts by Drew Jemilo (Agile2015)Drew Jemilo
Agile has moved far beyond commercial software into the world’s largest enterprises and government agencies. We have scaling methods which can help launch vehicles into the atmosphere and beyond, yet traditional contract mindsets have put a drag on escape velocity. But there’s good news! We have agile explorers discovering the next frontier of contract agility. Join us for this Agile2015 session and enter the new era! This era includes the Scaled Agile Framework® (SAFe®)
TRADITIONAL MODELS TO LEAN-AGILE APPROACHES
Fixed requirements, big up-front design, and gated processes have been the norm. The rationale seemed logical in the past. It would not make sense to award a contract or commit to a major development investment without knowing what the system is supposed to do, how much it costs, and when it will be completed. We assumed that complex systems could be fully defined before they were built, that requirements and solutions would not change, and that we could build it right the first time.
Traditional models exist but Lean-Agile contract approaches are gaining momentum in both the commercial and the U.S. Federal space. Find out more!
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
Šī prezentācija ir par to, kādas būtiskas lietas ir jāzina, slēdzot jebkuru līgumu, kādas ir tipiskas programmatūras izstrādes līguma daļas, kas ir mainījies līdz ar agile programmatūras izstrādes pieejas parādīšanos un kā sagatavot programmatūras izstrādes līgumu, kas atbalsta agile izstrādes pieeju.
Workshop on Agile estimation techniques including Planning poker, Affinity estimation and relative estimation. First prez at Trasys during a lunch seminar
This presentation tells what things are essential for any contract, what information has to be included in typical software development contract, what has changed after agile software development approach emergence and how to prepare your own agile software development contract.
Agile Contracts by Drew Jemilo (Agile2015)Drew Jemilo
Agile has moved far beyond commercial software into the world’s largest enterprises and government agencies. We have scaling methods which can help launch vehicles into the atmosphere and beyond, yet traditional contract mindsets have put a drag on escape velocity. But there’s good news! We have agile explorers discovering the next frontier of contract agility. Join us for this Agile2015 session and enter the new era! This era includes the Scaled Agile Framework® (SAFe®)
TRADITIONAL MODELS TO LEAN-AGILE APPROACHES
Fixed requirements, big up-front design, and gated processes have been the norm. The rationale seemed logical in the past. It would not make sense to award a contract or commit to a major development investment without knowing what the system is supposed to do, how much it costs, and when it will be completed. We assumed that complex systems could be fully defined before they were built, that requirements and solutions would not change, and that we could build it right the first time.
Traditional models exist but Lean-Agile contract approaches are gaining momentum in both the commercial and the U.S. Federal space. Find out more!
Ever wonder why Agile teams swear by relative estimation? My teams improved sprint planning efforts by a factor or 3, once we started using relative estimation.
Without understanding Agile relative estimation, teams tend to fall back to using time-based methods. This often leads them to spend way too much time on obsolete estimates that will be made even more complex with all the unknowns and constant emergent requirements of an Agile world!
“It's better to be roughly right, than precisely wrong!”
~ John Maynard Keyenes
The Solution is simple: understand that relative estimation is only a rough order of magnitude estimate to quickly organize the product backlog. This empowers your product owners (PO) to quickly make value based trade-offs on backlog items and decide on what stories the team should work next. This gives the business the highest bang for their buck!
PROBLEMS WITH TIME-BASED ESTIMATES
-Teams spend too much time trying to get it right
-Lack of confidence/experience can lead to people being either optimistic or pessimistic
-Timeline you are estimating may be too far in the future
-Due to long timeline, there are too many risks, unknowns, changes or dependencies!
WHY USE RELATIVE ESTIMATION?
-Allows a quick comparison of stories in the backlog
-Allows you to select a predictable volume of work to do in a sprint
-Uses a simple arbitrary scale
-Allows PO to make trade-offs and take on the most valuable stories next
ESTIMATION TIPS
-Relative points or equivalent Tshirt sizes are used to estimate stories, leveraging the Fibonacci sequence modified for Agile.
-The team estimates the story, not management nor the customer.
-Story estimates account for three things: effort, complexity, and unknowns. Don’t short sell yourself by estimating effort alone, that’s where waterfall projects face issues.
-Remember to estimate all Stories, user stories or technical stories. Even estimate research or discovery spikes.
-Refine your backlog as a team on a continuous basis, to get your stories to meet the Definition of Ready.
-Only pull into your sprint, stories that are refined and estimated.
-Break down stories that are large, into smaller slivers of value to optimize your flow.
-Don’t sweat it if you get it wrong, teams often do early on but improve over time.
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Answers the queries
What do Certified ScrumMaster Trainings involve, who is the certifying authority and how does the certification process work ?Why should you consider getting Certified at all? Does it add value to your career ?How do you take the decision on whether or not to go for certification ?
In other words, is it worth it?
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
Answers the queries
What do Certified ScrumMaster Trainings involve, who is the certifying authority and how does the certification process work ?Why should you consider getting Certified at all? Does it add value to your career ?How do you take the decision on whether or not to go for certification ?
In other words, is it worth it?
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
In this interactive webinar, the participants will get an overview of the fundamental principles and mechanics of Scrum, thereby understanding the benefits of adopting Scrum principles and values in an organization
1. USER
STORIES
&
RELATIVE
ESTIMATION
By
Bachan
Anand
Prepared
by
Indu
Menon
Please dial into (218) 895-4640 PIN: 3289145
2. Agenda
• What
is
the
need
for
user
stories?
• What
is
a
story?
• What
is
criteria
for
a
good
story?
• Rela7ve
Es7ma7on
• Planning
Poker
Please dial into (218) 895-4640 PIN: 3289145
3. What
problems
do
user
stories
address?
Communica7on
Problem!
Please dial into (218) 895-4640 PIN: 3289145
h?p://agile.conscires.com/
4. What
are
stories?
3C
Please dial into (218) 895-4640 PIN: 3289145
h?p://agile.conscires.com/
5. 3C
• Story
Card
• Wri?en
on
Note
cards
• Should
have
es7mates,
notes
etc
• No
jargon
• Wri?en
in
direct
speech
• Conversa7on
• Details
behind
the
story
• Emerges
when
team
talks
with
Product
owner,
customer
• Confirma7on
• Acceptance
tests
8. Rela<ve
es<ma<on
• Use
Story
points
as
units
• At
higher
abstrac7on
levels
rela7ve
es7mates
suit
be?er
than
the
absolutes.
• As
we
move
higher
the
abstrac7on
the
clarity
reduces
and
accuracy
with
absolute
es7mates
decreases.
h?p://agile.conscires.com/
9. Rela7ve
Es7mates
• Points
are
abstract
representa7ons
of
rela7ve
effort,
which
includes
complexity,
size
etc.
• Scales
currently
used:
– Fibonacci
Scale:
1,
2,
3,
5,
8,
13
...
– Linear
Scales:
1,
2,
3,
4,
5,
6,
7,
8,
9,
10
– T-‐shirt
sizes:
XS,
S,
M,
L,
XL
10. Rela<ve
es<ma<on-‐
Where?
• Velocity
– Measure
of
how
much
work
a
team
can
do
in
a
given
period
• Release
Planning
– It
is
easier
to
es7mate
high
level
scope
• Sprint
Planning
– Helps
focus
on
goals
(delivery
of
a
complete
work)
h?p://agile.conscires.com/
12. Es7mate
Each
Item
-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐
-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐
-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐
-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐-‐
• How
big
is
this?
• 1?
• 8?
• 100?
19. Rela<ve
es<ma<on
using
“Planning
Poker”
• Decide
on
scale
– Fibonacci
scale
(1,
2,
3,
5,
8,
13,
21...)
• Iden7fy
a
reference
story
set
– Use
most
understood
story
as
a
reference
story
for
each
level
on
the
scale
• Es7mate
the
rest
– Everybody
es7mates
individually,
then
reveals
as
a
team,
hence
the
term
“Planning
Poker”
Please dial into (218) 895-4640 PIN: 3289145
h?p://agile.conscires.com/
20. How
to
resolve
disagreement
in
es<ma<on?
• Consensus
– Ask
the
outliers
and
discuss
as
a
team
to
agree
on
an
es7mate
• Majority
– Pick
the
one
that
was
chosen
by
the
majority
• Choose
the
highest
h?p://agile.conscires.com/
21. Summary
• Define
your
challenges
• Set
realis7c
expecta7on
– Mastery
is
not
achieved
overnight
h?p://agile.conscires.com/
24. Dona7on
only
1
day
Trainings
in
US
– Irvine–
Nov
18th
• h?p://agile.conscires.com/1-‐day-‐agile-‐scrum-‐training-‐
irvine-‐10/
– Atlanta–
Nov
18th
• h?p://agile.conscires.com/1-‐day-‐agile-‐scrum-‐training-‐
atlanta-‐03/
– Las
Vegas–
Dec
2
• h?p://agile.conscires.com/1-‐day-‐agile-‐scrum-‐training-‐
lasvegas-‐02/
– Phoenix–
Dec
9
• h?p://agile.conscires.com/1-‐day-‐agile-‐scrum-‐training-‐
phoenix-‐03/