<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3157" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<DIV><SPAN class=210361919-19122007>> </SPAN>Thanks -- that makes sense, but
we have some change-resistant folks here who hate ESP but are <BR><SPAN
class=210361919-19122007>> </SPAN>deeply attached to their current priority
scheme (which was an addon to ESP also!) such that to get them<BR><SPAN
class=210361919-19122007>> </SPAN>into Bugzilla I have to deliver
this.<BR><BR><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff
size=2>Sorry to hear that, man. That's not fun to fight that kind of
battle, but here's some ammunition for you.</FONT></SPAN></DIV>
<DIV><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff size=2><SPAN
class=210361919-19122007><FONT face=Arial color=#0000ff size=2>Consider the
value of knowing that a bug fix has a set deadline, versus saying that
a bug must be fixed for a particular release (target milestone), while retaining
the ability to know a sense of how urgent the fix is to the customer (severity)
and how critical something is to fix "right now" versus holding off a bit while
keeping deadline and milestone in effect?</FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff size=2><SPAN
class=210361919-19122007></SPAN></FONT></SPAN> </DIV>
<DIV><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff size=2><SPAN
class=210361919-19122007><SPAN class=210361919-19122007><FONT face=Arial
color=#0000ff size=2>In our installations, we have separated out the enhancement
severity and created a new column, bug_type that contains the values defect
and enhancement, among others. Then, severity belongs to the
"customer" and priority belongs to the "developer" in whatever sense that holds
true. This works extremely well on one of our installations for a wide
variety of projects covering on the order of 3,000 users and well over 50K
bugs.</FONT></SPAN></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff size=2><SPAN
class=210361919-19122007><SPAN
class=210361919-19122007></SPAN></SPAN></FONT></SPAN> </DIV>
<DIV><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff size=2><SPAN
class=210361919-19122007><SPAN class=210361919-19122007><SPAN
class=210361919-19122007><FONT face=Arial color=#0000ff size=2>I don't know if
you're familiar with Agile development methods at all (specifically Scrum),
however, I would hope that you can take one particular plus away from it:
When a small team of developers commits to a limited set of tasks over a short
period of time, things often get done very rapidly due to the narrow focus over
the short term. It's that definition of the small list of tasks that are
immediately important that determine what gets done in the short time window the
team is commited to that helps the team perform very efficiently so long as
those priorities don't change during the development cycle. This does not
mean that scheduling priorities beyond the short term can be skipped. On
the contrary, knowing that we're going to LA from NYC is critical, but to get
there, we still have to get in the car and take one state at a time. If we
don't like the road we're taking now, we can make small corrections along the
way, but we don't decide to take I-80 most of the way then 2/3rds of the way
through decide to take a Gulf-coast
route...</FONT></SPAN></SPAN></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff size=2><SPAN
class=210361919-19122007><SPAN class=210361919-19122007><SPAN
class=210361919-19122007></SPAN></SPAN></SPAN></FONT></SPAN> </DIV>
<DIV><SPAN class=210361919-19122007><FONT face=Arial color=#0000ff size=2>Good
luck,</FONT></SPAN></DIV>
<DIV><SPAN class=210361919-19122007></SPAN> </DIV>
<DIV><SPAN class=210361919-19122007></SPAN><SPAN class=210361919-19122007><FONT
face=Arial color=#0000ff size=2>Kevin</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV>
<DIV dir=ltr align=left><SPAN
style="COLOR: green; mso-no-proof: yes">----<BR></SPAN><B><SPAN
style="FONT-SIZE: 8pt; COLOR: green; FONT-FAMILY: Arial; mso-no-proof: yes">Kevin
Benton<BR></SPAN></B><SPAN
style="FONT-SIZE: 8pt; COLOR: green; FONT-FAMILY: Arial; mso-no-proof: yes">MySQL
DBA #5739<BR>Senior Software Developer</SPAN><B><SPAN
style="FONT-SIZE: 8pt; COLOR: green; FONT-FAMILY: Verdana; mso-no-proof: yes"><BR></SPAN></B><SPAN
style="FONT-SIZE: 8pt; COLOR: green; FONT-FAMILY: Arial; mso-no-proof: yes">CAD
Global Infrastructure Flow Services<BR>Advanced Micro Devices<BR>2950 E
Harmony Rd<BR>Fort Collins, CO<SPAN style="mso-spacerun: yes">
</SPAN>80528<BR><BR></SPAN><SPAN
style="FONT-SIZE: 7.5pt; COLOR: green; FONT-FAMILY: Arial; mso-no-proof: yes">The
opinions stated in this communication do not necessarily reflect the view of
Advanced Micro Devices and have not been reviewed by management. This
communication may contain sensitive and/or confidential and/or proprietary
information. Distribution of such information is strictly prohibited
without prior consent of Advanced Micro Devices. This communication is
for the intended recipient(s) only. If you have received this
communication in error, please notify the sender, then destroy any remaining
copies of this communication.</SPAN></DIV></DIV></BLOCKQUOTE></BODY></HTML>