<head>
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Op 1-9-2010 20:13, barrettdab schreef:
<blockquote cite="mid:i5m53i+***@eGroups.com" type="cite">
<span style="display: none;"> </span>
<div id="ygrp-text">
<p>But this is reality for many, many developers. In many
companies, the programmers that built something become the
SME's when support issues come up. Not just bug fixes, but
ad hoc reporting, performance management, data fixes,
consulting and training, and God knows what else. And if
all the experts are working on new development? Tough.
Business has to keep on going day to day.<br>
</p>
</div>
</div>
</div>
</blockquote>
True. <br>
<br>
Things like reporting, appraisels, drinking a cup of hot chocolate,
getting trained, going to the toilet, having meetings are a fact of
(business) life, and necessary. It is not overhead and if it doesn't
get out of hand there is nothing wrong with it and I won't be
claiming that a developer should be coding for 100% of his available
type.<br>
<br>
I didn't list support, for a good reason. "Support" is a rather big
area to address. If the company doesn't have a kind of customer
support I would strongly advise to try to get a separate customer
support. I've seen a separate customer support role in even the
smallest companies. And if not then the PO or SM could take up the
role. As a ScrumMaster I've done that, filtering out many requests
that would otherwise had to be handled by the developers directly.
The cool thing about doing this is that you get a rather good idea
where the team is lacking some practices.<br>
<br>
Defects always seem to be urgent, especially if people have learned
that the only way to get their complaints fixed is by being a
nuisance. Therefore you need good triage. You can develop some
simple guidelines for classification, but even then the hard part is
to stick with it.<br>
<br>
Now there will be some defects of the type 'urgent & important'.
This kind of defects can't be put on the backlog for next sprint and
must be handled now. It is a valid reason for a sprint termination.
And the most important thing is then looking at why you ever
released a product with this kind of defect and what will be changed
to avoid it next time.<br>
<br>
If the large part of the defects that is flowing in is of this type
you should either take a good look at your triage or accept the fact
that what you've done in the past wasn't good enough and stop
developing new stuff until you have fixed the quality issues. You
can't build on a flaky foundation.<br>
<br>
<blockquote cite="mid:i5m53i+***@eGroups.com" type="cite">
<div id="ygrp-mlmsg" style="position: relative;">
<div id="ygrp-msg" style="z-index: 1;">
<div id="ygrp-text">
<p>
Personally, I think it would be a real shame if we said to
everyone working in those circumstances (which I strongly
suspect is a large majority of programmers out there in
the real world), "Sorry, unless you're in a team totally
dedicated to single, multi-iteration project doing
greenfield development without any maintenance
responsibilities, you can't do Scrum". Mostly, because
it's not true.<br>
</p>
</div>
<div style="color: rgb(255, 255, 255); height: 0pt;"><br>
</div>
</div>
</div>
</blockquote>
I don't think "Scrum" is suitable for all contexts, especially if
you are not willing to live up to some basic rules. I think that you
might miss out on some benifits that you can get if you would, but
that doesn't mean that you can't do effective software development.
You should do Scrum if you think the benifits outweigh the costs, if
not find something that better suits you. <br>
<br>
Maurice.<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.scrummaster.nl">http://www.scrummaster.nl</a> / <a class="moz-txt-link-freetext" href="http://twitter.com/scrumnl">http://twitter.com/scrumnl</a></pre>
<!-- |**|begin egp html banner|**| -->
<br>
<br>
<!-- |**|end egp html banner|**| -->
<div width="1" style="color: white; clear: both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- |**|begin egp html banner|**| -->
<br><br>
<tt>
To Post a message, send it to: ***@eGroups.com<BR>
To Unsubscribe, send a blank message to: scrumdevelopment-***@eGroups.com</tt>
<br><br>
<!-- |**|end egp html banner|**| -->
<!-- |**|begin egp html banner|**| -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=1569064/grpspId=1707209021/msgId=48219/stime=1283372701" width="1" height="1"> <br>
<!-- |**|end egp html banner|**| -->
<!-- |**|begin egp html banner|**| -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px solid #666; padding: 5px 0;" >
Your email settings: Individual Email|Traditional <br>
<a href="http://groups.yahoo.com/group/scrumdevelopment/join;_ylc=X3oDMTJmdm1jMG9kBF9TAzk3NDc2NTkwBGdycElkAzE1NjkwNjQEZ3Jwc3BJZAMxNzA3MjA5MDIxBHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyODMzNzI3MDE-">Change settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:scrumdevelopment-***@yahoogroups.com?subject=Email Delivery: Digest">Switch delivery to Daily Digest</a> | <a href = "mailto:scrumdevelopment-***@yahoogroups.com?subject=Change Delivery Format: Fully Featured">Switch to Fully Featured</a> <br>
<a href="http://groups.yahoo.com/group/scrumdevelopment;_ylc=X3oDMTJkMjA0ZWIxBF9TAzk3NDc2NTkwBGdycElkAzE1NjkwNjQEZ3Jwc3BJZAMxNzA3MjA5MDIxBHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjgzMzcyNzAx">
Visit Your Group
</a> |
<a href="http://docs.yahoo.com/info/terms/">
Yahoo! Groups Terms of Use
</a> |
<a href="mailto:scrumdevelopment-***@yahoogroups.com?subject=Unsubscribe">
Unsubscribe
</a>
<br>
</div>
<br>
<!-- |**|end egp html banner|**| -->
<div style="color: white; clear: both;"/>__,_._,___</div>
</body>
</html>