<?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: 10 Steps to Successful Marketing using Agile and Lean Practices</title>
	<atom:link href="http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/</link>
	<description>Adopt, Scale and Succeed with Agile Development</description>
	<lastBuildDate>Tue, 10 Jan 2012 03:30:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Jessica Kahn</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-7322</link>
		<dc:creator>Jessica Kahn</dc:creator>
		<pubDate>Tue, 05 Oct 2010 16:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-7322</guid>
		<description>Hi Marianne,

Thanks for your thoughtful response. You have some excellent points on the dislikes.  

Step 2. In the O (observation) step of our ORID process, we do bring in the numbers and facts to support the rest of the decision making process.  Great point on the importance of these KPIs.  We could do this better, and are in the process of upgrading our dashboard metrics, which will inform the process even more than it does today.

Step 4:  Yes, it definitely means customers. This was an oversight.  We conduct Validation Interviews to test messaging, drivers, calls to action and so forth with our customers. They are the most important stakeholder.

Step 6: True that we have it easier as a mostly co-located team.  We do have some team members including our EVP located remotely, and we use video conferencing on a daily basis to connect with those people.  Also, &lt;a href=&quot;http://agilezen.com/&quot; rel=&quot;nofollow&quot;&gt;AgileZen&lt;/a&gt; is very widely used in our team. I&#039;ll check out some of the other EMM solutions you reference.  Thanks again, and please continue to share your insights as we all learn together here.</description>
		<content:encoded><![CDATA[<p>Hi Marianne,</p>
<p>Thanks for your thoughtful response. You have some excellent points on the dislikes.  </p>
<p>Step 2. In the O (observation) step of our ORID process, we do bring in the numbers and facts to support the rest of the decision making process.  Great point on the importance of these KPIs.  We could do this better, and are in the process of upgrading our dashboard metrics, which will inform the process even more than it does today.</p>
<p>Step 4:  Yes, it definitely means customers. This was an oversight.  We conduct Validation Interviews to test messaging, drivers, calls to action and so forth with our customers. They are the most important stakeholder.</p>
<p>Step 6: True that we have it easier as a mostly co-located team.  We do have some team members including our EVP located remotely, and we use video conferencing on a daily basis to connect with those people.  Also, <a href="http://agilezen.com/" rel="nofollow">AgileZen</a> is very widely used in our team. I&#8217;ll check out some of the other EMM solutions you reference.  Thanks again, and please continue to share your insights as we all learn together here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jessica Kahn</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-7317</link>
		<dc:creator>Jessica Kahn</dc:creator>
		<pubDate>Tue, 05 Oct 2010 14:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-7317</guid>
		<description>Hi Josh,
We don&#039;t have a problem with individual accountability, most likely because nobody wants to let the team down and because everyone wants to look good to their peers. We have the opposite problem, which is that we often hold ourselves accountable to far more than we should with regard to work/life balance.  So we try to help each other get realistic on this front.  I have to refer to a great course that I took last week from &lt;a href=&quot;http://www.christopheravery.com/responsibility-process&quot; rel=&quot;nofollow&quot;&gt;Christopher Avery&lt;/a&gt;, called &quot;Knowledge Team Leadership&quot; which touches on the difference and balance  between responsibility vs. accountability among many other really exceptional lessons on team effectiveness.

In response to long term vision challenges, we try to remain very flexible and we do have to re-prioritize often. This can result in some inefficiencies, and we are always looking for ways to get more efficient here.  But generally, we favor frequent change over sticking with an old plan.  Our long term vision is a work in progress, as forces realign frequently.   Please share your ideas and your team&#039;s lessons with us, and we can all get smarter together here.</description>
		<content:encoded><![CDATA[<p>Hi Josh,<br />
We don&#8217;t have a problem with individual accountability, most likely because nobody wants to let the team down and because everyone wants to look good to their peers. We have the opposite problem, which is that we often hold ourselves accountable to far more than we should with regard to work/life balance.  So we try to help each other get realistic on this front.  I have to refer to a great course that I took last week from <a href="http://www.christopheravery.com/responsibility-process" rel="nofollow">Christopher Avery</a>, called &#8220;Knowledge Team Leadership&#8221; which touches on the difference and balance  between responsibility vs. accountability among many other really exceptional lessons on team effectiveness.</p>
<p>In response to long term vision challenges, we try to remain very flexible and we do have to re-prioritize often. This can result in some inefficiencies, and we are always looking for ways to get more efficient here.  But generally, we favor frequent change over sticking with an old plan.  Our long term vision is a work in progress, as forces realign frequently.   Please share your ideas and your team&#8217;s lessons with us, and we can all get smarter together here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: marianne seiler</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-7316</link>
		<dc:creator>marianne seiler</dc:creator>
		<pubDate>Tue, 05 Oct 2010 14:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-7316</guid>
		<description>This is a very interesting post.  The author hit on a number of key issues but also seems to have overlooked some critical points.

Likes:

Step 1: Acknowledged that marketing is different from software development.  Marketing lives in a very fluid environment.  In software development, programmers freeze the requirements and then build from those requirements.  There is no ‘freezing’ in marketing, the environment will continue to change and we must adapt to it.

Step 3: Marketing goals must align with business goals.  This seems like a given but I have seen marketing organizations have far different agendas than their sales counterparts.

Step 9:  Marketers must be ready and willing to respond to change – change is constant in marketing.  Sometimes practitioners of lean, agile or six-sigma become so enamored of the process it becomes more important than the output. Avoid this at all costs. 

Dislikes:

Step 2: Perhaps the author did not have the time to reference the facts used during the ORID process.  Marketing has to be about ROI or brand/market impact.  Any ORID process that does not utilize solid market data (response, ROI, cost per sale, etc.) is bound to arrive at the wrong answer.

Step 4:  Poll our stakeholders – I hope that also means customers.  Marketing needs to continually inform its decision making with the voice of the customer.

Step 6:  The physical task board works great when all the marketers are co-located but what do you do when people sit around the world.  Take a look at some of the EMM solutions (like Aprimo, Asset Link, Unica, etc.) that provide good electronic substitutes for a physical task board.

I believe whole heartedly that process disciplines like Lean, Agile, Six-Sigma have much to offer marketing.  However, these tool kits will need to be adapted – not just adopted – if they are to have significant impacts for marketers.</description>
		<content:encoded><![CDATA[<p>This is a very interesting post.  The author hit on a number of key issues but also seems to have overlooked some critical points.</p>
<p>Likes:</p>
<p>Step 1: Acknowledged that marketing is different from software development.  Marketing lives in a very fluid environment.  In software development, programmers freeze the requirements and then build from those requirements.  There is no ‘freezing’ in marketing, the environment will continue to change and we must adapt to it.</p>
<p>Step 3: Marketing goals must align with business goals.  This seems like a given but I have seen marketing organizations have far different agendas than their sales counterparts.</p>
<p>Step 9:  Marketers must be ready and willing to respond to change – change is constant in marketing.  Sometimes practitioners of lean, agile or six-sigma become so enamored of the process it becomes more important than the output. Avoid this at all costs. </p>
<p>Dislikes:</p>
<p>Step 2: Perhaps the author did not have the time to reference the facts used during the ORID process.  Marketing has to be about ROI or brand/market impact.  Any ORID process that does not utilize solid market data (response, ROI, cost per sale, etc.) is bound to arrive at the wrong answer.</p>
<p>Step 4:  Poll our stakeholders – I hope that also means customers.  Marketing needs to continually inform its decision making with the voice of the customer.</p>
<p>Step 6:  The physical task board works great when all the marketers are co-located but what do you do when people sit around the world.  Take a look at some of the EMM solutions (like Aprimo, Asset Link, Unica, etc.) that provide good electronic substitutes for a physical task board.</p>
<p>I believe whole heartedly that process disciplines like Lean, Agile, Six-Sigma have much to offer marketing.  However, these tool kits will need to be adapted – not just adopted – if they are to have significant impacts for marketers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mohsen</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-7171</link>
		<dc:creator>Mohsen</dc:creator>
		<pubDate>Thu, 30 Sep 2010 16:54:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-7171</guid>
		<description>Thanks so much for this empowering post on Agile marketing!</description>
		<content:encoded><![CDATA[<p>Thanks so much for this empowering post on Agile marketing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jessica Kahn</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-6637</link>
		<dc:creator>Jessica Kahn</dc:creator>
		<pubDate>Wed, 11 Aug 2010 22:02:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-6637</guid>
		<description>Jason and James,

Name the time and place and we&#039;ll make it happen. I bet we could learn a lot from how your team works as well. Thanks for posting!</description>
		<content:encoded><![CDATA[<p>Jason and James,</p>
<p>Name the time and place and we&#8217;ll make it happen. I bet we could learn a lot from how your team works as well. Thanks for posting!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-6636</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Wed, 11 Aug 2010 21:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-6636</guid>
		<description>Like the post, and there some great insights.  One question though.  Have you noticed any bad outcomes wrt to individual accountability and long term vision since each team member maintains their own backlog w/o a product ower?  If so have you designed any techniques to account for this?  I see that you mention the shared task board which help identifies bottlenecks/overcapacity, but has that been enough?</description>
		<content:encoded><![CDATA[<p>Like the post, and there some great insights.  One question though.  Have you noticed any bad outcomes wrt to individual accountability and long term vision since each team member maintains their own backlog w/o a product ower?  If so have you designed any techniques to account for this?  I see that you mention the shared task board which help identifies bottlenecks/overcapacity, but has that been enough?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curtis Simmons</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-6635</link>
		<dc:creator>Curtis Simmons</dc:creator>
		<pubDate>Wed, 11 Aug 2010 21:35:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-6635</guid>
		<description>Great post. We do something similar here but with a little less formality and few additions. 

First, we divide our work into various types of tasks and use color-coded cards to represent the task types. The primary types are Fixed projects (large, long-term, immovable projects, like conferences), Flexible projects (things we plan to do but can slip a few weeks if needed, like redesigning a brochure or completing a new whitepaper), Recurring projects (daily, weekly, monthly tasks, like social media updates or a customer newsletter), and Breaking News (unplanned items that inevitably arise from other teams but must be completed).

Our philosophy is that a marketing team is similar to a news organization. In the news analogy you have some weekly columns that must go out like clockwork and you have some larger editorial pieces you want to complete but can easily be bumped if a breaking news item like a fire happens. 

So we color code our cards so that we can visually see what tasks cannot be moved and which ones can if a breaking news item occurs. 

At the beginning of each week we plan out the next two weeks. On a daily basis we review / update the board during our stand-up meeting. Cards fall into one of four phases, Planning, In Progress, Peer Review and Published. 

As breaking news arises from internal teams or outside forces (press releases, product updates, maintenance windows, etc) then we place them into the backlog and then depending on the urgency we discuss them in the stand-up and determine the Story/Audience/Channels for the breaking news item. We then write-up task cards and insert them into our timeline, perhaps moving some of the Flexible project tasks cards back to the backlog for future consideration.</description>
		<content:encoded><![CDATA[<p>Great post. We do something similar here but with a little less formality and few additions. </p>
<p>First, we divide our work into various types of tasks and use color-coded cards to represent the task types. The primary types are Fixed projects (large, long-term, immovable projects, like conferences), Flexible projects (things we plan to do but can slip a few weeks if needed, like redesigning a brochure or completing a new whitepaper), Recurring projects (daily, weekly, monthly tasks, like social media updates or a customer newsletter), and Breaking News (unplanned items that inevitably arise from other teams but must be completed).</p>
<p>Our philosophy is that a marketing team is similar to a news organization. In the news analogy you have some weekly columns that must go out like clockwork and you have some larger editorial pieces you want to complete but can easily be bumped if a breaking news item like a fire happens. </p>
<p>So we color code our cards so that we can visually see what tasks cannot be moved and which ones can if a breaking news item occurs. </p>
<p>At the beginning of each week we plan out the next two weeks. On a daily basis we review / update the board during our stand-up meeting. Cards fall into one of four phases, Planning, In Progress, Peer Review and Published. </p>
<p>As breaking news arises from internal teams or outside forces (press releases, product updates, maintenance windows, etc) then we place them into the backlog and then depending on the urgency we discuss them in the stand-up and determine the Story/Audience/Channels for the breaking news item. We then write-up task cards and insert them into our timeline, perhaps moving some of the Flexible project tasks cards back to the backlog for future consideration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Cormier</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-6629</link>
		<dc:creator>Jason Cormier</dc:creator>
		<pubDate>Wed, 11 Aug 2010 14:27:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-6629</guid>
		<description>James and I would now like you, Dru and Anne to come to our offices and walk us through everything you know. How can we make that happen? :-)</description>
		<content:encoded><![CDATA[<p>James and I would now like you, Dru and Anne to come to our offices and walk us through everything you know. How can we make that happen? :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Clark</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-6626</link>
		<dc:creator>James Clark</dc:creator>
		<pubDate>Wed, 11 Aug 2010 04:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-6626</guid>
		<description>Okay Jessica, Anne and Dru - we want to visit and see this in action. This sounds like the answer to some of our own marketing initiative efforts. I&#039;m figuring from Dru&#039;s comment we&#039;re participating in this as your partner - we just don&#039;t know it. :)</description>
		<content:encoded><![CDATA[<p>Okay Jessica, Anne and Dru &#8211; we want to visit and see this in action. This sounds like the answer to some of our own marketing initiative efforts. I&#8217;m figuring from Dru&#8217;s comment we&#8217;re participating in this as your partner &#8211; we just don&#8217;t know it. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dru</title>
		<link>http://www.rallydev.com/agileblog/2010/07/10-steps-to-successful-marketing-using-agile-and-lean-practices/#comment-6506</link>
		<dc:creator>Dru</dc:creator>
		<pubDate>Thu, 29 Jul 2010 01:20:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=5199#comment-6506</guid>
		<description>Spot on!  On other aspect of agile marketing that has amazed me: As Agile marketing teams get into an iterative rhythm, we tend to see their often relied on external resources (think advertising firms, graphic designers, PPC vendors, media sales etc) fall into that same rhythm!  You then have a highly leveraged, very agile marketing resource model - Magic!  

Great post!</description>
		<content:encoded><![CDATA[<p>Spot on!  On other aspect of agile marketing that has amazed me: As Agile marketing teams get into an iterative rhythm, we tend to see their often relied on external resources (think advertising firms, graphic designers, PPC vendors, media sales etc) fall into that same rhythm!  You then have a highly leveraged, very agile marketing resource model &#8211; Magic!  </p>
<p>Great post!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

