<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Adept Technologies</title>
	<atom:link href="http://www.adeptechllc.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adeptechllc.com</link>
	<description>Software, Agile Process and Security</description>
	<lastBuildDate>Fri, 19 Mar 2010 15:57:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on I Miss my Treo by Julia</title>
		<link>http://www.adeptechllc.com/2010/03/12/i-miss-my-treo/comment-page-1/#comment-4640</link>
		<dc:creator>Julia</dc:creator>
		<pubDate>Fri, 19 Mar 2010 15:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=281#comment-4640</guid>
		<description>Only when my Treo finally bit the dust and I had to replace it, I too have made the switch from Palm to a Blackberry.  I went into Sprint and asked them what would be the best replacement for my Treo that had ease of messages and the best calendar, they suggest the PalmPixi.  At first I was excited because I loved my Treo so much I thought nothing but good things of Palm. The only thing I didn&#039;t like about my Treo was that it wasn&#039;t compatiable with Pandora&#039;s Internet Radio, I love that. But the Pixi did offer this feature so I wanted to upgrade.. Boy was that a mistake! I had the Pixi for not but a week and I couldn&#039;t take it. There was too much going on and the mostly touchscreen menu was not for me, I like to be able to scroll around with a left,right,up,down. So I opp for a BlackBerry that so many of my friends had raved about. I&#039;m still trying to adjust. I do like the apps that are offered and the navigation and themes that I never had on my Treo. But yes, the messages are scattered in 4 different places! This makes no sense to me. I do also like having the BlackBerry Messenger. But one thing I can not get over is how awful the calendar is!! I miss my Treo so much. I like having the color coded events to easily look at a month view see what colored icons I had going on that week and quickly be reminded what I had going on. I am actually amazed Blackberry has nothing similar. In fact, I don&#039;t know that any other device has a calendar that suits my needs like the PalmTreo. I struggle with this everyday, still waiting for someone to get on this. I love my blackberry, and am growingly getting attached to it, but I still consider giving it all up just to have my calendar back.
