Abstract

Everyone has heard about Agile.

User stories, product backlogs and iterations are no longer terms that come from another planet.

But do you know how every piece fits the puzzle?
And what the added value of analysis is in this development approach?

Price

Abstract

A must attend if you have even the smallest interest in analysis.

Get an answer to any 'W' question you've never uttered out loud.

What is analysis?
Who does this analysis?
Where and when do you do analysis?
How do you do it?
And why?

Price

Abstract

Analysis is more than talking to a couple of stakeholders and drawing up some requirements for a system to be developed.

There's an entire process behind it, closely linked to your development approach.

Price

Abstract

Analysis is more than talking to a couple of stakeholders and drawing up some requirements for a system to be developed.

There's an entire process, closely linked to your development approach.

In this session we dive into the process that is mapped onto Agile development approaches.

You will also get familiar with the typical work products related to Agile analysis.

Price

Abstract

To drawing the requirements that deliver the most value to your stakeholders you first need to know who these stakeholders are.

Who to include ?Who not to include ?
What is it that they need ? When do they need it ?

This session gives an insight into the creation and use of persona's when you are delivering value to customers.

Price

Abstract

How do you get the necessary information to derive your set of requirements?

How do you extract requirements from sources that are outdated or when they don't know what they want (yet)?

In this session we will give you an overview of different elicitation techniques from a practical point-of-view.

You will learn which technique is most suitable for each objective and kind of requirements. Discover benefits and pitfalls, best practices and practical guidelines.

Price

Abstract

The focus in agile development is on incremental delivery of the most valuable features first and fast feedback.

This often requires a different approach to elicit your requirements.

In this session you will learn how to embark on a customer journey and slice your releases based on priorities.

Price

Abstract

Design thinking is more than just the latest buzz word within the domain of analysis.

It's an emerging way of working that combines a lot of best practices to increase the value for your end users.

In this session you will get an introduction on the structure of design thinking and the different elements needed to complete it.

Price

Abstract

Once you've elicited your requirements, they are inside your head.

This is not the ideal situation as there exist no techniques to pull them out of your brain whenever they are needed.

You need to document your requirements so they are accessible whenever someone needs them.

In this session you will discover how you can document your requirements and keep them alive in the most useful way, depending on your development model and your stakeholders.

Price

Abstract

A picture says more than a 1000 words.

There exists a multitude of models you can use to document your requirements, but which one should you use?

Behold their beauty and keep your eyes open for all these different models, each with their own specific purpose, syntax and semantics.

Price

Abstract

We usually look at analysis through a pair of software- or product development glasses, yet a lot of the techniques, practices and principles are also applicable when doing analysis of non-IT products.

In this session you will expand your view and discover how the toolbox you've filled during this summer school can also be used for other products.

Price

Abstract

Through role-play examples, we will answer questions such as:

What are the requirements for any kind analyst?
How do I keep track of the bigger picture and not lose myself in all the details?
Which skills are indispensable to start as an analyst? To grow?
How do you deal with difficult stakeholders?

Price

Abstract

Analysis is more than just drawing up requirements for something new, you also need to make sure that your requirements are set up and maintained in such a way that they remain useful throughout their entire lifespan.

What should you consider for this?

And what are best practices in doing so?

Price

Abstract

It is done.

You have a finished product.

How do you know if your requirements were good?

When and how can we validate a working product with our users?

How do we gather their feedback?

What do we do with this information?

You will get the answers in this session.

Price

Abstract

Without change, there is no evolution.

Requirements will change and you shouldn't fight this fact as it is beyond your control.

You do have power over the way you handle these changes and it's in everyone best interest that you manage this properly.

How do you find the balance between initial effort and change?

How do you make sure you keep requirements valuable throughout the process flow?

Price

Abstract

Low/no code is the next best thing.

Through a graphical user interface, less technical people can now develop their own applications.

But since nobody starts building something without a plan, you still need to do some form of analysis.

Which tasks are important in a low code environment?

Which (new) challenges emerge and what makes life easier?

Price

Abstract

Documenting business processes is important to understand the business goals and how to achieve them.

BPMN is currently the most popular language to model these business processes.

In this session you will get an introduction on BPMN and learn about its advantages, best practices and some generic guidelines.

Price

Abstract

What about the non-functionals?

Usually they are not the first thing that comes to mind when you are exploring the options for new features, yet their impact can be massive.

Stakeholders usually don't have a direct answer when you ask about them, so how can you elicit them?

And how should you document them? How much information is sufficient?

Price

Abstract

The end users will always be your most important stakeholders and the real-life experience this user has with your product is becoming an increasingly important unique selling point.

What is this so called User Experience (UX)?

How does it affect your product and how can you increase it?

We've invited a specialist to tell you more about it.

Price

Abstract

Using specification by example allows you to document your requirements and write your test cases at the same time.

In this session the focus will be on coming up with the right examples to cover your requirements.

After a short introduction, you will take a deep dive into this marvelous world, learning its advantages and disadvantages, best practices and common pitfalls.

Price