This event is history, please check out the NEXT SESSION
Check out our related open workshops:
Check out our related in-house workshops:
|FREE BOOK for all participants:|
This programme is spread over 2 days, from 10h00 till 18h00, with a buffet lunch around 13h00. Our workshop leader will already be present from 9h30 to answer your questions and talk about your specific business analysis, requirements and/or innovation problems if you want this.
James Robertson and James Archer are experienced consultants, teachers, authors and practitioners whose area of concern is the requirements for products, and the contribution that good requirements make to successful projects. Their work in the area of business analysis and requirements gathering is valued by clients around the world.
We explore business analysis and show you how you can be more agile, more adaptable in your business analysis activities.
We take you through a framework for discovering the customers and their needs, for finding solutions and evaluating them, designing the business solution and getting it built. We look at how business analysis integrates with either agile or traditional development.
Identify and prioritise the customer segments. Customer, or user, segments are groups of people with the same characteristics and the same needs. For the highest priority segments, you produce value propositions that set down what you must deliver to satisfy the customers’ business needs. This value proposition is the foundation for what is to follow.
You ensure that it is worthwhile to provide value to a customer segment by looking at the value the segment brings to your organisation.
The business problem is, “How might you deliver the value proposition?” You and your team generate candidate solutions. Instead of stopping at one, you always find that subsequent candidates improve on the original.
To prove that a candidate is solving the right problem, each is the subject of a safe-to-fail probe. This is a quick, cheap experiment to determine the viability, the suitability and the outcome of a solution. You are also working with your customers to ensure that the candidate is solving the right problem and fulfilling the right need.
The solution space includes the people, software and devices used to fulfil the needs of the customer segments. When you are investigating this space, you are looking at the necessary business processes, and perhaps building process and data models of them to help with your understanding. You also scope the space so that the team can agree on the extent of the solution.
The solution involves, and is used by humans, so the investigation studies the culture and characteristics of the people involved in the solution. The investigation is quick, but thorough enough to prevent any nasty surprises for the development team.
Anything worthwhile is designed. Here you design the business solution to make it usable and convenient. The designing business analyst uses elements of the problem, the desired impact of the solution, the behaviour of the target customer segments, and the value proposition to craft the best possible solution.
Any valuable solution will be innovative. This section looks at some innovation techniques, especially in the areas of providing better information, and making the solution more convenient for its users.
Stories are fundamental to most agile development. However, if they are to be useful, the stories must be the right stories. This section gives you an approach to writing the right stories, ones that address the real customer problems.
We also show you how story maps give you a more descriptive and usable backlog. Story maps are the ideal repository for the information you are discovering, and the stories needed for the development cycles.
This section reviews the course and points out how by being agile, business analysis can be done quickly. We also look at other aspects of business analysis, how to break down silos, the minimal amount of effective documentation.
We take a look at lean thinking, and how the agile business analyst can avoid waste, unevenness and overburden.
While you can do your business analysis in an agile way, some organisations require a traditional requirements specification – so we show you how to build one from the results of your agile analysis.
This is a very brief overview of the programme of this unique workshop (spread over 2 days):
9.30h - 10.00h- Registration (only first day), coffee/tea and croissants
10.00h - Start of each workshop day
18.00h - End of each workshop daySPEAKERS » REGISTER »