<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Thomas Murphy &#187; Agile</title>
	<atom:link href="http://blogs.gartner.com/tom_murphy/category/agile/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/tom_murphy</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Tue, 31 Jan 2012 20:22:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Accurev enables GIT</title>
		<link>http://blogs.gartner.com/tom_murphy/2012/01/31/accurev-enables-git/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2012/01/31/accurev-enables-git/#comments</comments>
		<pubDate>Tue, 31 Jan 2012 20:22:00 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[ALM]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[SCCM]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2012/01/31/accurev-enables-git/</guid>
		<description><![CDATA[DVCS has become a popular trend in agile development with many open source projects making use of GIT and Mercurial and other vendors offering DVCS like function (see Hype Cycle for Application Development, 2011) but they are still a bit too on the edge for most enterprise use.&#160; Concerns about security, a still emerging toolset [...]]]></description>
			<content:encoded><![CDATA[<p>DVCS has become a popular trend in agile development with many open source projects making use of GIT and Mercurial and other vendors offering DVCS like function (see <a href="http://my.gartner.com/portal/server.pt?open=512&amp;objID=256&amp;mode=2&amp;PageID=2350940&amp;resId=1753116&amp;ref=QuickSearch&amp;sthkw=DVCS">Hype Cycle for Application Development, 2011</a>) but they are still a bit too on the edge for most enterprise use.&#160; Concerns about security, a still emerging toolset for understanding revision history and ties to other existing tools are among the concerns.&#160; <a href="http://www.accurev.com">Accurev</a> announced today support for using GIT as a backend for its SCM product.&#160; This will enable a much greater number of organizations to utilize the distributed development abilities of a DVCS while also having their enterprise SCCM governance needs met.&#160; This should also enable a broader number of users to tie GIT into their ALM systems.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2012/01/31/accurev-enables-git/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Taking Agile to Heart &#8211; at the Management Layer</title>
		<link>http://blogs.gartner.com/tom_murphy/2011/06/17/taking-agile-to-heart-at-the-management-layer/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2011/06/17/taking-agile-to-heart-at-the-management-layer/#comments</comments>
		<pubDate>Fri, 17 Jun 2011 05:51:12 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[ALM]]></category>
		<category><![CDATA[Agile]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2011/06/17/taking-agile-to-heart-at-the-management-layer/</guid>
		<description><![CDATA[I have been to lots of daily stand-up meetings in many different companies.&#160; It is great to see how different Scrum teams work and fit agile practices into their culture and to their needs.&#160; I saw a more unique instance this week on a visit to Rally Software.&#160; This wasn’t the traditional development team stand-up [...]]]></description>
			<content:encoded><![CDATA[<p>I have been to lots of daily stand-up meetings in many different companies.&#160; It is great to see how different Scrum teams work and fit agile practices into their culture and to their needs.&#160; I saw a more unique instance this week on a visit to <a href="http://www.rallydev.com/">Rally Software</a>.&#160; This wasn’t the traditional development team stand-up or even a product manager oriented scrum of scrums.&#160; No, this was the executive team daily stand-up.&#160; I thought it was great to see that outside of development the company taking the concept and putting it to use and the insight that this provides to the company about one of the core agile processes that the company espouses to its customers.&#160; Quick, simple, and efficient the meeting keeps the team on the same page and enables them to communicate with greater authenticity to customers and prospects.&#160; I think it is a great pattern for IT teams to socialize within their companies.&#160; For agile development to scale it has to work not just at the development layer but across the organization.&#160; Get them a Scrum spreadsheet and introduce the daily standup so they can experience the value directly.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2011/06/17/taking-agile-to-heart-at-the-management-layer/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>New Year 2011 AD Reading List</title>
		<link>http://blogs.gartner.com/tom_murphy/2011/01/07/new-year-2011-ad-reading-list/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2011/01/07/new-year-2011-ad-reading-list/#comments</comments>
		<pubDate>Fri, 07 Jan 2011 05:51:40 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Testing]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2011/01/07/new-year-2011-ad-reading-list/</guid>
		<description><![CDATA[A few relatively new books have been filling my reading time lately and they offer great content on how to improve the development process and team especially if you are making a shift towards Agile: Continuous Delivery – this is a great new book on what it really takes to make Continuous Integration work and [...]]]></description>
			<content:encoded><![CDATA[<p>A few relatively new books have been filling my reading time lately and they offer great content on how to improve the development process and team especially if you are making a shift towards Agile:</p>
<p><a href="http://continuousdelivery.com">Continuous Delivery</a> – this is a great new book on what it really takes to make Continuous Integration work and beyond.&#160; If you want to go faster, you have to automate and remove friction from the cycles and this book helps explain how.</p>
<p><a href="http://www.pragprog.com/titles/achbd/the-rspec-book">The RSpec Book</a> – Solid text that introduces the concepts of Behavior Driven Development using RSpec and Cucumber and drives a refocus of unit testing as a design method – a method designed to create well crafted code and to drive productive interaction between users, developers, and testers in a virtuous cycle of acceptance criteria and unit tests.</p>
<p><a href="http://www.agiletester.ca/">Agile Testing</a> – There are many Agile books out there but they are about developer practices, project management and sometimes requirements.&#160; Testers have been left hanging in the wind.&#160; This book helps define terminology, practices and the shifts a team will go through in the transition from waterfall to agile.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2011/01/07/new-year-2011-ad-reading-list/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Quick Scrum intro video</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/09/20/quick-scrum-intro-video/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/09/20/quick-scrum-intro-video/#comments</comments>
		<pubDate>Mon, 20 Sep 2010 05:21:00 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[ALM]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Axosoft]]></category>
		<category><![CDATA[scrum]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/09/20/quick-scrum-intro-video/</guid>
		<description><![CDATA[Axosoft has produced a nice 10 minute intro to scrum that describes the core processes without being a vendor tool pitch. http://www.axosoft.com/ontime/videos/scrum If you are trying to explain or understand the basics of the approach this is a great overview.]]></description>
			<content:encoded><![CDATA[<p>Axosoft has produced a nice 10 minute intro to scrum that describes the core processes without being a vendor tool pitch.  http://www.axosoft.com/ontime/videos/scrum<br />
If you are trying to explain or understand the basics of the approach this is a great overview.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/09/20/quick-scrum-intro-video/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Agile Gains Strong Presence and Delivers Returns</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/08/02/agile-gains-strong-presence-and-returns/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/08/02/agile-gains-strong-presence-and-returns/#comments</comments>
		<pubDate>Mon, 02 Aug 2010 21:20:07 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[MQ]]></category>
		<category><![CDATA[Quality]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/08/02/agile-gains-strong-presence-and-returns/</guid>
		<description><![CDATA[Agile project methods are continuing to become a standard with many organization (though “Agile” itself doesn’t denote a standard method) and the results are generally positive. As we work on the update to the Integrated Quality Suites MQ, data is matching what I see on client calls. Agile is still often loosely defined in many [...]]]></description>
			<content:encoded><![CDATA[<p>Agile project methods are continuing to become a standard with many organization (though “Agile” itself doesn’t denote a standard method) and the results are generally positive. As we work on the update to the Integrated Quality Suites MQ, data is matching what I see on client calls. </p>
<p><a href="http://blogs.gartner.com/tom_murphy/files/2010/08/image.gif"><img style="border-top-width: 0px;border-left-width: 0px;border-bottom-width: 0px;border-right-width: 0px" height="232" alt="image" src="http://blogs.gartner.com/tom_murphy/files/2010/08/image_thumb.gif" width="448" border="0" /></a></p>
<p>Agile is still often loosely defined in many companies with the core concept being an iterative approach to development that plans the project details in monthly (roughly) chunks.&#160; There are still wide variations as to which specific processes are being brought in beyond the planning process and reporting.&#160; This leads to mixed results and can increase stress and chaos among team members but generally is producing positive benefits.</p>
<p><a href="http://blogs.gartner.com/tom_murphy/files/2010/08/image1.gif"><img style="border-top-width: 0px;border-left-width: 0px;border-bottom-width: 0px;border-right-width: 0px" height="258" alt="image" src="http://blogs.gartner.com/tom_murphy/files/2010/08/image_thumb1.gif" width="499" border="0" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/08/02/agile-gains-strong-presence-and-returns/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Should I Embed Testers in the Dev Team?</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/06/08/should-i-embed-testers-in-the-dev-team/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/06/08/should-i-embed-testers-in-the-dev-team/#comments</comments>
		<pubDate>Tue, 08 Jun 2010 17:55:09 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Quality]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/06/08/should-i-embed-testers-in-the-dev-team/</guid>
		<description><![CDATA[At IBM’s Innovate conference a four person panel (Scott Ambler, Kim Warner, Reed Figgins, Brian Massey) addressed several issues with Agile and Testing.&#160; The starting question was the title line here.&#160; Agile generally thinks about small teams 5-15 people who work in close proximity (possibly the same room) with each other.&#160; Teams with the greatest [...]]]></description>
			<content:encoded><![CDATA[<p>At IBM’s Innovate conference a four person panel (Scott Ambler, Kim Warner, Reed Figgins, Brian Massey) addressed several issues with Agile and Testing.&#160; The starting question was the title line here.&#160; Agile generally thinks about small teams 5-15 people who work in close proximity (possibly the same room) with each other.&#160; Teams with the greatest success with Agile are co-located teams because they have the highest level of collaboration and this drives knowledge sharing and quality.&#160; Embedding testers in the agile team means that you are taking a proactive approach to quality and a recognition that quality is broader than just the code.&#160; However co-location will create the largest disruption, some of the test team may not fit well, and it can over time (if a team stays together) create blind-spots as the team begins to think more alike.&#160; While you should embed testers in agile teams, you should also have independent teams (potentially organized in COEs) that focus on automation, load/stress/performance, and to act as an independent IV&amp;V team.&#160; The bottom line is Agile can provide many benefits but it is a transformation and requires discipline and the right people and not everything will fit in the agile box.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/06/08/should-i-embed-testers-in-the-dev-team/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Metrics, The Trap We All Fall Into</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/06/08/metrics-the-trap-we-all-fall-into/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/06/08/metrics-the-trap-we-all-fall-into/#comments</comments>
		<pubDate>Tue, 08 Jun 2010 16:06:17 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Metrics]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/06/08/metrics-the-trap-we-all-fall-into/</guid>
		<description><![CDATA[A lot of the calls I take focus on metrics for the QA team.&#160; How many testers per developer, how many hours of testing, how many defects, etc.&#160; Unfortunately many of these metrics don&#8217;t end up yielding useful information often because they are too simple and they leave to many variables open.&#160; We like metrics [...]]]></description>
			<content:encoded><![CDATA[<p>A lot of the calls I take focus on metrics for the QA team.&#160; How many testers per developer, how many hours of testing, how many defects, etc.&#160; Unfortunately many of these metrics don&#8217;t end up yielding useful information often because they are too simple and they leave to many variables open.&#160; We like metrics because they can help us get a read on project directions and if we are falling in the averages or not but it is too easy to fall into the trap of easy metrics that mislead.&#160; I discussed this in earlier research on defect containment (see Toolkit: Defect Containment and Quantitative Defect Management, G00160257).&#160; Yesterday at IBM&#8217;s Innovate conference <a href="http://www.ivarjacobson.com/home.cfm">Ivar Jacobson</a> talked about the need to focus on metrics that were better not easy:    <br /><i></i></p>
<blockquote><p><i>People look at the wrong things:         <br />– Things that are easy to measure but meaningless          <br />– “Checking boxes” rather than results          <br />– Few, if any, qualitative measures          <br />And present them in the wrong way:          <br />– Confusing and contradictory data          <br />– Meaningful only to specialists &#8211; and maybe not even to them!          <br />– Unclear purpose          <br />– Point data and not trends          <br />– Hard to understand and use to make decisions          <br />To close the gap, how well you are doing needs to be measured in business terms</i></p>
</blockquote>
<p> <i>
<p></p>
<p>   </i>He suggested looking at metrics that help see if we are delivering better applications, delivering faster, systems that are easier to use, cheaper to run, and leading to happier users.&#160; These are not single dimension views but they focus on what matters.&#160; IBM is adding a number of capabilities for improved metrics to its Team Concert ALM product (as are other ALM vendors) and while these tools do provide increased reporting capabilities it will be important to not misuse the information and to recognize that seeing bad numbers doesn&#8217;t mean seeing &quot;bad people&quot;.&#160; This is the real core of the use of metrics is while they may be the proverbial warning flag they don&#8217;t tell you directly how to fix the problem.&#160; This doesn&#8217;t mean all dashboards are evil but they can&#8217;t replace Management by Walking Around and getting your hands dirty.
<p><img alt="" src="http://img.zemanta.com/pixy.gif?x-id=3cab1968-5afe-8edb-a01e-fd9197ccf136" /></p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/06/08/metrics-the-trap-we-all-fall-into/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Rally Expands Offering With Acquisition of AgileZen</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/04/14/rally-expands-offering-with-acquisition-of-agilezen/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/04/14/rally-expands-offering-with-acquisition-of-agilezen/#comments</comments>
		<pubDate>Wed, 14 Apr 2010 17:32:42 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[ALM]]></category>
		<category><![CDATA[Agile]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/04/14/rally-expands-offering-with-acquisition-of-agilezen/</guid>
		<description><![CDATA[Over the past few years we have seen a solid growth in the number of companies using Agile development methods.&#160; From the ALM viewpoint Agile is one of the drivers for companies to acquire new tools.&#160; Rally Software has played well in this market with their SaaS delivered solutions supporting Scrum.&#160; Generally this market has [...]]]></description>
			<content:encoded><![CDATA[<p>Over the past few years we have seen a solid growth in the number of companies using Agile development methods.&#160; From the ALM viewpoint Agile is one of the drivers for companies to acquire new tools.&#160; Rally Software has played well in this market with their SaaS delivered solutions supporting Scrum.&#160; </p>
<p>Generally this market has been driven by the need for: easy to get started and use, low capital expenditure, collaborative, connected as in connects to all my existing tools, and analytic.&#160; We have captured this in many research notes and by no means see anything of a letup but an acceleration in the market.&#160; This acceleration is driven by the need for better project transparency and the drive to improve productivity and better make use of globally dispersed teams (which may include internal and external resources).&#160; </p>
<p>Rally’s acquisition <a href="http://www.rallydev.com/agile_products/agilezen">of AgileZen</a> fits into this pattern by broadening the ways that projects can be managed and measured in a tool that fits well to the current Rally platform.&#160; We expect to see continued growth in the number of acquisitions and vendors broadening from Agile == Scrum to adapt support for a broader set of Agile techniques.&#160; </p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/04/14/rally-expands-offering-with-acquisition-of-agilezen/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Developers play a roll in quality but must be compensated for it</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/04/09/developers-play-a-roll-in-quality-but-must-be-compensated-for-it/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/04/09/developers-play-a-roll-in-quality-but-must-be-compensated-for-it/#comments</comments>
		<pubDate>Sat, 10 Apr 2010 02:44:19 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[Unit Testing]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/04/09/developers-play-a-roll-in-quality-but-must-be-compensated-for-it/</guid>
		<description><![CDATA[As organizations begin to absorb Agile development methods they will see that there are lots of great tasks for developers to perform generally all which result in better quality code sooner in the life-cycle.&#160; Practices such as mandatory unit tests or test driven development (TDD), code reviews, static analysis, etc. are all great but they [...]]]></description>
			<content:encoded><![CDATA[<p>As organizations begin to absorb Agile development methods they will see that there are lots of great tasks for developers to perform generally all which result in better quality code sooner in the life-cycle.&nbsp; Practices such as mandatory unit tests or test driven development (<a href="http://en.wikipedia.org/wiki/Test-driven_development">TDD</a>), code reviews, static analysis, etc. are all great but they will put a hit on traditional developer productivity as in SLOC produced.&nbsp; Organizations can&#8217;t expect that a developer will produce the same volume of code while producing all this extra work.&nbsp; It is true that there is a level of automation for the production of unit tests but it is still more work.&nbsp; This doesn&#8217;t mean that it is a bad idea or that developers will be less productive overall, there are many studies that have conflicting data to this point.&nbsp; What is known is that the quality of the work will improve, defects will be found sooner and this will reduce the cost of development and maintenance.&nbsp; However if you decide to levy this &#8220;tax&#8221; on developers, it must be matched with a change to the way developer productivity is measured.</p>
<div class="zemanta-pixie"><img class="zemanta-pixie-img" alt="" src="http://img.zemanta.com/pixy.gif?x-id=bd373417-4f6a-81f1-ac91-39fb67647592" /></div>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/04/09/developers-play-a-roll-in-quality-but-must-be-compensated-for-it/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>The &#8220;Agile&#8221; Methodology</title>
		<link>http://blogs.gartner.com/tom_murphy/2010/01/11/the-agile-methodology/</link>
		<comments>http://blogs.gartner.com/tom_murphy/2010/01/11/the-agile-methodology/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 17:22:05 +0000</pubDate>
		<dc:creator>Thomas Murphy</dc:creator>
				<category><![CDATA[Agile]]></category>

		<guid isPermaLink="false">http://blogs.gartner.com/tom_murphy/2010/01/11/the-agile-methodology/</guid>
		<description><![CDATA[Currently I see methodology discussions often start with “we are using the agile method.”&#160; This generally rubs me a bit the wrong way because I don’t think of Agile as a method or process but as a philosophy and a set of practices.&#160; It is also not 1 thing but a category.&#160; Or if we [...]]]></description>
			<content:encoded><![CDATA[<p>Currently I see methodology discussions often start with “we are using <em>the</em> agile method.”&#160; This generally rubs me a bit the wrong way because I don’t think of Agile as a method or process but as a philosophy and a set of practices.&#160; It is also not 1 thing but a category.&#160; Or if we say that Agile is a methodology there is not an agile method but many agile methods: Lean, XP, Scrum, etc.&#160; What normally occurs is that when a client says agile is their emerging method is Scrum is being used as a project management process and maybe some additional agile practices are in place.&#160; I expect this trend to continue but hope we can be more precise about terminology and recognize that agile isn’t just a method but a change to how we think about delivering software.&#160; This is the conversation to have with the business not just we are doing the same old thing with new names.&#160; For agile to ultimately succeed in a broad way at your organization you must have a productive relation with the business IT can’t be agile on its own.</p>
]]></content:encoded>
			<wfw:commentRss>http://blogs.gartner.com/tom_murphy/2010/01/11/the-agile-methodology/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