I miss my Treo.
Does anyone know of any solutions? Or calendar options? Or should I just go back to my Treo?</description>
		<content:encoded><![CDATA[<p>Only when my Treo finally bit the dust and I had to replace it, I too have made the switch from Palm to a Blackberry.  I went into Sprint and asked them what would be the best replacement for my Treo that had ease of messages and the best calendar, they suggest the PalmPixi.  At first I was excited because I loved my Treo so much I thought nothing but good things of Palm. The only thing I didn&#8217;t like about my Treo was that it wasn&#8217;t compatiable with Pandora&#8217;s Internet Radio, I love that. But the Pixi did offer this feature so I wanted to upgrade.. Boy was that a mistake! I had the Pixi for not but a week and I couldn&#8217;t take it. There was too much going on and the mostly touchscreen menu was not for me, I like to be able to scroll around with a left,right,up,down. So I opp for a BlackBerry that so many of my friends had raved about. I&#8217;m still trying to adjust. I do like the apps that are offered and the navigation and themes that I never had on my Treo. But yes, the messages are scattered in 4 different places! This makes no sense to me. I do also like having the BlackBerry Messenger. But one thing I can not get over is how awful the calendar is!! I miss my Treo so much. I like having the color coded events to easily look at a month view see what colored icons I had going on that week and quickly be reminded what I had going on. I am actually amazed Blackberry has nothing similar. In fact, I don&#8217;t know that any other device has a calendar that suits my needs like the PalmTreo. I struggle with this everyday, still waiting for someone to get on this. I love my blackberry, and am growingly getting attached to it, but I still consider giving it all up just to have my calendar back.<br />
I miss my Treo.<br />
Does anyone know of any solutions? Or calendar options? Or should I just go back to my Treo?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I Miss my Treo by John Wirtz</title>
		<link>http://www.adeptechllc.com/2010/03/12/i-miss-my-treo/comment-page-1/#comment-4639</link>
		<dc:creator>John Wirtz</dc:creator>
		<pubDate>Sat, 13 Mar 2010 14:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=281#comment-4639</guid>
		<description>The problem with smart phones is that once you start using one brand it becomes habit.  Like so many other things in life we get use to what we use regularly.  In my case, I started with a basic phone and seperate pda when I switched to the Blackberry.  So the BB was my first smart phone and I have become use to it.  Smart phone maker&#039;s biggest problem though was until Apple got into the game with integration and marketing, none of them pushed software beyond what was preinstalled on the device.  Now everyone is playing catch up with Apple even though there are plenty of sources already out there for other devices, except Android which didn&#039;t exist before.

I&#039;ve tried the iphone, sidekick and treo and haven&#039;t been impressed with any of them.  The Treo seemed old but capable and wasn&#039;t very satisfying.  The Sidekick seemed like someone took the much maligned but very capable WinMo OS and put it in a toy.  Finally, oy, the iphone, don&#039;t get me started.  As you mentioned the upgrade train you lock into with Apple just to get the functionality that should have been built in from the start and only to end up with a mediocre product.  The only thing Apple has done right is to create an integrated app store.  For me, the problem is that its integrated with itunes which I lothe.  Contrary to popular belief, I&#039;m not an Apple hater, I think they make some fairly good products.  They lock you into their draconian hardware and software rules.  If you deviate, they&#039;ll happily brick the hardware you paid for.  So you really don&#039;t own your Apple products.

At least with the BB, WinMo device, Android, and Treo devices you could buy third party software without voiding your warranty.  If you haven&#039;t found it yet, try Crackberry.com for software and recommendations.  They were there before RIM created App World.  I know, not much help with what you need.</description>
		<content:encoded><![CDATA[<p>The problem with smart phones is that once you start using one brand it becomes habit.  Like so many other things in life we get use to what we use regularly.  In my case, I started with a basic phone and seperate pda when I switched to the Blackberry.  So the BB was my first smart phone and I have become use to it.  Smart phone maker&#8217;s biggest problem though was until Apple got into the game with integration and marketing, none of them pushed software beyond what was preinstalled on the device.  Now everyone is playing catch up with Apple even though there are plenty of sources already out there for other devices, except Android which didn&#8217;t exist before.</p>
<p>I&#8217;ve tried the iphone, sidekick and treo and haven&#8217;t been impressed with any of them.  The Treo seemed old but capable and wasn&#8217;t very satisfying.  The Sidekick seemed like someone took the much maligned but very capable WinMo OS and put it in a toy.  Finally, oy, the iphone, don&#8217;t get me started.  As you mentioned the upgrade train you lock into with Apple just to get the functionality that should have been built in from the start and only to end up with a mediocre product.  The only thing Apple has done right is to create an integrated app store.  For me, the problem is that its integrated with itunes which I lothe.  Contrary to popular belief, I&#8217;m not an Apple hater, I think they make some fairly good products.  They lock you into their draconian hardware and software rules.  If you deviate, they&#8217;ll happily brick the hardware you paid for.  So you really don&#8217;t own your Apple products.</p>
<p>At least with the BB, WinMo device, Android, and Treo devices you could buy third party software without voiding your warranty.  If you haven&#8217;t found it yet, try Crackberry.com for software and recommendations.  They were there before RIM created App World.  I know, not much help with what you need.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I Miss my Treo by Johnny</title>
		<link>http://www.adeptechllc.com/2010/03/12/i-miss-my-treo/comment-page-1/#comment-4638</link>
		<dc:creator>Johnny</dc:creator>
		<pubDate>Fri, 12 Mar 2010 20:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=281#comment-4638</guid>
		<description>Unfortunately I have come to the sad conclusion that phones are no longer made for users, they are made for the people that review phones.  The wow factor is more important than the usability of the phone.  
I really think that there has been no better smart phone series that the Treo’s.  My biggest frustration is with Palm.  They did a lousy job marketing the phone to the public and showcasing all the apps that were available.  I am always anoid  at the fact that people seem to think that the IPhone is the only phone that can do what it does.  Palm has failed to learn the lesson that Apple learned the hard way, it’s the apps that sell the phone and the customer will want the largest selection of apps, even if they don’t come from palm.  I think Palm didn’t push these apps because they wouldn’t make any money from them directly.  But they may have held on to more market share.
When I dropped my phone for the 150th time and finally killed it, I switched from my palm 700p to a Blackberry Storm.  What a disaster.  The only good feature that the Blackberries had was the e-mail push technology which is now available everywhere.  What I really hated about the Blackberries is the way they lump all messages together.  I would look at my phone to see I had messages then it was like an Easter egg hunt to figure out what kind of message it was, (voice, text, etc.).  THEN, when you want to reply to a text message for example, the phone asks you if you want to send an; e-mail, Text message, MM message, or voice mail.  If you get an e-mail and want to reply the phone asks you if you want to send an; e-mail, Text message, MM message, or voice mail.  If you get a MM message and want to reply the phone asks you …well, you get the idea.  
Contact management was awful and the calendar was useless.  The touch screen, which requires you to use your fingers often selected the wrong  text on websites or in trying to edit a message. Couple that with the slow response from touch screen and you could go mad trying to send an e-mail.  Plus I had to use two hands to manipulate the phone, all that swiping made the phone more inconvenient to use.
I finally went on e-bay and purchased a 755p which was in mint condition.  I have since started to use p-tunes heavily to listen to internet radio and I have added a Bluetooth GPS. I expect to be buying another off of e-bay to that I can have another back up.  My only dwindling hope is that Palm will see the light and make a phone that will similar button layout as the Treo’s and can run the Palm OS emulation software that has come out.  The fact that there is Palm OS emulation software to begin with ought to be a big hint to palm.  I myself started on a Palm 5000, (remember those?) and have almost 20 years of contacts in my phone.  Switching that over will be no easy task so I will give up my Palm OS device when they pull it out of my cold dead fingers, or until I can’t get another one on e-bay.</description>
		<content:encoded><![CDATA[<p>Unfortunately I have come to the sad conclusion that phones are no longer made for users, they are made for the people that review phones.  The wow factor is more important than the usability of the phone.<br />
I really think that there has been no better smart phone series that the Treo’s.  My biggest frustration is with Palm.  They did a lousy job marketing the phone to the public and showcasing all the apps that were available.  I am always anoid  at the fact that people seem to think that the IPhone is the only phone that can do what it does.  Palm has failed to learn the lesson that Apple learned the hard way, it’s the apps that sell the phone and the customer will want the largest selection of apps, even if they don’t come from palm.  I think Palm didn’t push these apps because they wouldn’t make any money from them directly.  But they may have held on to more market share.<br />
When I dropped my phone for the 150th time and finally killed it, I switched from my palm 700p to a Blackberry Storm.  What a disaster.  The only good feature that the Blackberries had was the e-mail push technology which is now available everywhere.  What I really hated about the Blackberries is the way they lump all messages together.  I would look at my phone to see I had messages then it was like an Easter egg hunt to figure out what kind of message it was, (voice, text, etc.).  THEN, when you want to reply to a text message for example, the phone asks you if you want to send an; e-mail, Text message, MM message, or voice mail.  If you get an e-mail and want to reply the phone asks you if you want to send an; e-mail, Text message, MM message, or voice mail.  If you get a MM message and want to reply the phone asks you …well, you get the idea.<br />
Contact management was awful and the calendar was useless.  The touch screen, which requires you to use your fingers often selected the wrong  text on websites or in trying to edit a message. Couple that with the slow response from touch screen and you could go mad trying to send an e-mail.  Plus I had to use two hands to manipulate the phone, all that swiping made the phone more inconvenient to use.<br />
I finally went on e-bay and purchased a 755p which was in mint condition.  I have since started to use p-tunes heavily to listen to internet radio and I have added a Bluetooth GPS. I expect to be buying another off of e-bay to that I can have another back up.  My only dwindling hope is that Palm will see the light and make a phone that will similar button layout as the Treo’s and can run the Palm OS emulation software that has come out.  The fact that there is Palm OS emulation software to begin with ought to be a big hint to palm.  I myself started on a Palm 5000, (remember those?) and have almost 20 years of contacts in my phone.  Switching that over will be no easy task so I will give up my Palm OS device when they pull it out of my cold dead fingers, or until I can’t get another one on e-bay.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just Enough vs. Just In Case by Keith McMillan</title>
		<link>http://www.adeptechllc.com/2010/03/01/just-enough-vs-just-in-case/comment-page-1/#comment-4637</link>
		<dc:creator>Keith McMillan</dc:creator>
		<pubDate>Sat, 06 Mar 2010 22:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=273#comment-4637</guid>
		<description>Hello Lev,

I&#039;m afraid we&#039;re going to have to disagree on this. I used to be a proponent of modeling every use case/user story, and then keeping the model up to date, so we knew the design of every use case, which classes it involved, and what methods.  Over time, we had to let go of updating all those models after someone changed something, due to the pressure of delivering more to the customer, and a funny thing happened: it just didn&#039;t matter that the models weren&#039;t up to date: nobody used them.

Sure, it&#039;s a good idea to make sure that the features you want are represented as user stories, or use cases, to make sure you don&#039;t forget something important, but that can be done in a very lightweight way (keeping track of themes or epics, and then making sure there are stories for them, for instance), and that&#039;s not what I mean by complete traceability.  Traceability to me is being able to refer to a detailed model for the story (typically class and sequence diagrams), and knowing that the model is correct.  That means that someone kept it up to date, or rather that &lt;i&gt;everyone&lt;/i&gt; who worked on the system did.

The value of producing a model for a story or a use case is in thinking about how you&#039;re going to deal with the requirements, and that can be done at a whiteboard. If it&#039;s put into a formal modeling tool, in my experience it&#039;s seldom referred to afterward, sometimes because it&#039;s no longer correct (because nobody updated it), sometimes because it doesn&#039;t cover the right level of detail in order to be useful, and sometimes because it&#039;s just easier to read the code.

In my experience, which is considerable after over a decade working for large companies as a consultant, here&#039;s only one that got any real value from complete traceability, and they were filing FDA paperwork for medical devices, so it was a requirement for them.

I appreciate your comments, even if we disagree,

Keith</description>
		<content:encoded><![CDATA[<p>Hello Lev,</p>
<p>I&#8217;m afraid we&#8217;re going to have to disagree on this. I used to be a proponent of modeling every use case/user story, and then keeping the model up to date, so we knew the design of every use case, which classes it involved, and what methods.  Over time, we had to let go of updating all those models after someone changed something, due to the pressure of delivering more to the customer, and a funny thing happened: it just didn&#8217;t matter that the models weren&#8217;t up to date: nobody used them.</p>
<p>Sure, it&#8217;s a good idea to make sure that the features you want are represented as user stories, or use cases, to make sure you don&#8217;t forget something important, but that can be done in a very lightweight way (keeping track of themes or epics, and then making sure there are stories for them, for instance), and that&#8217;s not what I mean by complete traceability.  Traceability to me is being able to refer to a detailed model for the story (typically class and sequence diagrams), and knowing that the model is correct.  That means that someone kept it up to date, or rather that <i>everyone</i> who worked on the system did.</p>
<p>The value of producing a model for a story or a use case is in thinking about how you&#8217;re going to deal with the requirements, and that can be done at a whiteboard. If it&#8217;s put into a formal modeling tool, in my experience it&#8217;s seldom referred to afterward, sometimes because it&#8217;s no longer correct (because nobody updated it), sometimes because it doesn&#8217;t cover the right level of detail in order to be useful, and sometimes because it&#8217;s just easier to read the code.</p>
<p>In my experience, which is considerable after over a decade working for large companies as a consultant, here&#8217;s only one that got any real value from complete traceability, and they were filing FDA paperwork for medical devices, so it was a requirement for them.</p>
<p>I appreciate your comments, even if we disagree,</p>
<p>Keith</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just Enough vs. Just In Case by Lev Ayzner</title>
		<link>http://www.adeptechllc.com/2010/03/01/just-enough-vs-just-in-case/comment-page-1/#comment-4636</link>
		<dc:creator>Lev Ayzner</dc:creator>
		<pubDate>Sat, 06 Mar 2010 21:54:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=273#comment-4636</guid>
		<description>While I agree with &quot;just enough&quot; mentality in general, I may not agree with traceability is &quot;incredibly expensive and time consuming to produce, and to maintain&quot;.

Knowing what is the right thing to do is necessary but not sufficient. Necessary and sufficient is doing the right thing the right way... Then, it may provide &quot;good enough&quot; value. Hard to believe that no one has got any positive experience with traceability.

Thanks,
LevA</description>
		<content:encoded><![CDATA[<p>While I agree with &#8220;just enough&#8221; mentality in general, I may not agree with traceability is &#8220;incredibly expensive and time consuming to produce, and to maintain&#8221;.</p>
<p>Knowing what is the right thing to do is necessary but not sufficient. Necessary and sufficient is doing the right thing the right way&#8230; Then, it may provide &#8220;good enough&#8221; value. Hard to believe that no one has got any positive experience with traceability.</p>
<p>Thanks,<br />
LevA</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just Enough vs. Just In Case by Ryan</title>
		<link>http://www.adeptechllc.com/2010/03/01/just-enough-vs-just-in-case/comment-page-1/#comment-4635</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Thu, 04 Mar 2010 21:34:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=273#comment-4635</guid>
		<description>I agree with your post, Keith, but I think there is another complication here. Sometimes the &quot;just in case&quot; is hidden behind a well constructed facade backed by well thought out (but usually quite convoluted) theories and ideas. It requires digging and wading through the facade in order to realize that what is actually behind there is simply a &quot;just in case&quot; or sometimes a nice CYA. Unfortunately, tearing down the facade usually takes a lot of time and effort.</description>
		<content:encoded><![CDATA[<p>I agree with your post, Keith, but I think there is another complication here. Sometimes the &#8220;just in case&#8221; is hidden behind a well constructed facade backed by well thought out (but usually quite convoluted) theories and ideas. It requires digging and wading through the facade in order to realize that what is actually behind there is simply a &#8220;just in case&#8221; or sometimes a nice CYA. Unfortunately, tearing down the facade usually takes a lot of time and effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just Enough vs. Just In Case by Keith McMillan</title>
		<link>http://www.adeptechllc.com/2010/03/01/just-enough-vs-just-in-case/comment-page-1/#comment-4634</link>
		<dc:creator>Keith McMillan</dc:creator>
		<pubDate>Tue, 02 Mar 2010 15:15:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=273#comment-4634</guid>
		<description>Hello Rama,

&quot;Just enough&quot; is going to be different for every team, and for each activity you undertake, so it&#039;s not possible to give concrete guidance on how much is just enough.  

That&#039;s the reason I suggest that we ask &quot;why?&quot;  If we ask &quot;who needs this, and for what? Is this the best form for what they need?&quot; we stand a better chance of finding all that make-work we do &quot;just in case.&quot;  

We&#039;re always going to be asked to do more than is &quot;just enough&quot; but at least if we&#039;re asking the questions, we can try to keep our focus on providing just enough.

Thanks for your comments!
Keith</description>
		<content:encoded><![CDATA[<p>Hello Rama,</p>
<p>&#8220;Just enough&#8221; is going to be different for every team, and for each activity you undertake, so it&#8217;s not possible to give concrete guidance on how much is just enough.  </p>
<p>That&#8217;s the reason I suggest that we ask &#8220;why?&#8221;  If we ask &#8220;who needs this, and for what? Is this the best form for what they need?&#8221; we stand a better chance of finding all that make-work we do &#8220;just in case.&#8221;  </p>
<p>We&#8217;re always going to be asked to do more than is &#8220;just enough&#8221; but at least if we&#8217;re asking the questions, we can try to keep our focus on providing just enough.</p>
<p>Thanks for your comments!<br />
Keith</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just Enough vs. Just In Case by Rama</title>
		<link>http://www.adeptechllc.com/2010/03/01/just-enough-vs-just-in-case/comment-page-1/#comment-4633</link>
		<dc:creator>Rama</dc:creator>
		<pubDate>Tue, 02 Mar 2010 11:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=273#comment-4633</guid>
		<description>Hi Keith
It is no doubt a very interesting and informative discussion. We face these kinds of issues often.
It will be really good if we extend this further and try to explore on how we could help the team define &quot; Just what is enough&quot;. I believe that many a times although the team members are aware of the &quot;Just enough&quot;, but what prevents them from implementing the thought is the litmus test for determining what is &quot; Just Enough&quot;.
Thoughts welcome
Regards
Rama</description>
		<content:encoded><![CDATA[<p>Hi Keith<br />
It is no doubt a very interesting and informative discussion. We face these kinds of issues often.<br />
It will be really good if we extend this further and try to explore on how we could help the team define &#8221; Just what is enough&#8221;. I believe that many a times although the team members are aware of the &#8220;Just enough&#8221;, but what prevents them from implementing the thought is the litmus test for determining what is &#8221; Just Enough&#8221;.<br />
Thoughts welcome<br />
Regards<br />
Rama</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just Enough vs. Just In Case by Petri Heiramo</title>
		<link>http://www.adeptechllc.com/2010/03/01/just-enough-vs-just-in-case/comment-page-1/#comment-4632</link>
		<dc:creator>Petri Heiramo</dc:creator>
		<pubDate>Mon, 01 Mar 2010 20:31:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=273#comment-4632</guid>
		<description>Nice post, and to the point. Thanks for writing it.


Yours, Petri</description>
		<content:encoded><![CDATA[<p>Nice post, and to the point. Thanks for writing it.</p>
<p>Yours, Petri</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Just Enough vs. Just In Case by Casey</title>
		<link>http://www.adeptechllc.com/2010/03/01/just-enough-vs-just-in-case/comment-page-1/#comment-4631</link>
		<dc:creator>Casey</dc:creator>
		<pubDate>Mon, 01 Mar 2010 15:46:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=273#comment-4631</guid>
		<description>Keith, a thousand times YES! I currently work for the large IT department you were recently consulting for, and this article really gets down to one of the major root causes of project delays here. I&#039;m tempted to print up t-shirts and posters with the phrase &quot;The antidote to &#039;just in case&#039; is &#039;just enough&#039;&quot; on them. Thanks for your insight.</description>
		<content:encoded><![CDATA[<p>Keith, a thousand times YES! I currently work for the large IT department you were recently consulting for, and this article really gets down to one of the major root causes of project delays here. I&#8217;m tempted to print up t-shirts and posters with the phrase &#8220;The antidote to &#8216;just in case&#8217; is &#8216;just enough&#8217;&#8221; on them. Thanks for your insight.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
