Group items tagged

TDD34-8£60,000-6,064 (6.48%)1,470

BDD109-29£60,000+3.44%2,823 (3.02%)607

User Experience43+8£55,000-5,279 (5.65%)1,045

Cerificering IIBA biedt certificeringmogelijkheden voor business analisten en requirements engineers. Men kan twee soorten examen afleggen:

1. CBAP – Certified Business Analysis Professional. Om dit examen te kunnen doen moet men al voldoende jaren ervaring als business analist hebben. Vervolgens moet men ook een moeilijke examen, gebaseerd op BABOK (Business Analysis Body of Knowledge), afleggen.

2. CCBA - Certification of Competency in Business Analysis. Dit certificaat is bedoeld als een certificataat voor professionals die nog niet aan een hoge eisen van CBAP kunnen voldoen, maar wel de erkenning van hun kennis en kunde willen krijgen.

In my experience use cases are very powerful tools - their purpose is show the view from a *user's point of view*. The presented example is already very technical, and specifies a lot of details.

May I offer alternatives to the example in the article?A) A few brief classic requirements (for business) & a diagram (BPMN or UML activity diagram) (for the engineers)B) A use case with a lot less details (maybe 4-8 steps) & user interface design & a list of business rules (describing the essence of the details)C) No use case. One single sentence describing the goal & rationale ("As a user I want to have a recovery method when I forget the password because ....") & brief description of the important parts, business rules (no flow details!) & user interface design

May I offer other improvements to the "classic" use case in the example?- Instead of a summary, formulate it as a goal (remove redundancy)- Adding how frequently this is done ("Frequency: seldom, max. once per month ... once every few years")- Keep the main flow under 10 points- Remove pre-conditions and post-conditions. Keep it simple.- Integrate the alternative flows into the main flow (if possible, leave away details)

The Agile Extension to the BABOK® Guide

The importance of business analysis practices

How business analysis is performed in agile lifecycles

XP pretty much banned use cases, replacing them with the similar sounding “user stories”

Scrum did similar, using the “product backlog” instead of user stories

Yet as I go around projects, I keep running across organizations suffering from three particular, real, painful, and expensive problems

Through the new practice guide and PMI-PBA certification, PMI will drive an awareness of the role globally that IIBA® has simply not had the resources to do

To obtain a PMI-PBA, first you complete an application that verifies you meet the following requirements: Minimum of 3 years (4,500 hours) of business analysis experience within the past 8 consecutive years if you have a bachelor’s degree. (Or 5 years/7500 hours of experience if you do not.) (For comparison, the CBAP® requires 7,500 hours of experience and the CCBA® 3,750.) 2,000 hours working on project teams within the past eight consecutive years. 35 business analysis education (contact hours).

IIBA(tm)) announced the release of a draft of the Introduction for the Agile Extension to the Business Analysis Body of Knowledge (BABOK

many business analysts are struggling to understand how the role changes in Agile projects

"weak" or "sham" Agile implementations in organisations where "doing Agile" is not accompanied by any real cultural or governance change

Big-View (Product)

Pre-View (Release)

Now-View (Iteration)

shed some light on the difference between process maps and use cases.

different techniques and basically the result is the same

if you’re more comfortable with use cases then stick to them or if you’re more familiar with process maps then draw a map

to support the ability for systems to change, we should be able to safely make big changes (supported by automated scenarios), as well as the small ones (supported by automated object specifications).

Impact mapping

mind mapping

For most enterprises moving to Agile, this is a new and critical role, typically translating into a full-time job, requiring one PO to support each Agile team (or, at most, two teams). This role has significant relationships and responsibilities outside the local team, including working with Product Management, Customers, Business Owners, and other stakeholders

Without the right number of people in the right roles, bottlenecks will severely limit velocity.

BiZZdesign positioned as a Leader in Magic Quadrant for Enterprise Architecture Tools 2012

Focus op de toegevoegde waarde voor de klant staat centraal