Business Analyst Community & Resources | Modern Analyst

The Community Blog for Business Analysts

Adrian M.

The business analyst cannot forget "The Why"!

There are many tools and techniques available to the business analyst for a variety of tasks. One of my favorite one is the short table-style template for documenting a "Problem/Opportunity Statement" as follows: The problem of <specify in one sentence the problem or opportunity bei...

1 Responses

This entry was published on Jan 08, 2009 / Adrian M.. Posted in Enterprise Analysis (BABOK KA), Business Analysis. Bookmark the Permalink or E-mail it to a friend.

Seven Words You Can Never Use in a Requirements Specification

This is the text of a presentation my boss had attended at a Telelogic conference and which, she later shared with the BA team at work. It lists specific words that when used in requirements, compromise the quality of the very requirements. I'll let the article describe further. Looking forward to some feedback...Les, thanks for your wisdom. SEVEN...

3 Responses

This entry was published on Oct 16, 2008 / . Posted in . Bookmark the Permalink or E-mail it to a friend.

Craig Brown

How to write Entity Relationship Diagrams

E R Diagram View SlideShare presentation or Upload your own. (tags: er diagram)

0 Responses

This entry was published on Aug 29, 2008 / Craig Brown. Posted in Data Analysis & Modeling, Systems Analysis, Business Analysis, Domain Modeling. Bookmark the Permalink or E-mail it to a friend.

David Wright

Memories of IT

I am now lucky enough to be working at a consulting company with a great group of experienced people, and we do share some great "war stories", and it made me think that I do have my share of experiences that, if written down, some small number of people may find interesting. Seems to me a blog is great for that. I would call this memories r...

0 Responses

This entry was published on Jun 19, 2008 / David Wright. Posted in Career as a Business Systems Analyst. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade - that's all 13 Principles of mine: do you have any? win a free copy of my book.

Thirteen is all you need, at least in this point in time. I may add to them as time goes by, but I would also like to hear from readers if they have any suggestions or thoughts or their very own principles for IT Projects success. Pleae offer them and maybe we can get them into the second edition of the book...which you all remember is available at...

0 Responses

This entry was published on Jun 17, 2008 / David Wright. Posted in Systems Analysis, Business Analysis. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade Day 15 - Principle #13: Use Architecture to Manage and Integrate the Deliverables

13. Given many medium to small software Deliverables, use Architecture to manage and integrate the Deliverables into a complete system. This is a more specific statement of Principle #3; in Cascade, an Information System Architecture is used to integrate the two week deliverables, until a complete deliverable (component, sub-system) is assemble...

0 Responses

This entry was published on Jun 13, 2008 / David Wright. Posted in Systems Analysis. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade Day 14 - Principle #12: Parcel work into two-week periods

12. Within the three month phase, parcel work into two-week periods; analyze for 2 weeks, then design and develop for 2 weeks (two developers), and then test for 2 weeks. When the first 2 weeks of analysis is done, start the next two weeks of analysis in parallel to the design/development; carry on in cascading 2 week periods until the entire proje...

0 Responses

This entry was published on Jun 09, 2008 / David Wright. Posted in Systems Analysis. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade Day 13 - Principle #11: Partition large projects into 3 month phases, that is the longest period you can plan for without the chance of significant change

#11. Partition large projects into 3 month phases, that is the longest period you can plan for without the chance of significant change to priorities, resourcing, etc. I was lucky to learn this early in the 90's as Project Management was getting a higher profile, accompanied by the increased use of Microsoft Project. Other PM tools wer...

0 Responses

This entry was published on Jun 05, 2008 / David Wright. Posted in Systems Analysis. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade Day 12 - Principle #10: Models are better than text

#10. Models are better than text. I would like to think that by this point in time, this principle no longer requires justification. It has been at least a few years since I last saw a dense “SRD” or “SDD” document (SYSTEM REQUIREMENTS DOCUMENT, SYSTEM DESIGN DOCUMENT). I must offer my respect to the many talented people who labored to produ...

0 Responses

This entry was published on Jun 02, 2008 / David Wright. Posted in Systems Analysis. Bookmark the Permalink or E-mail it to a friend.

David Wright

Cascade Day 11 - Principle #9: Leave a record of what you have done, so the project will not miss you if you leave

#9. Leave a record of what you have done, so the project will not miss you if you leave. If change is the only constant, then resources on a project will change. The risk in such change is that a person’s contribution to a project will be lost, and that the new person assigned to the project will have to start over. This is a particular risk in...

0 Responses

This entry was published on May 29, 2008 / David Wright. Posted in Systems Analysis. Bookmark the Permalink or E-mail it to a friend.

Page 33 of 36

First Previous 27 28 29 30 31 32 [33] 34 35 36 Next Last

Modern Analyst Blog Latests

Jarett Hailes

Three Audacious Goals for Business Analysts in 2013

As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...

Howard Podeswa

Hey IIBA, What’s Up With That?

Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...

Adrian M.

BA ABCs: “C” is for Class Diagram

Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN