<?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 on: Wrike Review</title>
	<atom:link href="http://blog.brodzinski.com/2007/09/wrike-review.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.brodzinski.com/2007/09/wrike-review.html</link>
	<description>Dealing with software projects in real life</description>
	<lastBuildDate>Fri, 10 Feb 2012 19:07:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Tony Mobily</title>
		<link>http://blog.brodzinski.com/2007/09/wrike-review.html#comment-42057</link>
		<dc:creator>Tony Mobily</dc:creator>
		<pubDate>Wed, 31 Aug 2011 15:15:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/wrike-review.html#comment-42057</guid>
		<description>Hi there,

I was wondering if you&#039;d consider giving Apollo a go too: http://www.apollohq.com

Apollo covers both project management and CRM. It has cases&amp;deals (or &quot;opportunities&quot;), calendars, timers, and several tools to help your team coordinate.

Let us know!

Merc.</description>
		<content:encoded><![CDATA[<p>Hi there,</p>
<p>I was wondering if you&#8217;d consider giving Apollo a go too: <a href="http://www.apollohq.com" rel="nofollow">http://www.apollohq.com</a></p>
<p>Apollo covers both project management and CRM. It has cases&amp;deals (or &#8220;opportunities&#8221;), calendars, timers, and several tools to help your team coordinate.</p>
<p>Let us know!</p>
<p>Merc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerome</title>
		<link>http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1918</link>
		<dc:creator>Jerome</dc:creator>
		<pubDate>Wed, 14 Oct 2009 17:49:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1918</guid>
		<description>Paul you may wish to consider PMP HQ http://www.pmphq.com - the combination of comprehensive project management suite with wide arsenal of collaboration tools such as wiki, file sharing etc</description>
		<content:encoded><![CDATA[<p>Paul you may wish to consider PMP HQ <a href="http://www.pmphq.com" rel="nofollow">http://www.pmphq.com</a> &#8211; the combination of comprehensive project management suite with wide arsenal of collaboration tools such as wiki, file sharing etc</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1917</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 23 Jun 2008 11:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1917</guid>
		<description>On Sep 11, 2007, Pawel wrote &quot;We follow our users’ feedback and their requests about tasks dependence feaure. We’re currently working on this feature. It’s a high priority for us, so expect it to be delivered to www.wrike.com within a couple of months. &quot;&lt;br/&gt;&lt;br/&gt;It doesn&#039;t look like this has been implemented and 9 months later. I take it it&#039;s not coming?</description>
		<content:encoded><![CDATA[<p>On Sep 11, 2007, Pawel wrote &#8220;We follow our users’ feedback and their requests about tasks dependence feaure. We’re currently working on this feature. It’s a high priority for us, so expect it to be delivered to <a href="http://www.wrike.com" rel="nofollow">http://www.wrike.com</a> within a couple of months. &#8220;</p>
<p>It doesn&#8217;t look like this has been implemented and 9 months later. I take it it&#8217;s not coming?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daria</title>
		<link>http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1916</link>
		<dc:creator>Daria</dc:creator>
		<pubDate>Tue, 09 Oct 2007 14:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1916</guid>
		<description>Pawel,&lt;br/&gt;I promised you to get back, so now &lt;br/&gt;I want to let you know that we released two significant features. One of them is the &lt;a HREF=&quot;http://www.wrike.com/blog/9/8/2007/Update_tasks_via_e_mail&quot; REL=&quot;nofollow&quot;&gt;intelligent reply function&lt;/a&gt;, which allows you to use the “reply to all” button to update your tasks. The other new feature is the &lt;a HREF=&quot;http://www.wrike.com/blog/8/18/2007/The_Dashboard_helps_you_meet_deadlines&quot; REL=&quot;nofollow&quot;&gt;dashboard&lt;/a&gt;, which helps you to quickly review your tasks and lets you begin your work at once. &lt;br/&gt;By the way, regarding e-mail invitations sent to the customers, we designed them the way they are to let your customers follow the progress of the task in Wrike with the team. This makes your project work transparent for the customers, and they really feel involved in the process.&lt;br/&gt;&lt;br/&gt;Thank you once again for your feedback.</description>
		<content:encoded><![CDATA[<p>Pawel,<br />I promised you to get back, so now <br />I want to let you know that we released two significant features. One of them is the <a HREF="http://www.wrike.com/blog/9/8/2007/Update_tasks_via_e_mail" REL="nofollow">intelligent reply function</a>, which allows you to use the “reply to all” button to update your tasks. The other new feature is the <a HREF="http://www.wrike.com/blog/8/18/2007/The_Dashboard_helps_you_meet_deadlines" REL="nofollow">dashboard</a>, which helps you to quickly review your tasks and lets you begin your work at once. <br />By the way, regarding e-mail invitations sent to the customers, we designed them the way they are to let your customers follow the progress of the task in Wrike with the team. This makes your project work transparent for the customers, and they really feel involved in the process.</p>
<p>Thank you once again for your feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1915</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Tue, 11 Sep 2007 20:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1915</guid>
		<description>Daria,&lt;br/&gt;&lt;br/&gt;First of all, thank you for exhaustive explanations. Several things I want to add:&lt;br/&gt;&lt;br/&gt;1. I&#039;ve checked FAQ and your tips from initial Wrike setup. Unfortunately it doesn&#039;t work exactly like it was explained. A couple of times I had an email with label in brackets in the subject field and the task wasn&#039;t added to the group. They was appended to the root.&lt;br/&gt;&lt;br/&gt;2. Your explanation of pricing plans makes the thing clear. You should add them on the website.&lt;br/&gt;&lt;br/&gt;3. With invitations I didn&#039;t mean limiting access to data - it is done well although I haven&#039;t mentioned that in the review. My point was that quite often on CC list you have people who aren&#039;t directly involved in project, task etc. They&#039;re there only to let them know about some things. It wouldn&#039;t be unusual to have customer on CC just to let them know you scheduled some task to one of your people.</description>
		<content:encoded><![CDATA[<p>Daria,</p>
<p>First of all, thank you for exhaustive explanations. Several things I want to add:</p>
<p>1. I&#8217;ve checked FAQ and your tips from initial Wrike setup. Unfortunately it doesn&#8217;t work exactly like it was explained. A couple of times I had an email with label in brackets in the subject field and the task wasn&#8217;t added to the group. They was appended to the root.</p>
<p>2. Your explanation of pricing plans makes the thing clear. You should add them on the website.</p>
<p>3. With invitations I didn&#8217;t mean limiting access to data &#8211; it is done well although I haven&#8217;t mentioned that in the review. My point was that quite often on CC list you have people who aren&#8217;t directly involved in project, task etc. They&#8217;re there only to let them know about some things. It wouldn&#8217;t be unusual to have customer on CC just to let them know you scheduled some task to one of your people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daria</title>
		<link>http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1914</link>
		<dc:creator>Daria</dc:creator>
		<pubDate>Tue, 11 Sep 2007 19:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1914</guid>
		<description>Pawel, &lt;br/&gt;&lt;br/&gt;Thank you for your review of &lt;a HREF=&quot;http://www.wrike.com&quot; REL=&quot;nofollow&quot;&gt;Wrike&lt;/a&gt;. We appreciate your positive evaluation of Wrike’s email-based project management concept. As you noted, we worked out a system of email notifications that helps you follow every detail of the project progress. We’re also pleased that you found Wrike a simple tool to use for projects, as we’re doing everything possible to make our subscribers’ work easy and comfortable. Thanks for pointing out the fact that the interface is clean and intuitive. &lt;br/&gt;&lt;br/&gt;It’s a pity you didn’t check FAQ page of Wrike’s site, as there you would be able to find the exact rules how to label emailed tasks in the subject field. Actually you just need to put the group title in square brackets e.g. [group title], write the task title and put the due date in square brackets, like this [yyyy-dd-mm]. The email body will be copied in the task description. You will find more information &lt;a HREF=&quot;http://www.wrike.com/faq.html#q3&quot; REL=&quot;nofollow&quot;&gt;here&lt;/a&gt; and &lt;a HREF=&quot;http://www.wrike.com/faq.html#q4&quot; REL=&quot;nofollow&quot;&gt;here&lt;/a&gt; &lt;br/&gt;&lt;br/&gt;As for updating tasks by using the “reply to all” button, that feature is coming next week, so we’ll be glad if you continue using your Wrike account to take advantage of intelligent reply processing for e-mails. We follow our users’ feedback and their requests about tasks dependence feaure. We’re currently working on this feature. It’s a high priority for us, so expect it to be delivered to &lt;a HREF=&quot;http://www.wrike.com&quot; REL=&quot;nofollow&quot;&gt;www.wrike.com&lt;/a&gt; within a couple of months. There are some architectural challenges that we want to solve elegantly. Our system has an open sharing model with possible many-to-many relations. This makes it easy to use on the user interface side, but at the same time makes technical implementation of features like dependency a tricky part. &lt;br/&gt;&lt;br/&gt;We would like to point out that Wrike helps you to realize a small team collaboration model with no need to pay for extra accounts. That is why we have free individual and power user plans. People can collaborate effectively with their team, almost at almost no cost. They create one paid account and a couple of free accounts. So the team leader/manager can share and assign an unlimited number of tasks with his team members. &lt;br/&gt;&lt;br/&gt;The beauty of Wrike is in its simplicity. Invitations to the system help to make the process easier without additional steps. So you don&#039;t have to go to a particular page every time to add new people. Our intention is to make users’ experiences with Wrike easier and more pleasant, so if you send an e-mail to John Smith and add wrike@wrike.com to recipients, John does not get access to the full project. He only gets an access to that particular e-mail and that particular task. There’s no need for you to send any embarrassing e-mails. People will not get access to your crucial information. They only have access to what you explicitly grant them the access to. We are not sure whether you already knew about this system behavior, so we wanted to explicitly outline this. Anyway, we plan to make our invitational e-mail much lighter, just like the one you get from LinkedIn nowadays. We are also working on a feature that will let people mark tasks complete with one click from their e-mail. That will help the most conservative stakeholders to stay away from the new tool and still be able manage projects. &lt;br/&gt;&lt;br/&gt;We know that there is always room for improvement. That is why we are working hard to enhance our software and make our users’ lives easier. Thank you for recognizing Wrike’s development growth potential.</description>
		<content:encoded><![CDATA[<p>Pawel, </p>
<p>Thank you for your review of <a HREF="http://www.wrike.com" REL="nofollow">Wrike</a>. We appreciate your positive evaluation of Wrike’s email-based project management concept. As you noted, we worked out a system of email notifications that helps you follow every detail of the project progress. We’re also pleased that you found Wrike a simple tool to use for projects, as we’re doing everything possible to make our subscribers’ work easy and comfortable. Thanks for pointing out the fact that the interface is clean and intuitive. </p>
<p>It’s a pity you didn’t check FAQ page of Wrike’s site, as there you would be able to find the exact rules how to label emailed tasks in the subject field. Actually you just need to put the group title in square brackets e.g. [group title], write the task title and put the due date in square brackets, like this [yyyy-dd-mm]. The email body will be copied in the task description. You will find more information <a HREF="http://www.wrike.com/faq.html#q3" REL="nofollow">here</a> and <a HREF="http://www.wrike.com/faq.html#q4" REL="nofollow">here</a> </p>
<p>As for updating tasks by using the “reply to all” button, that feature is coming next week, so we’ll be glad if you continue using your Wrike account to take advantage of intelligent reply processing for e-mails. We follow our users’ feedback and their requests about tasks dependence feaure. We’re currently working on this feature. It’s a high priority for us, so expect it to be delivered to <a HREF="http://www.wrike.com" REL="nofollow">http://www.wrike.com</a> within a couple of months. There are some architectural challenges that we want to solve elegantly. Our system has an open sharing model with possible many-to-many relations. This makes it easy to use on the user interface side, but at the same time makes technical implementation of features like dependency a tricky part. </p>
<p>We would like to point out that Wrike helps you to realize a small team collaboration model with no need to pay for extra accounts. That is why we have free individual and power user plans. People can collaborate effectively with their team, almost at almost no cost. They create one paid account and a couple of free accounts. So the team leader/manager can share and assign an unlimited number of tasks with his team members. </p>
<p>The beauty of Wrike is in its simplicity. Invitations to the system help to make the process easier without additional steps. So you don&#8217;t have to go to a particular page every time to add new people. Our intention is to make users’ experiences with Wrike easier and more pleasant, so if you send an e-mail to John Smith and add <a href="mailto:wrike@wrike.com">wrike@wrike.com</a> to recipients, John does not get access to the full project. He only gets an access to that particular e-mail and that particular task. There’s no need for you to send any embarrassing e-mails. People will not get access to your crucial information. They only have access to what you explicitly grant them the access to. We are not sure whether you already knew about this system behavior, so we wanted to explicitly outline this. Anyway, we plan to make our invitational e-mail much lighter, just like the one you get from LinkedIn nowadays. We are also working on a feature that will let people mark tasks complete with one click from their e-mail. That will help the most conservative stakeholders to stay away from the new tool and still be able manage projects. </p>
<p>We know that there is always room for improvement. That is why we are working hard to enhance our software and make our users’ lives easier. Thank you for recognizing Wrike’s development growth potential.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1913</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Sun, 09 Sep 2007 19:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1913</guid>
		<description>No, but I&#039;ll put it on the list.</description>
		<content:encoded><![CDATA[<p>No, but I&#8217;ll put it on the list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1912</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 09 Sep 2007 15:53:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2007/09/wrike-review.html#comment-1912</guid>
		<description>Have you looked at Vertabase project management softare yet?  http://www.vertabase.com.&lt;br/&gt;&lt;br/&gt;There&#039;s a free trial on the site.</description>
		<content:encoded><![CDATA[<p>Have you looked at Vertabase project management softare yet?  <a href="http://www.vertabase.com." rel="nofollow">http://www.vertabase.com.</a></p>
<p>There&#8217;s a free trial on the site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

