Principles of agile business analysis

Business analysis in classical, hybrid and agile project contexts

/
Rainer Wendt describes the new structures for agile principles of agile business anaysis with the concept of planning horizons.
At a glance: All relationships between the core concepts

Core concepts of business analysis or: all about turtles

/
What do business analysis and turtles have to do with each other? Learn more about the BACCM mode, the core concepts and their relationships to each other.
Requirements workshops - determine requirements together

The ideal requirements workshop

/
Requirements workshops are a great technique for developing requirements. Where does this resonate in the execution, preparation and follow-up of a workshop?
Gather requirements with field observation

The best observation techniques in requirements engineering

/
Observation techniques like field observation, apprenticing and contextual inquiry are good development techniques in requirements engineering. What are some tips?
Perfect feature reviews - whenever you find the time.

The perfect review of features

/
For feature reviews, both review meetings and mechanical reviews are available. What is recommended when and how does a mechanical review go?
Problems - are they good or bad?

The problem with the problem

/
A good problem statement describes the task to be solved as generally as possible and so helps with the search for the right solution.
Agile Coaches

A Plea for the Agile Coach

/
How does the role of agile coaches in businesses look today? And what would organizations be missing is they went without agile coaches?
Migrating old systems is a real challenge

Migrate complicated applications agilely

/
How do you migrate applications? And why is it worthwhile to consider an agile, iterative approach?
Flash of inspiration

How does creativity come into IT analysis?

/
Does requirements engineering have to develop further to be able to design new solutions? And how can creativity be embedded into IT analysis?
Documentation with post-it notes does the trick!

Product specification – the seven biggest mistakes

/
Why do you want to specify products when you could just develop them? Seven reasons to renounce documentation.
Expanding your knowledge online

Where do you get your knowledge from?

/
Do you want to know something, learn to do something, or master something? An evaluation of knowledge acquisition and the importance of feedback by Dr. Andrea Herrmann.
Manufacture or Industry

Manufacture or Industry? IT doesn't have a choice!

/
Digitalization leads to new processes and structures. How should business IT set itself up to allow these changes?
Correctly exchanging requirements

Exchanging requirements correctly

/
A structured exchange of requirements among companies are not easy to arrange. The ReqIF standard in the OMG can help.
Eliciting usability requirements using a charrette session

Collaboratively developing usability requirements

/
A charrette session is a good opportunity to collaboratively develop requirements. What's important with charrette sessions?
Functional security

Practicing Functional Safety

/
The functional safety is concerned with the analysis of possible dangers and the definition of safety functions. How does that look practically?
The foundations of usability requirement

The foundations of usability requirements development

/
What should you pay attention to when developing usability requirements? What role does human performance capacities and perception play?
You should be careful while driving into fog

The paradigm shift in requirements engineering

/
Products have errors because the wrong employees carry out the wrong tasks. It is time for a paradigm shift.
Organisations often have to deal with too many requirements. Perhaps it’s time for a change?

Requirements with an expiration date

/
What can you do when there are too many requirements and you can't keep track anymore? Try working with templates and expiration dates.
Interview with Rainer Wendt

Becoming a Business Analyst – Interview with Rainer Wendt

/
An interview with Rainer Wendt, president of the IIBA Germany Chapter, about becoming a business analyst and business analysis in the IIBA Germany chapter.
Discussing content and arriving at better conclusions

What is requirements engineering and what content goes into a specification?

/
Requirements engineers translate users' desires into language that developers can understand. But what kind of content goes into a specification?

Effective teams with a unified vision

/
Effective teams are an important factor in developing products. A unified vision is absolutely necessary for team work to succeed. How do you develop it?

The solution evaluation in business analysis

/
Solution Evaluation is the assessment of existing or new solutions before or after a business goes into operation. Read more about Solution Evaluation.

Securing systems with misuse cases

/
Misuse cases are a good instrument in the area of safety and security to help you elicit quality requirements properly. How do misuse cases work?
5 Things software developers should learn

