If you intresting in sport buy steroids only here it true you find place where you can find information about steroids

From the category archives:

BA Knowledge

Business analysts apply knowledge from the BABOK and other resources to improve their performance against their goals. In this section, we explore each knowledge area and learn how to improve.

If your project is a turkey, kill it early

by Adrian Reed on February 1, 2012 · 4 comments

in Engaging the Business,Enterprise Analysis,Leading Organizational Change

Right, I might be branded a heretic, but I’m going to say it. Organizations that deliver every project that they kick off (with the project’s scope intact) are either extremely lucky, extremely risk averse, or extremely misguided. This sounds like a contrarian view, and may even sound a little controversial.  In fact, you might (quite [...]

{ 4 comments }

Why I may never adopt the practice of “just-in-time requirements”

by Adriana Beal on January 26, 2012 · 22 comments

in Agile BA Practices,Requirements Analysis,Requirements Elicitation

The agile movement promotes positive change when it encourages teams to work together to create products that are fit for purpose with as little non-value-added activities as possible. Agile approaches embrace mechanisms for continuous improvement, and include practices that can be traced to Lean thinking, a management philosophy that aims to identify what creates value [...]

{ 22 comments }

BA Stories: What are your requirements verification practices? (BABOK 6.5)

by Laura Brandenburg on January 23, 2012 · 7 comments

in BA Stories,Requirements Analysis

Verification ensures the intrinsic quality of the requirements. Although it would be a significant waste of time outside academic circles, I could verify requirements for a solution that had zero business value and that my organization had no intention of funding. They’d be verified but not validated (and we’ll get to validated next). The purpose [...]

{ 7 comments }

BA Stories: Let Your Stakeholders Know You Heard Them (BABOK 3.3, 3.4)

by Laura Brandenburg on January 16, 2012 · 7 comments

in BA Stories,Requirements Elicitation

While we’ve already talked about the importance of Preparing for Elicitation and Conducting Elicitation Activities, it’s not enough to stop there. The next two (and IMHO, critical) tasks in the Elicitation Knowledge area are Document Elicitation Results and Confirm Elicitation Results. The purpose of Document Elicitation Results is to: Record the information provided by stakeholders for [...]

{ 7 comments }

BA Stories: The Value of Reusable Requirements (BABOK 4.3)

by Laura Brandenburg on January 9, 2012 · 11 comments

in BA Stories,Requirements Planning and Management

When I first started my consulting business just over 3 years ago, I intended to focus solely on understanding the capabilities of legacy systems. Unearthing requirements had become a bit of a pet passion of mine and I realized that in every BA role I’d had in years prior, I was always trying to find [...]

{ 11 comments }

User Stories: Not Just Agile Anymore

by Steven A Jones on December 28, 2011 · 9 comments

in Agile BA Practices,Requirements Analysis,Requirements Elicitation

The User Story:  simple and elegant. “As a ______, I want to _________, so that I can __________.” Why must a user story only be used for Agile projects?  I was at a seminar recently where the speaker kept talking about user stories only in the context of an agile project.  Is there a thought [...]

{ 9 comments }

The Power of Index Cards

by Tony Heap on December 22, 2011 · 9 comments

in Agile BA Practices,Requirements Planning and Management

If you know even a little about Agile, you’ll have heard of the idea of using index cards for managing requirements. It might seem like a trivial concept, but I’ve had some unexpected successes with index cards recently, so I thought I’d share them with you. The concept Here’s the concept. Now, brace yourselves, because [...]

{ 9 comments }

BA Stories: Oh where, oh where does this requirement belong? (BABOK 7.2)

by Laura Brandenburg on December 19, 2011 · 1 comment

in BA Stories,Solution Assessment and Validation

Again, like we did in Assess the Proposed Solution, we are finding ourselves in the midst of the solution world in a very defined way. Allocating Requirements is a task that is done by someone, and if it’s not done by the BA, we might be missing an opportunity to create more value for our [...]

{ 1 comment }

Why board members are the wrong people to decide IT vendors

by Ryan Knapton on December 14, 2011 · 4 comments

in Creating alignment,IT Strategy,Solution Assessment and Validation

If I had a dollar for every time I heard a vendor say, “I know the perfect solution, and I just happen to sell it!” I’d be a retired BA. Instead, I’m a practising BA and one of my responsibilities is to help businesses understand that not all vendors are all-seeing and all-knowing. Nik Gebhard [...]

{ 4 comments }

BA Stories: Good Things Come in Nice Packages (BABOK 4.4)

by Laura Brandenburg on December 12, 2011 · 3 comments

in BA Stories,Communication,Requirements Specifications

There is a distinction between the project requirements and the requirements package. Requirements can be organized, sliced and diced, torn apart, allocated, put back together, assigned attributes,  etc. Packages are finely wrapped presentations of requirements in ways that suit a specific stakeholder audience. Very often we conflate the two, or start with the package before [...]

{ 3 comments }

← Previous Entries

Next Entries →