Group items tagged

Requirements.net is home of the industry consortium for business analysis. Through focus on requirements definition, visualization, and management, the companies behind Requirements.net are driven to share and sponsor best practices and technologies to improve industry requirements practices

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

Welkom bij het DREAM Event Atos Origin organiseert op dinsdag 9 maart 2010 voor de tweede keer het Dutch Requirements Engineering and Management event. Het event is open voor de gehele Requirements community; voor iedereen die werkt met specificaties.

Hartelijk welkom op de website van DREAM (Dutch Requirements Engineering And Management). In 2014 is al voor de 5de maal het DREAM event succesvol georganiseerd (zie hier een terugblik op de afgelopen events). We willen ook de komende jaren een bijdrage blijven leveren aan het verder verspreiden van de kennis en het begrip betreffende alles wat te maken heeft met requirements; van business rules tot en met user stories, van functioneel ontwerp tot en met modellen van bedrijfsprocessen.

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).

Requirements analysis

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.

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)

Focus op de toegevoegde waarde voor de klant staat centraal

MKS Named a Leader in Forrester’s Analysis of Agile Development Management Tools

MKS is pleased to offer you a complimentary copy of this independent research

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)

Inclusion

Clarity

Streamlining

Gherkin

test automation

The Big BDD Picture: The main goals of BDD are collaboration and automation