Author Archive: JB

Jonathan Babcock is a business analyst who thoroughly enjoys what he does. Practical Analyst is his outlet for sharing what he's learned, and for interacting with like-minded folks.

To keep up with the latest on Practical Analyst, you can subscribe to the RSS feed, follow Jonathan on Twitter, or view his profile on Linked In.

rss feed Facebook Twitter Google Plus LinkedIn

"Party of Four" Key Considerations in Product Development

"Party of Four" Key Considerations in Product Development

| February 15, 2007 | 1 Comment

This “party of four” key considerations comes from Adam Bullied at writethatdown.com. Basic? Absolutely. Product management 101 type stuff? Yes, sir. But if you’re not including these 4 key and simple concepts in your product planning you probably ought to.

Continue Reading

Business Analyst Job Description

Business Analyst Job Description

| February 14, 2007 | 37 Comments

So, what exactly is a Business Analyst? What is the role of the Analyst in the software development lifecycle? If you don’t want to be completely confused, don’t bother trying to get a conclusive definition by just “Googling” it. There are dozens of variations on the BA role depending on the company, and on the software engineering methodology used.

Continue Reading

Functional Specs: Don't write them??

| February 13, 2007 | 0 Comments

“Functional specifications documents lead to an illusion of agreement. A bunch of people agreeing on paragraphs of text is not real agreement. Everyone is reading the same thing, but they’re often thinking something different.”

Continue Reading

Great Software Engineering Proverbs

Great Software Engineering Proverbs

| February 13, 2007 | 0 Comments

Lots of software engineering quotes and maxims. Some of them hurt to laugh at because they’re so true, some are classics, and some are just hilarious.

Continue Reading

Avoiding the "How" Trap in Requirements Authoring

Avoiding the "How" Trap in Requirements Authoring

| February 12, 2007 | 1 Comment

One of the main challenges in drafting requirements is to state “what” the solution must entail, and not “how” the solution must be tailored. I found the excerpt below from a paper authored by Ivy Hooks very helpful.

Continue Reading