This event is history, please check out the NEXT SESSION
Check out these related open workshops:
Check out our related in-house workshops:
What will you learn here ?
By attending this two-day course, you will learn:
Why we organize this workshop: Increasing importance of business analysis and business analysts
|FREE BOOK for all participants:|
Whether you work in an agile team, or write traditional specifications, the essential business analysis task is to uncover the real needs of the real customers. Without understanding the real need, it is extremely difficult to deliver real value. Actually, assuming you know the solution is where many agile projects go astray, and is also where good business analysis shows its true value.
Your organization is constantly having to adapt to the relentless changes to its environment – changes to the law, changes in the marketplace, changes in technology, and changes to the available opportunities. Any change results in a development effort to deliver a new or enhanced software system, business process, consumer product or service. Furthermore, the rate of change is so rapid that we simply don’t have time to get the wrong result and deliver the wrong solution.
This course is about using analytical skills to understand the real, underlying problem to solve. It is about integrating business analysis skills into your team regardless of whether it is an agile team, or a more traditional one producing a complete requirements specification. It is about ensuring that you always deliver the right solution, and that you deliver quickly.
This workshop is based on a brand new book with the same name. We had hoped to get it at our workshop, but Addison Wesley can't deliver on time. We promise to send participants of our "Business Analysis Agility" workshop a free copy when it finally becomes available.
Who should attend this workshop ?
Business analysis is a skill that should be present in all development efforts, and in day-to-day organisational tasks. The skill is usually, but not necessarily, associated with job titles such as:
We also believe that Business Stakeholders, Users, Software Customers and Testers will benefit from learning advanced business analysis techniques, and how they can contribute to the organisation's wellbeing.
Why should you attend this workshop ?
Despite our technological advances, the biggest problem is still the human one: how to correctly understand the customer’s real problem, and how to ensure that your solution is correctly solving that problem.
The real problem is not found by running endless prototypes past our customers. Nor is it likely that an assumed solution will deliver much value. However, analytical thinking uncovers the real needs and allows the right solution to emerge. This means:
This course gives you a different approach to business analysis. This one provides a business analysis framework that works regardless of whether you are part of an agile environment and need to provide stories for iterative development, or whether you are in a traditional environment and need to produce a requirements specification suitable for more formalized environments and outsourcing.
What’s in it for You ?
Our businesses thrive or flounder on the effectiveness of their business processes, both automated and manual. Businesses with good processes provide a better service and are more responsive to their customers. The converse is also true. Business analysis is the craft of enlightened improvement to business systems and processes. Moreover, business analysis gives you ways of identifying the areas where development efforts will yield the highest value.
This two-day course in business analysis gives you the skills and tools to discover your client's real business, and to determine and demonstrate the best ways of improving it.
This course gives you a vision of the modern business analyst, one who understands the business analyst's role is much more than writing requirements. This course is a natural companion to Mastering the Requirements Process, where we teach the art of requirements writing. The models and understanding from Business Analysis Agility are the foundation for your requirements process.
|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 is an experienced consultant, teacher, author and practitioner whose area of concern is the requirements for products, and the contribution that good requirements make to successful projects. His 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 demonstrate how business analysis can be integrated with, and improve Agile methods such as Scrum, Crystal, etc.
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.