Friday, March 19, 2010

   Quick Links:   Articles     MA Blog     Community Blog     Templates     Books     BA Humor     Events     Jobs     Interview Questions         RSS Feeds

Business Analyst Articles: Business Analysis & Systems Analysis

Resources



Articles and White Papers
Minimize


Current Articles | Search | Subscribe (RSS)

Entries for the 'Solution Assessment and Validation (BABOK KA)' Category


» FEATURED: Using Extreme Inspections to Significantly Improve Requirements Practice
Article Rating (1581 Views) (6 Comments)
Using Extreme Inspections to Significantly Improve Requirements Practice Extreme Inspections are a low-cost, high-improvement way to assure specification quality, effectively teach good specification practice, and make informed decisions about the requirements specification process and its output, in any project. The method is not restricted to be used on requirements analysis related material; this article however is l...

» FEATURED: An Introduction to the Business Analysis Body of Knowledge (BABOK 2.0)
Article Rating (3632 Views) (2 Comments)
An Introduction to the Business Analysis Body of Knowledge (BABOK 2.0) The Business Analysis Body of Knowledge (BABOK® 2.0) is the definitive guide to the profession of business analysis. Every business analyst can profit from it, and few analysts can afford to be without it.

» FEATURED: Agile Business Analysis in Flow --The Work of the Agile Analyst (Part 2)
Article Rating (5075 Views) (8 Comments)
In Part 1 of  this article, I talked about the new skills and attitudes business analysts need to bring to agile development... Now it's time to talk specifics. What exactly do BAs do in agile development? How will your activities differ from those of traditional development? Let's take a look at agile business analysis from the perspecti...

» FEATURED: The Sound of Valid Requirements
Article Rating (1968 Views) (2 Comments)
If requirements management practices were songs entering a popularity contest, requirements validation would hardly be a favorite contender. It's easy to understand why: validation is usually a tedious, time consuming task, and, as with nearly every quality control activity, it is supposed to reveal defects, going against our natural desire of bein...

» Ten Application Definition Best Practices
Article Rating (2720 Views) (0 Comments)
The ubiquity of software project failures – with failure defined as projects that fundamentally failed to meet business-sponsor expectations, missed scheduled completion dates, or exceeded budget – is a pronounced theme in any number of independent research reports on custom software development. The Standish Group, for example, cited that only 31%...

» Enterprise Architect for Business Analysts
Article Rating (47292 Views) (7 Comments)
As a software architect and developer I’ve used Enterprise Architect (EA) from Sparx Systems (www.sparxsystems.com) for a number of years. In that time I’ve spent considerable time and energy trying to get our business analysts to do the same. While I’ve had some success I must admit it’s been an uphill battle. I suspect this is partly because EA i...

» Best Practices for Agile/Lean Documentation
Article Rating (2068 Views) (1 Comments)
Ideally, an agile document is just barely good enough, or just barely sufficient, for the situation at hand. Documentation is an important part of agile software development projects, but unlike traditionalists who often see documentation as a risk reduction strategy, agilists typically see documentation as a strategy which increases overall projec...

» Agile Requirements Best Practices
Article Rating (1295 Views) (0 Comments)
To be honest, I'm not very enamored with the term "best practice". I believe that the term "contextual practice" makes far more sense because what is a "best practice" in some situations proves to be a "worst practice" in others. Having said that, people are interested in best practices so here they are when it comes to agile requirements modeling:...

» Agile Requirements Modeling
Article Rating (1561 Views) (0 Comments)
Many traditional project teams run into trouble when they try to define all of the requirements up front, often the result of a misguided idea that developers will actually read and follow what the requirements document contains. The reality is that the requirements document is usually insufficient, regardless of how much effort goes into it, the r...

Do you twitter?: If you want short updates on what's going on in the BA world and at ModernAnalyst.com, simply follow us on Twitter: http://twitter.com/ModernAnalyst



Privacy Statement  |  Terms Of Use
Copyright 2006-2010 by Modern Analyst Media LLC