5 things software developers can learn from designers

/
Design thinking is the ability to perceive things that others cannot see and knowing how to execute ideas. What can developers learn from designers?
Addressing risks in agile projects

Addressing risks in agile projects

/
Find out how to develop systematic risk identifcation mechanisms in your projects so that you can manage and minize the risks you face regularly. 
IT Analysis 2016

IT Analysis 2016 – Taking Stock

/
There are many IT anaylsis concepts. Concepts that compliment each other, some that conflict and some that contradict each other. Time to take stock. 
Inspections as path towards good specifications

Inspection as the Path to Good Specifications

/
Errors in specifications are unavoidable. An inspection is used to find those errors. Here are six best pratices help you do so. 
The System Footprint

Visualized Understanding: The System Footprint

/
Using a system footprint to visualize your system requirements and allow everyone on your team to stay informed of the big picture. 

Lean traceability in three steps

/
Learn how to get the right amount of traceability in your agile projects. Improve your compliance and your overall performance through lean traceability.
Clear steps. Clear rules. High pace.

Agile Specifications

/
How do you get agile specifications done within 2 weeks by following 5 steps and 2 basic rules? Maik Pfingsten explains how it works.
The Internet of Things – Hype or Business Opportunity

The Internet of Things - Hype or Business Opportunity?

/
Are there sustainable business models able to prove that the Internet of Things is not just a concept but an economically feasible trend?

A Conversation with Peter Gerstbach of IIBA

/
The Guide to Business Analysis Body of Knowledge (BABOK) is a rich source of knowledge and another good reason for talking to Peter Gerstbach of IIBA.

Interview with Stefan Sturm, IREB

/
The following is an interview between Stefan Sturm, Managing Director at IREB, and Tanja Weiß of microTOOL, about ireb, cpre and requirements engineering.

When Run-of-the-Mill Is a Good Thing

/
Run-of-the-mill is a term that describes something that is of average quality, something that is mean, or cookie-cutter. But is it always a bad thing?
design thinking more than another method

Design Thinking

/
Design Thinking is more than just another method of solving problems. It is an attitude. Learn more about the 6 phases of Design Thinking.
The Golden Circle by Simon Sinek

The Golden Circle in Requirements Engineering

/
Why does a company do what it does? Why should customers opt for a solution of a particular manufacturer? The Golden Circle helps to answer these questions.
Understanding different points of view

Torn out of Context in Reverse at 50 mph

/
When eliciting requirements it is paramount to keep an eye on the context and on the background on which persons are creating requirements.
When personas meet use case 2.0

When Personas meet Use Case 2.0

/
What is the difference between Persona scenarios and use cases? And how do personas and Use Case 2.0 fit together?
The-ideal-number-of-diagrams

The Ideal Number of Diagrams and Diagram Elements

/
„How many diagrams are necessary to describe a system?“ Systems developers are familiar with these kinds of questions. But is the number really important?
System Context with Sunny Side Up

Industry 4.0 and the System Context

/
What is a system context, how do you make a smart visualization and what are the important benefits of system context diagrams?

On Your Mark, Get Set, Goal Diagram

/
If you are busying yourself with stakeholders and their goals, a goal diagram might be an effective and easy way for you to visualize interdependencies.
approach to requirements

Why the Right Approach to Requirements is Critical to Your Projects

/
How much time do you dedicate to requirements Engineering when you operate a project? Read why the right approach to requirements is critical to projects.
steps to good requirements

IREB: 6 Steps To Good Requirements

/
Requirements Engineering is a key discipline in systems development. Find out the 6 key steps to developing good requirements in your projects. 

Why not ask the stakeholders for once

/
How do you want to deliver good results if you do not know the goals of your stakeholders? Read what happens when you ignore stakeholders and their wishes.
Taking An Agile Approach With Use Cases

Taking An Agile Approach With Use Cases

/
For many companies use cases are the method of choice for stakeholder communication. Find out how they help us understand how a system supports users.