Software Development Cross Solution - Index of - Free

Put assumptions on trial for their lives
When it comes to requirements, no assumption is a good
assumption. So whenever planing poker turns up your team’s
assumptions, don’t let that assumption into your project without first
doing everything you can to beat it out of your project...
At least you know what you don’t know
Put every assumption on trial
You’re aiming for as few assumptions as possible
when making your estimates. When an assumption
rears its head in planning poker, even if your entire
team shares the assumption, expect that assumption to
be wrong until it is clarified by the customer.
As opposed to not knowing what
you don’t know...
No matter how hard you try, some assumptions really will survive clarification with
the customer. That’s OK. Sometimes the customer doesn’t have a great answer to
a particular assumption at the beginning of a project, and in those cases you need
to live with the assumption. The important thing is that you know that there is an
assumption being made, and you can write it down as a risk for that user story (like on
the back of your user story card). This helps you keep an eye on and track your risks,
knocking them out at a later stage in your project.
gathering requirements
Depending on customer
priority, you might even
decide to delay the
development of a user
story that has a number of
surviving assumptions until
they can be clarified.
While you can’t always get rid of all
assumptions, the goal during estimation
is to eliminate as many assumptions as
possible by clarifying those assumptions
with the customer. Any surviving
assumptions then become risks.
Download at WoweBook.Com
you are here 4 51