Home Page

Communication

JJournal

Jabian Journal and Visual Communication

My employer, Jabian Consulting, produces a semi-annual publication of our consultants’ latest thinking on today’s most important business and technology issues. The Spring, 2014 issue just came out today, and it’s really good (and I’d say that even if I didn’t work there!)! You […]

Methodology

rowing

It’s (Still) All About the Team

If we can learn those basic, timeless principles that make any project successful, we’ll be able to identify them and adapt more easily to any environment whether waterfall, spiral, scrum, or the next big thing. One of those principles is that of enabling and empowering the cross-functional team.

waterfall

Agile and Traditional Methodologies Compared…. Again

This post is spurred by a few articles I’ve read recently which have only served to reinforce some similar thoughts I’ve been having for a while now on the constant, competitively toned comparisons between agile and traditional development methodologies.

As I read article after article extolling the wonders of these new methodologies against the weaknesses of the traditional methods, I begin to wonder if the emphasis isn’t too much on agile methodologies over agile principles.

Professionalism

handsacross

The Benefits of a Sincere Compliment

Mark Twain once said, “I can live for two months on a good compliment,” and I think many of us would agree with him. The “business” of delivering business solutions can be a stressful and, at times, seemingly thankless one. […]

Requirements

stack of colorful binders in a office

Roughly Right, or Precisely Wrong?

John Maynard Keynes, the acclaimed economist, once stated, “It is better to be roughly right than precisely wrong.” This holds true for business analysis and solution requirements.

inventory

“Requirements as Inventory” Metaphor

Think of requirements as inventory or as component materials in a storage bin with a shelf life and a carrying cost. Inventory isn’t free. You have to pay someone to produce (model and document) requirements. You need a supply of good, current (fresh) requirements to produce a quality product.

Requirements Model

A Requirements Model (Graphic)

There is no perfect, fits-all template or set of documents which will be effective across all companies or even for all of a given company’s projects. The business analyst should work with internal and external stakeholders to determine which communicative tools will best serve for each project effort and model requirements accordingly.