<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://www.kai-mai.com">
<channel>
 <title>Kai Mai&#039;s Blog - Take Back the Web - Nodes for development</title>
 <link>http://www.kai-mai.com/tags/development</link>
 <description>Nodes containing the tag development</description>
 <language>en</language>
<item>
 <title>Notes &amp; Thoughts On the Presentation &quot;Scrum at Borland&quot; at SDForum&#039;s SEM SIG</title>
 <link>http://www.kai-mai.com/node/110</link>
 <description>&lt;p&gt;
I am a big fan of agile development, especially Scrum and test-driven development.
&lt;/p&gt;
&lt;p&gt;
On Sept 20th, I attended the presentation &lt;a href=&quot;http://sdforum.com/index.cfm?fuseaction=Calendar.eventDetail&amp;eventID=12926&quot;&gt;SCRUM at Borland: A Case Study of Transition&lt;/a&gt;
hosted by &lt;a href=&quot;http://www.sdforum.org/index.cfm?fuseaction=Page.viewPage&amp;pageId=672&amp;parentID=659&quot;&gt;SEM SIG&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
It&#039;s a very good presentation about how Borland adopted &lt;a href=&quot;http://www.controlchaos.com/&quot;&gt;Scrum&lt;/a&gt;, and the insights and lessons learned.  
&lt;/p&gt;
&lt;p&gt;
The presentation slides can be downloaded &lt;a href=&quot;http://f1.grp.yahoofs.com/v1/0GglRwXdWL919noe5E5RSQjsiXPdz_HKvnJXGthulTRPNyEozp5RX922TcE-1LUR_65ClsBlFXm6hqwnU48w-V0HVogv/Speaker%20Presentations/2007/AgileAction09202007.ppt&quot;&gt;here&lt;/a&gt;.  But you must sign up for &lt;a href=&quot;http://groups.yahoo.com/group/sdforum_semsig&quot;&gt;SEM SIG Yahoo group&lt;/a&gt;.   If you have problem with the download link, you can browse the file folder of the Yahoo group to find it.   There are other past presentations available for download as well.
&lt;/p&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/72&quot;&gt;development&lt;/a&gt; &lt;a href=&quot;tags/143&quot;&gt;agile&lt;/a&gt; &lt;a href=&quot;tags/144&quot;&gt;scrum&lt;/a&gt; &lt;a href=&quot;tags/145&quot;&gt;sdforum&lt;/a&gt; &lt;a href=&quot;tags/146&quot;&gt;borland&lt;/a&gt; &lt;a href=&quot;tags/201&quot;&gt;methodology&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">development</category>
 <category domain="http://www.technorati.com/tag">agile</category>
 <category domain="http://www.technorati.com/tag">scrum</category>
 <category domain="http://www.technorati.com/tag">sdforum</category>
 <category domain="http://www.technorati.com/tag">borland</category>
 <category domain="http://www.technorati.com/tag">methodology</category>
 <pubDate>Sat, 27 Oct 2007 19:57:46 -0700</pubDate>
</item>
<item>
 <title>Can QAs Find Too Many Bugs?</title>
 <link>http://www.kai-mai.com/node/56</link>
 <description>&lt;p&gt;
I have been taking the responsiblity of monitoring a bug-tracking queue for a product at work.
&lt;/p&gt;
&lt;p&gt;
Sheila, the &lt;a href=&quot;http://en.wikipedia.org/wiki/Quality_Assurance&quot;&gt;QA&lt;/a&gt; in my group, has been opening many bug tracking calls and flooded the queue. She asked me if she has opened too many bug calls (in other words, found too many bugs (BTW, most of them are not my bugs)).  Apparently, some people don&#039;t like seeing many bug calls. 
I&#039;d rather see QAs find as many bugs as they can and report them, rather than not trying to find them or not reporting them. Even if they are not sure whether it is a bug, a tracking call should still be opened to track it and determine whether it&#039;s a real bug.
&lt;/p&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/72&quot;&gt;development&lt;/a&gt; &lt;a href=&quot;tags/76&quot;&gt;qa&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">development</category>
 <category domain="http://www.technorati.com/tag">qa</category>
 <pubDate>Thu, 16 Mar 2006 19:09:44 -0800</pubDate>
</item>
<item>
 <title>Framework, CMS - What Do I Really Want from a Web Application Rapid Development Kit</title>
 <link>http://www.kai-mai.com/node/52</link>
 <description>&lt;p&gt;
Inspired by the blog &lt;a href=&quot;http://www.robertpeake.com/index.php?/archives/125-What-I-Want-From-A-Framework.html&quot;&gt;What I Want From A Framework&lt;/a&gt;, I want to discuss what I want from a web application rapid development kit(WARDK) as a lazy developer.  I am going to use PHP language as an example in my discussion, but the discussion can apply to other languages such as Java, Ruby, and Python.
&lt;/p&gt;
&lt;p&gt;
Here’s what I want:
the most important and common features (every web application that supports multiple users need to have these):
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; user management(CRUD operations on users, ban users, user group management), pluggable authentication(LDAP, &lt;a href=&quot;http://openid.net/&quot;&gt;OpenID&lt;/a&gt;, integration with other systems) &lt;a href=&quot;http://openid.net/&quot;&gt;OpenID&lt;/a&gt;)
&lt;/ul&gt;
&lt;p class=&quot;awTags_TagLinks&quot;&gt;Tags: &lt;a href=&quot;tags/47&quot;&gt;java&lt;/a&gt; &lt;a href=&quot;tags/65&quot;&gt;php&lt;/a&gt; &lt;a href=&quot;tags/69&quot;&gt;web&lt;/a&gt; &lt;a href=&quot;tags/70&quot;&gt;application&lt;/a&gt; &lt;a href=&quot;tags/71&quot;&gt;framework&lt;/a&gt; &lt;a href=&quot;tags/72&quot;&gt;development&lt;/a&gt; &lt;a href=&quot;tags/73&quot;&gt;ruby&lt;/a&gt; &lt;a href=&quot;tags/74&quot;&gt;python&lt;/a&gt; &lt;/p&gt;</description>
 <category domain="http://www.technorati.com/tag">java</category>
 <category domain="http://www.technorati.com/tag">php</category>
 <category domain="http://www.technorati.com/tag">web</category>
 <category domain="http://www.technorati.com/tag">application</category>
 <category domain="http://www.technorati.com/tag">framework</category>
 <category domain="http://www.technorati.com/tag">development</category>
 <category domain="http://www.technorati.com/tag">ruby</category>
 <category domain="http://www.technorati.com/tag">python</category>
 <pubDate>Wed, 15 Mar 2006 21:10:03 -0800</pubDate>
</item>
</channel>
</rss>

