<?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>waterfall Archives - IRM Training</title>
	<atom:link href="https://irm.com.au/tag/waterfall/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Australian Leading Training Provider since 1989</description>
	<lastBuildDate>Mon, 30 Apr 2018 05:53:28 +0000</lastBuildDate>
	<language>en-AU</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
<site xmlns="com-wordpress:feed-additions:1">214999885</site>	<item>
		<title>Most Popular Business Analysis Techniques</title>
		<link>https://irm.com.au/popular-ba-techniques/</link>
					<comments>https://irm.com.au/popular-ba-techniques/#comments</comments>
		
		<dc:creator><![CDATA[IRM Training]]></dc:creator>
		<pubDate>Fri, 17 Feb 2017 03:33:50 +0000</pubDate>
				<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[activity diagrams]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[BPMN]]></category>
		<category><![CDATA[business analysis techniques]]></category>
		<category><![CDATA[context diagrams]]></category>
		<category><![CDATA[data flow diagrams]]></category>
		<category><![CDATA[ERD]]></category>
		<category><![CDATA[interviewing]]></category>
		<category><![CDATA[object-oriented]]></category>
		<category><![CDATA[requirements workshop]]></category>
		<category><![CDATA[waterfall]]></category>
		<guid isPermaLink="false">https://irm.com.au/?p=553</guid>

					<description><![CDATA[<p>It can be difficult to keep up with the most popular business analysis techniques. Do you know which methodology analysts have the most experience using? How about diagramming techniques? We conducted a survey of over 1,100 business analysts (68% with over 5 years experience) which gave some interesting results as to what business analysis techniques [&#8230;]</p>
<p>The post <a href="https://irm.com.au/popular-ba-techniques/">Most Popular Business Analysis Techniques</a> appeared first on <a href="https://irm.com.au">IRM Training</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>It can be difficult to keep up with the most popular business analysis techniques. Do you know which methodology analysts have the most experience using? How about diagramming techniques?</p>
<p>We conducted a survey of over 1,100 business analysts (68% with over 5 years experience) which gave some interesting results as to what business analysis techniques are the most popular.</p>
<h2>Methodologies</h2>
<p>When it comes to software development methodologies, 68% said they had experience with <strong>waterfall development</strong>, 46% said iterative whilst <strong>object-oriented</strong> (44%) and <strong>agile</strong> (34%) also rated highly.</p>
<p>Assuming that many of these analysts would be working for large organisations &#8211; with mainframe systems &#8211; it’s not surprising to see <strong>waterfall</strong> so widely represented. We can also conclude that analysts need to work on a variety of different applications &#8211;<strong> iterative, OO</strong> and <strong>agile</strong> being very common on web services and client/server projects.</p>
<p>Interestingly, disciplines like <a href="https://en.wikipedia.org/wiki/ITIL"><strong>ITIL</strong></a> and <a href="https://en.wikipedia.org/wiki/Six_Sigma"><strong>Six Sigma</strong></a>, which have received lots of press recently, only rated 20% and 17% respectively.</p>
<p>&nbsp;</p>
<h2>Modelling</h2>
<p>Whilst the most regularly used diagramming technique was <strong>flowcharting</strong> (63%), when it comes to formal diagramming techniques, <strong>use case</strong> led the way (55%) followed by <strong>data flow diagrams</strong> (42%), <strong>activity diagrams</strong> (38%) and <strong>context diagrams</strong> (34%). <strong>Entity relationship diagrams</strong> were still widely used (30%) and “new kid on the block” <strong>BPMN</strong> came in at 13%.</p>
<p><img data-recalc-dims="1" fetchpriority="high" decoding="async" class="aligncenter wp-image-1018 size-medium" src="https://i0.wp.com/irm.com.au/wp-content/uploads/2016/03/drawing-for-visual-communication-270x300.jpg?resize=270%2C300&#038;ssl=1" alt="business analysis techniques" width="270" height="300" /></p>
<p>Note that <strong>Business Process Management (BPM)</strong> scored highly in the methodologies section (52%) but didn’t show a correspondingly high result for BPMN usage. Perhaps this indicated that <strong>BPM</strong> was interpreted as a generic term covering methodology, software products and general process improvement?</p>
<p>&nbsp;</p>
<h2>Elicitation</h2>
<p>For requirements gathering, 67% said<strong> interviewing</strong> was the most frequently used method. <strong>Requirements workshops</strong> came in at 45% and <strong>JAD sessions</strong> 34%.</p>
<p>The survey showed there were a bewildering range of tools, techniques and methodologies in widespread use. Probably too many for the poor analyst to master. As always, it comes down to the old saying &#8211; it’s not what you know it’s how you use it!</p>
<p>&nbsp;</p>
<p style="text-align: right;">Download our free <a href="https://irm.com.au/downloadable-requirements-solution-template/">Requirements Specification Template</a></p>
<hr />
<p style="text-align: right;"><em>If you liked this article, you may also enjoy:</em></p>
<p style="text-align: right;"><em><a href="https://irm.com.au/manage-client-expectations/">Facilitated Workshops &#8211; When and Why?</a></em></p>
<p style="text-align: right;"><em><a href="https://irm.com.au/requirements-big-data-projects/">There&#8217;s More to Modelling than Runways &amp; Catwalks</a></em></p>
<p style="text-align: right;"><em><a href="https://irm.com.au/creative-thinking-techniques/">Creative Thinking Techniques</a></em></p>
<hr />
<p>&nbsp;</p>
<p>The post <a href="https://irm.com.au/popular-ba-techniques/">Most Popular Business Analysis Techniques</a> appeared first on <a href="https://irm.com.au">IRM Training</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://irm.com.au/popular-ba-techniques/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">553</post-id>	</item>
		<item>
		<title>Separating Analysis from Design</title>
		<link>https://irm.com.au/separating-analysis-design/</link>
		
		<dc:creator><![CDATA[IRM Training]]></dc:creator>
		<pubDate>Mon, 12 Apr 2004 04:31:13 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[BA techniques]]></category>
		<category><![CDATA[business analysis]]></category>
		<category><![CDATA[business analysis tools]]></category>
		<category><![CDATA[SDLC]]></category>
		<category><![CDATA[waterfall]]></category>
		<guid isPermaLink="false">https://irm.com.au/?p=576</guid>

					<description><![CDATA[<p>Looking at what business objectives you are trying to satisfy before leaping into the technology enables you to use the technology wisely, manage scope and cut costs, producing systems which work for your clients. It’s easy to concentrate on the technical features of any project and lose sight of the reason for its existence. Every [&#8230;]</p>
<p>The post <a href="https://irm.com.au/separating-analysis-design/">Separating Analysis from Design</a> appeared first on <a href="https://irm.com.au">IRM Training</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>Looking at what business objectives you are trying to satisfy before leaping into the technology enables you to use the technology wisely, manage scope and cut costs, producing systems which work for your clients.</p>
<p>It’s easy to concentrate on the technical features of any project and lose sight of the reason for its existence. Every project exists to solve a problem. Either what you have doesn’t work well enough and needs improving, or you need to invent something totally new. After all, “If it ain’t broke, don’t fix it.”</p>
<p>Too often the pressures of deadlines and budgets lead us to bypass the important process of analysing business needs, and we leap straight into the technology. But how often do we find that the system doesn’t do exactly what’s required. Users are obliged to use workarounds, reducing some of the benefits we were supposed to provide which also affects our credibility. How often do we need to invest extra time and expense in providing Version 2 (and 3 and 4 and …), when some careful work might have exposed the real needs earlier?</p>
<p>&nbsp;</p>
<p>Read full paper: <a href="https://irm.com.au/wp-content/uploads/2016/04/Separating_Analysis_from_Design.pdf">Separating Analysis from Design</a></p>
<p>&nbsp;</p>
<hr />
<p style="text-align: right;"><em>If you liked this paper, you may also enjoy:</em></p>
<p style="text-align: right;"><em><a href="https://irm.com.au/clear-writing/">Is Business Analysis Low Tech?</a></em></p>
<p style="text-align: right;"><em><a href="https://irm.com.au/solution-mode-thinking-2/">Solution Mode Thinking</a></em></p>
<p style="text-align: right;"><em><a href="https://irm.com.au/stakeholder-communications-pictures-not-words/">Stakeholder Communications &#8211; Pictures not Words</a></em></p>
<hr />
<p>&nbsp;</p>
<p>The post <a href="https://irm.com.au/separating-analysis-design/">Separating Analysis from Design</a> appeared first on <a href="https://irm.com.au">IRM Training</a>.</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">576</post-id>	</item>
	</channel>
</rss>
