wiki.accu.org

User Tools

Site Tools

Trace:
2015:noestimates_does_not_mean_no_estimates

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
2015:noestimates_does_not_mean_no_estimates [2014/11/04 13:50] – created jonjagger2015:noestimates_does_not_mean_no_estimates [2016/06/11 14:05] (current) – external edit 127.0.0.1
Line 1: Line 1:
 Back to [[conference:committee:2015-proposals]]\\ Back to [[conference:committee:2015-proposals]]\\
 \\ \\
-**Title**: #NoEstimates does not mean "no estimates"\\+**Title**: NoEstimates does not mean 'no estimates'\\
 **Proposer**: [[2015:Seb Rose]]\\ **Proposer**: [[2015:Seb Rose]]\\
 **Type**: Tutorial\\ **Type**: Tutorial\\
Line 8: Line 8:
 The #NoEstimates hashtag has been generating a lot of heat in software The #NoEstimates hashtag has been generating a lot of heat in software
 development circles for the past couple of years, but what does it development circles for the past couple of years, but what does it
-really mean? It’s time to find out.\\+really mean? It's time to find out.\\
 \\ \\
 When Woody Zuill first started using the hashtag he sparked a debate When Woody Zuill first started using the hashtag he sparked a debate
 that has caused tempers to flare and blood to boil, but Woody himself that has caused tempers to flare and blood to boil, but Woody himself
-doesn’t think that estimates are inherently bad:\\+doesn't think that estimates are inherently bad:\\
 \\ \\
-“If our response every time we reach the end of a project is to say ‘we +If our response every time we reach the end of a project is to say 'we 
-must produce better estimates’ then we’re in a cycle of continuous ‘no +must produce better estimates' then we're in a cycle of continuous 'no 
-improvement’”\\+improvement'\\
 \\ \\
-In this session we’ll cut through the #NoEstimates rhetoric and sketch+In this session we'll cut through the #NoEstimates rhetoric and sketch
 out the dysfunctions at the heart of software development that gave rise out the dysfunctions at the heart of software development that gave rise
-to the hashtag in the first place. We’ll investigate some possible ways+to the hashtag in the first place. We'll investigate some possible ways
 that we can turn this around, so that we can improve the outcomes for that we can turn this around, so that we can improve the outcomes for
 customers AND development teams. We might even find out how to use customers AND development teams. We might even find out how to use
 estimates effectively.\\ estimates effectively.\\
 \\ \\
-\\ +The Cucumber for Java Book - Seb Rose, Matt Wynne & Aslak Hellesoy
-The Cucumber for Java Book - Seb Rose, Matt Wynne & Aslak Hellesøy+
 Now available from the Pragmatic Press - Now available from the Pragmatic Press -
 https://pragprog.com/book/srjcuc/the-cucumber-for-java-book\\ https://pragprog.com/book/srjcuc/the-cucumber-for-java-book\\
2015/noestimates_does_not_mean_no_estimates.1415109039.txt.gz · Last modified: 2016/06/11 14:05 (external edit)