<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Practical Analyst - Latest Comments</title><link>http://practicalanalyst.disqus.com/</link><description>Practical insight for business analysts and solution delivery professionals</description><atom:link href="https://practicalanalyst.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 23 May 2013 09:51:40 -0000</lastBuildDate><item><title>Re: Business Analyst Career Talk on Jobshadow.com</title><link>http://practicalanalyst.com/business-analyst-career-talk-on-jobshadow-com/#comment-905830070</link><description>&lt;p&gt;Can someone please help me on how to get experiences in&lt;br&gt;Business Analyst, I really want to enter BA role, maybe as junior or whatever, I&lt;br&gt;have good customer skills as well as writing, listening, communication and&lt;br&gt;facilitating skills, I do not mind doing volunteer work, just want to gain experiences&lt;br&gt;and start from somewhere really. Any tips or ideal are much appreciated. Email address&lt;br&gt;“woleosho1@gmail.com”&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tony</dc:creator><pubDate>Thu, 23 May 2013 09:51:40 -0000</pubDate></item><item><title>Re: Business Analysts: A Resume is a Work Sample</title><link>http://practicalanalyst.com/business-analysts-a-resume-is-a-work-sample/#comment-809198342</link><description>&lt;p&gt;While I truly appreciate your view of the resume, the fact is that the resume will probably never make it past the screener program if it does not have enough of the "buzz words" and you will not see it.  It is a shame but job seekers can spend four hours tailoring their resume to the job posting only to be reject by the screener in Taleo or another application as it mysteriously processes 500+ applicants down to a group of 10.  it is almost like developing a scientific algorithm for choosing a winning lottery ticket.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ngneer</dc:creator><pubDate>Fri, 22 Feb 2013 23:58:46 -0000</pubDate></item><item><title>Re: Business Analyst Job Description</title><link>http://practicalanalyst.com/business-analyst-job-description/#comment-717641879</link><description>&lt;p&gt;cool story bro&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">guy</dc:creator><pubDate>Fri, 23 Nov 2012 12:28:10 -0000</pubDate></item><item><title>Re: Use Cases or User Stories? Read Up!</title><link>http://practicalanalyst.com/use-cases-or-user-stories-read-up/#comment-707628822</link><description>&lt;p&gt;can you help me ....how to represent a story to a use case&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">hfh hawatmeh</dc:creator><pubDate>Sun, 11 Nov 2012 10:57:52 -0000</pubDate></item><item><title>Re: Business Analysts, Be Kind to your Stakeholders!</title><link>http://practicalanalyst.com/business-analysts-be-kind-to-your-stakeholders/#comment-687838118</link><description>&lt;p&gt;Jonathan, I wholeheartedly agree.&lt;/p&gt;&lt;p&gt;One question though:&lt;/p&gt;&lt;p&gt;At my current assignment, the BA captures business and functional requirements, and SA defines the software requirements (SRS). Should the business be responsible for reviewing/approving the SRS as well?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Duane Banks</dc:creator><pubDate>Sat, 20 Oct 2012 10:56:41 -0000</pubDate></item><item><title>Re: We&amp;#8217;re Business People First</title><link>http://practicalanalyst.com/were-business-people-first/#comment-687830193</link><description>&lt;p&gt;&lt;br&gt;The way I see it, the role of a BA is essentially a matter of understanding and facilitating resolutions to problems. So, perhaps business analysis is neither a business nor an IT role, but a problem-solving role.&lt;/p&gt;&lt;p&gt;How so?  Well, not all resolutions to business problems involve technology; and not all resolutions require acumen of the particular business (in my opinion). The common denominator for all resolutions is problem-solving.&lt;/p&gt;&lt;p&gt;I believe Business Analysts ought to serve as partners to both the business and the solutions team.&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Duane Banks</dc:creator><pubDate>Sat, 20 Oct 2012 10:41:06 -0000</pubDate></item><item><title>Re: Business Analyst Job Description</title><link>http://practicalanalyst.com/business-analyst-job-description/#comment-676219041</link><description>&lt;p&gt;yo JB you talk like a fugen Fagit&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">FU JB</dc:creator><pubDate>Mon, 08 Oct 2012 10:23:11 -0000</pubDate></item><item><title>Re: The Value of Small Wins (or, How to Eat an Elephant)</title><link>http://practicalanalyst.com/the-value-of-small-wins-or-how-to-eat-an-elephant/#comment-671647463</link><description>&lt;p&gt;Another great post Jonathan! Its something about the small effort that makes your feel good when you complete it successfully. You might have heard of "Well begun is half done".. I have a twist to this in the context of this post "Consistent small beginnings have great endings" :)&lt;/p&gt;&lt;p&gt;I am a big fan of the "Fifth Discipline"... it was the first book I was told to read right after the college and its a new book each time you read it. :)&lt;br&gt;I liked the socio-psychological reasons for why the small wins work. It is in my view the basis for how everyone gets huge projects done. From an analyst's perspective it makes a lot sense to be able to relate to smaller, simpler components that build up to form a larger context or problem.&lt;/p&gt;&lt;p&gt;Congratulations again on your promotion and I wish you luck with eating the next elephant! :)&lt;/p&gt;&lt;p&gt;Cheers!&lt;br&gt;Yamo &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaaqub Mohamed(Yamo)</dc:creator><pubDate>Thu, 04 Oct 2012 21:08:40 -0000</pubDate></item><item><title>Re: Business Analyst Career Talk on Jobshadow.com</title><link>http://practicalanalyst.com/business-analyst-career-talk-on-jobshadow-com/#comment-666480576</link><description>&lt;p&gt;hello Sir,&lt;br&gt;i will be joining in a business analysis firm in 2013. i m a fresher with a Bachelor degree in engineering. i m very excited about it but a little bit confuse too because of lack of knowledge of this field. Can you provide me with some basic fundamentals one need to know about it.If possible  also refer some good books on this .&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">saket kumar</dc:creator><pubDate>Sat, 29 Sep 2012 16:00:03 -0000</pubDate></item><item><title>Re: Open Source Data Modeling Tools &amp;#8211; Worth a Look!</title><link>http://practicalanalyst.com/open-source-data-modelling-tool-worth-a-look/#comment-656940114</link><description>&lt;p&gt;Thanks, Michael. Should be fixed now.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jbabcock</dc:creator><pubDate>Thu, 20 Sep 2012 15:24:11 -0000</pubDate></item><item><title>Re: Business Analyst Job Description</title><link>http://practicalanalyst.com/business-analyst-job-description/#comment-648911000</link><description>&lt;p&gt;Thank you JB, I always find answers to my questions in practical analyst .. :) &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wael Said</dc:creator><pubDate>Thu, 13 Sep 2012 06:49:50 -0000</pubDate></item><item><title>Re: Open Source Data Modeling Tools &amp;#8211; Worth a Look!</title><link>http://practicalanalyst.com/open-source-data-modelling-tool-worth-a-look/#comment-643666863</link><description>&lt;p&gt;The link to Dia is blank&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Michael Phoenix</dc:creator><pubDate>Fri, 07 Sep 2012 17:42:36 -0000</pubDate></item><item><title>Re: Open Source Data Modeling Tools &amp;#8211; Worth a Look!</title><link>http://practicalanalyst.com/open-source-data-modelling-tool-worth-a-look/#comment-626868238</link><description>&lt;p&gt;good post&lt;br&gt;Muchas gracias&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">guest</dc:creator><pubDate>Thu, 23 Aug 2012 13:28:51 -0000</pubDate></item><item><title>Re: Free Desktop Tools a Business Analyst Should Know About</title><link>http://practicalanalyst.com/free-desktop-tools-a-business-analyst-should-know-about-2/#comment-625634062</link><description>&lt;p&gt;how do i become a business anlyst... currently i am working software developer...i just dont know how to get going....could you help &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Addie</dc:creator><pubDate>Wed, 22 Aug 2012 08:39:58 -0000</pubDate></item><item><title>Re: Business Analysts: A Resume is a Work Sample</title><link>http://practicalanalyst.com/business-analysts-a-resume-is-a-work-sample/#comment-613283070</link><description>&lt;p&gt;good article overall....&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Pramod</dc:creator><pubDate>Wed, 08 Aug 2012 06:16:28 -0000</pubDate></item><item><title>Re: We&amp;#8217;re Business People First</title><link>http://practicalanalyst.com/were-business-people-first/#comment-611616534</link><description>&lt;p&gt;Thanks for the comment and the reference, Gretchen. I was not familiar with that book. I'll be sure to check it out!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Babcock</dc:creator><pubDate>Mon, 06 Aug 2012 22:13:13 -0000</pubDate></item><item><title>Re: We&amp;#8217;re Business People First</title><link>http://practicalanalyst.com/were-business-people-first/#comment-603477914</link><description>&lt;p&gt;I just started reading Love Works by Joel Manby.  Joel provides an approach and real life examples of how to implement a "people first" culture in any business environment.  I highly recommend this book. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gretchen Hansen</dc:creator><pubDate>Mon, 30 Jul 2012 17:25:13 -0000</pubDate></item><item><title>Re: Business Analysis Can Kill a Project (In a Good Way)</title><link>http://practicalanalyst.com/business-analysis-can-kill-a-project-in-a-good-way/#comment-596517468</link><description>&lt;p&gt;Thanks for the comment and additional insight, David! You're right -  it's not necessarily about requirements being met 100%, but about heading off ill-fated projects and requests that will not provide the business value needed to justify completion.&lt;/p&gt;&lt;p&gt;After another read, I also think I might have chosen better wording when asking if readers have ever "killed a project", in that it is never something single-handedly done by the analyst.&lt;/p&gt;&lt;p&gt;The analyst's tasks is to provide the facts, data and recommendations needed to put business stakeholders in a position to make informed, decisions, which may include abandoning the iffy project request.&lt;/p&gt;&lt;p&gt;Again, thanks! &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Babcock</dc:creator><pubDate>Tue, 24 Jul 2012 12:54:35 -0000</pubDate></item><item><title>Re: Business Analysis Can Kill a Project (In a Good Way)</title><link>http://practicalanalyst.com/business-analysis-can-kill-a-project-in-a-good-way/#comment-596265195</link><description>&lt;p&gt;The issue is not whether the BA should recommend pulling the plug if user requirements are not 100% met, it's more that the BA has a responsibility to the project's business owner and sponsor, that if the benefits promised in the business case will not be realised, the the business case should be re-evaluated on that basis, then it's the sponsor / executive decision to terminate, put on hold, or continue with a new case as appropriate &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David J C Morris</dc:creator><pubDate>Tue, 24 Jul 2012 06:56:46 -0000</pubDate></item><item><title>Re: Visual Modeling: A Critical Skill for Business Analysts</title><link>http://practicalanalyst.com/visual-modeling-a-critical-skill-for-business-analysts/#comment-589836593</link><description>&lt;p&gt;Thanks for the comment, Jeremy. I agree with you on sticking primarily with the "tried and true", I do like to leave the door open for innovation, though, and am typically fine with whatever models or hybrids a team agrees best suits the need.&lt;/p&gt;&lt;p&gt;We've seen benefit in some cases by actually specifying requirements primarily in visuals with supporting text instead of the opposite as was previous habit.&lt;/p&gt;&lt;p&gt;It's all about providing the information in the format that's easiest to understand and discuss, and with context that makes it meaningful to the user/reviewer.&lt;/p&gt;&lt;p&gt;BTW - I am a longtime fan of the Seilevel site and message boards, and really looking forward to Joy Beatty and Anthony Chen's upcoming book on visual modeling!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Babcock</dc:creator><pubDate>Mon, 16 Jul 2012 22:54:36 -0000</pubDate></item><item><title>Re: We&amp;#8217;re Business People First</title><link>http://practicalanalyst.com/were-business-people-first/#comment-589832441</link><description>&lt;p&gt;Thanks, Yamo! I appreciate the comment.&lt;/p&gt;&lt;p&gt;Even when a BA typically works on IT/software projects, it's important to look at outcomes in terms of business value instead of just, "did we give the customer what they asked for?" That's the easy way out. A good BA doesn't just rely on the business stakeholder to know the business (you know, because we're "IT"), but helps stakeholders through the process of discovery and analysis - providing insight and business expertise -  to ensure the best business outcomes.&lt;/p&gt;&lt;p&gt;One of the complications that comes with the BA with the IT blinders on is that every solution is approached in terms of what we must do with our software and systems instead of also considering people and process as well. This can result in over-engineered systems and sub-optimal solutions across the board. Anyway....&lt;/p&gt;&lt;p&gt;BTW - love the turn of phrase - "For a business analyst the first order of business is business."&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Babcock</dc:creator><pubDate>Mon, 16 Jul 2012 22:47:35 -0000</pubDate></item><item><title>Re: We&amp;#8217;re Business People First</title><link>http://practicalanalyst.com/were-business-people-first/#comment-589638025</link><description>&lt;p&gt;Great article, Jonathan. I completely agree with your point-of-view; we really need to dispel the myth about a BA being closely associated (or only associated) with IT projects. There is no better time to do this now, while the role of a BA getting more recognized and clarified. For a business analyst the first order of business is business. :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yaaqub Mohamed(Yamo)</dc:creator><pubDate>Mon, 16 Jul 2012 17:51:11 -0000</pubDate></item><item><title>Re: Visual Modeling: A Critical Skill for Business Analysts</title><link>http://practicalanalyst.com/visual-modeling-a-critical-skill-for-business-analysts/#comment-587055244</link><description>&lt;p&gt;I could not agree more.  In fact, I would go further and say that visual models are not optional, but required for every project.  There is no way that the full picture can be seen without visual help.  Typically on an IT project, multiple visual models are needed because any single model will only show things from a limited perspective.&lt;/p&gt;&lt;p&gt;I would even be more rigorous about "what does a visual model look like".  Rather than have the BA start from scratch and find their own format, there have been years (even decades) of work on models like Process Flows, ensuring that the model is complete and consistent.  Whenever I set out to do a new Process Flow, Business Data Diagram, Ecosystem Map, or Data Flow Diagram, I grab the latest template because I know that practitioners have included all their lessons learned in these models as they were developed.&lt;/p&gt;&lt;p&gt;Great article, I encourage you to continue preaching this message to whoever will listen!&lt;/p&gt;&lt;p&gt;Jeremy Gorr&lt;br&gt;Senior Product Manger&lt;br&gt;Seilevel&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeremy Gorr</dc:creator><pubDate>Fri, 13 Jul 2012 12:08:23 -0000</pubDate></item><item><title>Re: Tools: Risk Matrix</title><link>http://practicalanalyst.com/tools-risk-matrix/#comment-584414828</link><description>&lt;p&gt;Thanks, Dougie! By all means, borrow away!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Babcock</dc:creator><pubDate>Wed, 11 Jul 2012 14:24:34 -0000</pubDate></item><item><title>Re: Thought, Problems, and Business Analysts</title><link>http://practicalanalyst.com/thought-problems-and-business-analysts/#comment-579096328</link><description>&lt;p&gt;Great post and great questions are below too. Don't missed them.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ales</dc:creator><pubDate>Fri, 06 Jul 2012 19:33:19 -0000</pubDate></item></channel></rss>