<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Buy Bentyl Without Prescription &raquo; We Always Have The Cheapest Offers In Our Online-Drugstore</title>
	<atom:link href="http://www.agileadvice.com/tag/risk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agileadvice.com</link>
	<description>All Things Agile: Scrum, OpenAgile, XP &#38; Lean</description>
	<lastBuildDate>Sat, 04 Feb 2012 19:54:25 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Buy Bentyl Without Prescription &raquo; We Always Have The Cheapest Offers In Our Online-Drugstore</title>
		<link>http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/</link>
		<comments>http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 14:54:24 +0000</pubDate>
		<dc:creator>Christian Gruber</dc:creator>
				<category><![CDATA[Agile Management]]></category>
		<category><![CDATA[Scrum, XP and Lean]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[capabilities]]></category>
		<category><![CDATA[christian edward gruber]]></category>
		<category><![CDATA[estimation]]></category>
		<category><![CDATA[Israfil]]></category>
		<category><![CDATA[management]]></category>
		<category><![CDATA[Metrics]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[risk]]></category>
		<category><![CDATA[scrum]]></category>
		<category><![CDATA[status]]></category>
		<category><![CDATA[truthfulness]]></category>
		<category><![CDATA[velocity]]></category>

		<guid isPermaLink="false">http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/</guid>
		<description><![CDATA[<p>The question of "expected velocity" and long-term planning has come up at more than one client. A recent client conversation got me thinking, however, questioning how to interpret velocity when estimating and plotting a roadmap based on a current backlog of features. Assume, for a moment, a backlog of story-pointed features, and 10 good iterations (consistent team, no odd occurrences that would affect velocity). Mathematically average velocity (well, a mean really) is a 50/50 proposition for any subsequent iteration. Some organizations don't find this level of confidence acceptable. What velocity should be reported as expected for iteration/sprint planning and roadmap forecasting, and how should it be used?</p>]]></description>
			<content:encoded><![CDATA[<p> <p> <b>Buy amaryl without prescription</b>, The question of "expected velocity" and long-term planning has come up at more than one client. A recent client conversation got me thinking, however, questioning how to interpret velocity when estimating and plotting a roadmap based on a current backlog of features, <b>cheap amaryl</b>. Assume, for a moment, <b>Order amaryl online</b>, a backlog of story-pointed features, and 10 good iterations (consistent team, no odd occurrences that would affect velocity). Mathematically average velocity (well, <b>amaryl approved</b>, a mean really) is a 50/50 proposition for any subsequent iteration. Some organizations don't find this level of confidence acceptable. What velocity should be reported as expected for iteration/sprint planning and roadmap forecasting, and how should it be used?<br /></p><h2>Context</h2>Interpreting velocity, before anything else, requires some context, <b>buy amaryl without prescription</b>.  <b>Order amaryl from canada</b>, An agile organization that sees estimates as hypothetical might find this article is of less use. In fact, a good question is <a href="http://epistemologic.com/2008/07/02/you-dont-need-story-points-either/">whether estimation is even a value-added activity</a>. For this post assume an organization that sees strong value in estimation and planning.<br /><h3>Culture</h3>The biggest piece of context is to know the organizational culture, <b>buy amaryl internet</b>. This is important in two respects, and both of these cultural factors are important because they impact how Velocity is understood within the organization.<br /><h4>What is Failure?</h4>First is the meaning of failure in the organization.  <b>Buy amaryl without prescription</b>, Is failure to deliver what was committed to by the planned date considered a failure of the team, or is it simply a fact to be understood and accounted for in future planning.  <b>Find cheap amaryl online</b>, Even in Agile organizations, the former is often true and a hard habit to break. If not delivering to expectations is considered failure and has negative consequences, then that means that estimation is being treated not as estimation, <b>find discount amaryl online</b>, but as prediction and contract. Velocity is therefore a commitment, <b>Buy cheap amaryl internet</b>, and should therefore be used conservatively.<br /><h4>Consistency or Speed?</h4>The second item to know is whether consistency and predictability of delivery is of a higher strategic value than the actual rate of delivery. This is often un-stated. Usually people want fast and consistent delivery, <b>buy amaryl without prescription</b>. The truth is that you can get consistent, or fast software development, <b>amaryl pharmacy online</b>, or a balance between the two. Lack of trust is usually a strong motivation to encourage consistency over speed, <b>Drug amaryl online purchase</b>, or a history of quality problems, etc. In this case, as well, <b>low cost amaryl</b>, Velocity is more of a boundary than an indicator.<br /><h3>Emotional Loading in Estimation (or why not Low-ball?)</h3>If estimation is seen as binding, contractual, <b>Amaryl</b>, or limiting, then additional emotions get overloaded. Trust, promise, <b>amaryl in uk</b>, and betrayal are words used in such organizational cultures.  <b>Buy amaryl without prescription</b>, Distrust is usually a strong factor, especially between silos (business vs. technology, <b>Sale amaryl</b>, company vs. project management vs. customer, etc.), <b>order cheap amaryl online</b>. So when people are asked to give estimates, even using agile-friendly mechanisms such as story points, <b>Cheap amaryl tablets</b>, there is usually a process of cementing that estimate into a part of an accountability model, so estimates start to get conservative. People are then accused of low-balling, others are accused of irrational expectations.., <b>buy amaryl without prescription</b>. we've all seen this. The language clearly becomes one of contention and blame, <b>buy discount amaryl online</b>. Even the term low-balling is often an outright pejorative term for estimating too conservatively.</p>
<p><p>This doesn't happen only in agile environments, <b>Cheap amaryl in usa</b>, and project managers in traditional PMBOK frameworks have long factored risk into "contingency budgets".  <b>Buy amaryl without prescription</b>, Interestingly, however, if a Project Manager were to factor risk into the task estimates, they'd be "low-balling capacity," yet if they were to factor it out and layer it on top of the project work, it's "contingency budgeting" (At least in a few experiences I've had). Either way, someone's adding a factor for uncertainty, based on the need to predict conservatively or liberally or somewhere in between.</p><p>That's the point of the article: how can Agile projects use velocity to estimate as conservatively (or liberally) as is appropriate?<br /></p><h2>An average is a 50% chance to succeed (or fail)</h2>Velocity is not a constant, <b>amaryl online review</b>. It's a set of instantaneous values on a curve, with instances being iterations.  <b>Amaryl online stores</b>, That means that it varies, and is therefore only meaningful statistically. So how do you reasonably use velocity statistically, <strong>and</strong> improve confidence, <b>approved amaryl pharmacy</b>. One way is to stop delivering against "average" velocity, <b>buy amaryl without prescription</b>.</p>
<p><p>A lot of coaches use average velocity over the previous N iterations. This is not helpful for all sorts of reasons, <b>Amaryl information</b>, if estimation is a commitment. By definition, average (well, actually a mean, <b>amaryl professional</b>, but they're close) is a 50/50 proposition. If you report the average team velocity (assuming it's accurate), <b>Amaryl pills</b>, then about half the time the team will be under and about half the time the team will be over, statistically.  <b>Buy amaryl without prescription</b>, So basically an average is a crap shoot, when taken in any given instance. <strong>It's can only be good in the long run.</strong> For this to work, the long-haul has to include permission to fail and a lot of trust, <b>amaryl india</b>. Teams need to be able to go miss dates but will sometimes exceed dates and it should all wash out in the end. In organizations such as I'm describing, <b>Cheap amaryl from canada</b>, that trust isn't there, so. Additionally, if the language of commitment is around meeting instantaneous iteration commitments (as opposed to delivering high-quality customer value as quickly as is sustain-ably possible) then you aren't playing the long-game, <b>canadian pharmacy amaryl</b>, you're playing a very short-game.<br /></p><h3>Simulate Velocity, not work</h3><p>In a PMI training course I took when I was at Sun Microsystems, <b>Fda approved amaryl</b>, we were nicely informed that two point estimates of tasks are a perfect way to fail half the time, per the above logic. One point estimates are just idiotic, <b>buy amaryl without prescription</b>. Three point estimates were better. We simulated with a monte-carlo algorithm and found a curve and a distribution, <b>amaryl cheap price</b>, and then determined a confidence level yadda yadda. Well, <b>Find amaryl online</b>, we're trying to avoid wasting a lot of time estimating up-front, but one way to start representing velocity properly is to do the same kind of statistical modelling done in traditional product management, only simulate velocity, not work items.</p><p>In this approach, <b>discount amaryl no rx</b>, you take the last N iterations (say 10). Determine the maximum velocity (optimistic) and the minimum velocity (pessimistic), <b>Amaryl non prescription</b>, and then the mode (the velocity value that seems to occur most frequently).  Then you do <a href="http://en.wikipedia.org/wiki/Monte_Carlo_method">monte-carlo simulation</a> <b>Buy amaryl without prescription</b>, so you get a statistical pattern. Now, you actually can determine an answer based on confidence. If you want to be right with an 80% confidence, <b>purchase amaryl no rx</b>, you pick a velocity where 80% of the simulated runs were successful. (Note - there are a paucity of excel templates to do this math automatically, <b>Amaryl uk</b>, and often they are for sale. It would be nice to have a few functions with arbitrary distributions based on min-max-mode to help this along.)</p><p>It's not perfect, and it's a potentially huge amount of administrative overhead. Elsewhere I've referenced blogs that entirely oppose any estimation at all, but if you are gong to, then working statistically with simulation is the only way to take small sample numbers meaningful.</p><h3>Commitment Velocity: Low-Ball as a policy.</h3><p>Another approach, one perhaps controversial, but taught by some Scrum trainers is to pick the lowest historical delivered velocity, <b>buy amaryl without prescription</b>. This is a commitment-based approach, <b>cheap amaryl</b>, on the assumption that building trust around consistent delivery is critical to building sound relationships where product owners and teams can safely state their needs and get things done with a minimum of contractual behaviour. By taking the minimum, <b>Buy amaryl on line</b>, you force a low-ball capacity, which means you can have high-confidence of success after a few iterations. You have, likely, <b>amaryl medicine</b>, after a while, some spare time on your hands.  <b>Purchase amaryl overnight delivery</b>, Teams can then choose to pull more work in (without adjusting their commitment velocity), work on "technical debt", improve their skills, etc, <b>buy amaryl in canada</b>.  <b>Buy amaryl without prescription</b>, A team could raise their commitment velocity in certain inflection points in the project. A new team member is added that provides a necessary skill not previously available, and after a few iterations the team is consistently hitting a higher number, <b>Best price amaryl</b>, but this is a careful process to ensure that they are committing, and if they don't make their new number, it goes down to what they got accomplished.</p><h3>Indemnify teams' learning</h3><p>An arguably healthier option, if you have built enough trust, is to simply indemnify a team from failing to meet the estimate. Since you're doing mathematics on actuals to generate an expected future number, everyone can acknowledge that past behaviour is no guarantee of future behaviour, and simply use it for capacity planning. In this case, estimation is actually estimation, not commitment or contract. The team is expected to be ahead sometimes, and behind sometimes. The upside of this is that a lot of extra time isn't spent playing with fictional numbers, <b>buy amaryl without prescription</b>. Teams are spending their efforts on delivery as quickly-yet-sustain-ably as they can, and the organization treats them as trusted professionals in this. The temptation to assume you can predict the future is seen as folly, and the estimates are used to guide overall direction, not to make outward customer commitments.</p><h2>Don't be mindless</h2><p>There may be other approaches, I'm sure. The agile community is certainly not short of people who love this topic and can talk for hours on "proper" estimation. The point of this post is merely to point out some options, and ask you to look at your organizational culture, team culture, customer culture, the meaning of terms like commitment, failure, success, consistency, speed, etc.  <b>Buy amaryl without prescription</b>, As you understand the culture, balance consistency vs. speed, trust, and other factors to choose a method of estimation that meets your goals. Don't do estimation based on your own, internal cultural assumptions, as you may have developed or been taught techniques that are useful when and where they were taught, but may no longer be so. Or maybe they weren't so useful then either. Regardless, this because estimation cuts at the heart of the dialogue between producer and consumer, and establishes parameters for that discussion, it's critical that you think your choice through.</p><p>[Christian also blogs at <a href="http://www.geekinasuit.com/">http://www.geekinasuit.com/</a>]</p>.</p>
<p></p>
<p><b>Similar posts:</b> <a href='http://www.agileadvice.com/?p=193'>Premarin online without prescription</a>. <a href='http://www.agileadvice.com/?p=192'>Tetracycline online without prescription</a>. <a href='http://www.agileadvice.com/?p=191'>Celexa online without prescription</a>. <a href='http://www.agileadvice.com/?p=190'>Erythromycin online without prescription</a>. <a href='http://www.agileadvice.com/?p=189'>Cymbalta online without prescription</a>. <a href='http://www.agileadvice.com/?p=188'>Ultracet online without prescription</a>. <a href='http://www.agileadvice.com/?p=187'>Zovirax online without prescription</a>. <a href='http://www.agileadvice.com/?p=186'>Benadryl online without prescription</a>. <a href='http://www.agileadvice.com/?p=185'>Claritin online without prescription</a>. <a href='http://www.agileadvice.com/?p=184'>Lamisil online without prescription</a>.<br />
<b>Trackbacks from:</b> <a href='http://www.donohueseatery.com/?p=328'>Buy amaryl without prescription</a>. <a href='http://studia.nzs.pl/?p=1100'>Buy cialis super active+ without prescription</a>. <a href='http://studia.nzs.pl/?p=782'>Buy benadryl without prescription</a>. <a href='http://www.donohueseatery.com/?p=216'>Buy fml without prescription</a>. <a href='http://www.donohueseatery.com/?p=436'>Buy cialis without prescription</a>. <a href='http://www.donohueseatery.com/?p=138'>Buy mojo maxx without prescription</a>. <a href='http://www.donohueseatery.com/?p=457'>Buy vastarel without prescription</a>. <a href='http://studia.nzs.pl/?p=1152'>Buy aggrenox without prescription</a>. <a href='http://www.donohueseatery.com/?p=289'>Buy alert caps (sleep & relaxation aid) without prescription</a>. <a href='http://www.bmmug.org/?p=67'>Buy cialis jelly without prescription</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.agileadvice.com/2009/01/23/scrumxplean/report-average-velocity-and-fail-50-of-the-time/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Buy Bentyl Without Prescription &raquo; We Always Have The Cheapest Offers In Our Online-Drugstore</title>
		<link>http://www.agileadvice.com/2008/03/19/miscellaneous/article-on-risk-and-the-brain/</link>
		<comments>http://www.agileadvice.com/2008/03/19/miscellaneous/article-on-risk-and-the-brain/#comments</comments>
		<pubDate>Wed, 19 Mar 2008 15:39:04 +0000</pubDate>
		<dc:creator>Mishkin Berteig</dc:creator>
				<category><![CDATA[Miscellaneous]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[brain]]></category>
		<category><![CDATA[risk]]></category>

		<guid isPermaLink="false">http://www.agileadvice.com/2008/03/19/miscellaneous/article-on-risk-and-the-brain/</guid>
		<description><![CDATA[This article called "To Bet Or Not To Bet: How The Brain Learns To Estimate Risk Buy bentyl without prescription, " is interesting, particularly because agile methods treat risk completely differently than traditional methods. Bentyl rx. Bentyl overnight shipping. Bentyl us. Order discount bentyl. Bentyl malaysia. Buy bentyl generic. Buy bentyl us. Bentyl information. Compare [...]]]></description>
			<content:encoded><![CDATA[<p> This article called "<a href="http://www.sciencedaily.com/releases/2008/03/080312093854.htm">To Bet Or Not To Bet: How The Brain Learns To Estimate Risk</a> <b>Buy bentyl without prescription</b>, " is interesting, particularly because agile methods treat risk completely differently than traditional methods.  Bentyl rx.  Bentyl overnight shipping.  Bentyl us.  Order discount bentyl.  Bentyl malaysia.  Buy bentyl generic.  Buy bentyl us.  Bentyl information.  Compare bentyl prices.  Canadian pharmacy bentyl.  Generic bentyl online.  Buy discount bentyl.  Order generic bentyl.  Buy bentyl in us.  Bentyl price.  Get bentyl.  Bentyl online sales.  Cheapest bentyl.  Bentyl medication.  Real bentyl without prescription.  Cheap bentyl from canada.  Cheap bentyl online.  Find discount bentyl online.  Bentyl professional.  Best price bentyl.  Bentyl pharmacy.  Cheap bentyl in usa.  Where to order bentyl.  Low cost bentyl.  Tablet bentyl.  Buying bentyl.  Buy cheapest bentyl.  Bentyl india.  Buy bentyl from us.  Order bentyl on internet.  Cheap price bentyl.  Order discount bentyl online.  Canadian bentyl.  Find cheap bentyl online.  Order cheap bentyl.</p>
<p></p>
<p><b>Similar posts:</b> <a href='http://www.agileadvice.com/?p=284'>Buy vasaka without prescription</a>. <a href='http://www.agileadvice.com/?p=283'>Buy vasotec without prescription</a>. <a href='http://www.agileadvice.com/?p=282'>Buy vastarel without prescription</a>. <a href='http://www.agileadvice.com/?p=281'>Buy vega h cream without prescription</a>. <a href='http://www.agileadvice.com/?p=280'>Buy ventolin without prescription</a>. <a href='http://www.agileadvice.com/?p=279'>Buy verapamil without prescription</a>. <a href='http://www.agileadvice.com/?p=278'>Buy vesicare without prescription</a>. <a href='http://www.agileadvice.com/?p=277'>Buy v-gel without prescription</a>. <a href='http://www.agileadvice.com/?p=276'>Buy viagrx without prescription</a>. <a href='http://www.agileadvice.com/?p=275'>Buy viamax without prescription</a>.<br />
<b>Trackbacks from:</b> <a href='http://www.donohueseatery.com/?p=265'>Buy bentyl without prescription</a>. <a href='http://www.donohueseatery.com/?p=28'>Buy speman without prescription</a>. <a href='http://www.coresample.info/?p=13'>Buy paxil without prescription</a>. <a href='http://www.donohueseatery.com/?p=85'>Buy probenecid without prescription</a>. <a href='http://www.donohueseatery.com/?p=295'>Buy acai natural energy boost without prescription</a>. <a href='http://studia.nzs.pl/?p=952'>Buy diflucan without prescription</a>. <a href='http://www.itplaysquake.com/?p=25'>Buy clomid without prescription</a>. <a href='http://studia.nzs.pl/?p=88'>Buy vermox without prescription</a>. <a href='http://www.bmmug.org/?p=39'>Buy zoloft without prescription</a>. <a href='http://www.donohueseatery.com/?p=343'>Buy nolvadex without prescription</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.agileadvice.com/2008/03/19/miscellaneous/article-on-risk-and-the-brain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

