<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Changes to DetailedSuggestionStatus</title>
    <description/>
    <link>http://www.motiro.org/en-us</link>
    <language>en-us</language>
    <generator>Motiro</generator>
    <pubDate>Fri, 29 Feb 2008 10:18:03 -0500</pubDate>
    <ttl>60</ttl>
<item><title>Detailed suggestion status</title><description>&lt;p&gt;This suggestion is related to &lt;a class="done" href="http://www.motiro.org/wiki/show/MarcarSugestoesQueEstaoEmDesenvolvimento"&gt;Suggestion status report&lt;/a&gt;&lt;/p&gt; &lt;p&gt;A checkbox is very good for binary states &lt;span style="background: #ffb8b8"&gt;liki&lt;/span&gt;&lt;span style="background: #b8ffb8"&gt;like&lt;/span&gt; done/not done, but suggestion life cycles use to be a little more complex than that for many teams. &lt;span style="background: #ffb8b8"&gt;Done&lt;/span&gt;&lt;span style="background: #b8ffb8"&gt;&amp;quot;Done&amp;quot;&lt;/span&gt; leaves pretty much no doubt (what is done is done), but the &amp;quot;not done&amp;quot; state can be broken into many smaller states like approved/accepted, under development, under revision or acceptance testing.&lt;/p&gt; &lt;p&gt;For some teams many of these states do not make any sense, but for other they do. Maybe having a fixed set of states will not be a very good idea. Too many states will make people &lt;span style="background: #b8ffb8"&gt;slower to&lt;/span&gt; decide &lt;span style="background: #ffb8b8"&gt;slowly&lt;/span&gt; and too little will be limiting. A better approach is having a free text field to let the team decide for themselves what makes sense for them. This field should provide completion suggestion with previously entered values to avoid indecision.&lt;/p&gt;</description><pubDate>Fri, 29 Feb 2008 10:18:03 -0500</pubDate><dc:creator>thiagoarrais</dc:creator><guid>http://www.motiro.org/wiki/show/DetailedSuggestionStatus?revision=2</guid></item><item><title>Detailed suggestion status</title><description>&lt;p&gt;This suggestion is related to &lt;a class="done" href="http://www.motiro.org/wiki/show/MarcarSugestoesQueEstaoEmDesenvolvimento"&gt;Suggestion status report&lt;/a&gt;&lt;/p&gt;&lt;p&gt;A checkbox is very good for binary states liki done/not done, but suggestion
life cycles use to be a little more complex than that for many teams. Done
leaves pretty much no doubt (what is done is done), but the &amp;quot;not done&amp;quot; state can
be broken into many smaller states like approved/accepted, under development,
under revision or acceptance testing.&lt;/p&gt;&lt;p&gt;For some teams many of these states do not make any sense, but for other they
do. Maybe having a fixed set of states will not be a very good idea. Too many
states will make people decide slowly and too little will be limiting. A better
approach is having a free text field to let the team decide for themselves what
makes sense for them. This field should provide completion suggestion with
previously entered values to avoid indecision.&lt;/p&gt;</description><pubDate>Tue, 31 Jul 2007 19:07:17 -0400</pubDate><dc:creator>thiagoarrais</dc:creator><guid>http://www.motiro.org/wiki/show/DetailedSuggestionStatus?revision=1</guid></item>  </channel>
</rss>
