20+ years business analysis experience of author Mark Ridley is distilled into this guide for new or would-be business analysts. Mark's experience has been gained on large and multi-£million business change projects in both the public and private sectors.
This guide is written for projects where a supplier - whether internal or external - is providing the solution. Mark covers the role of a BA from project inception (or just before) to handover to the solution provider. He presents a minimum set of structured tools and techniques that define the core deliverables of any business change project. Pretty much anything project-related that a BA is asked to do can be derived from them - whether it's estimates and product definition for a project manager or supporting the business in their workflow redesign.
Mark includes a section at the end of each chapter that offers related information, best practice tips, and guidance on the softer skills a business analyst needs.
You'll see how the various techniques are used in the stages a business change project experiences - from analysis of the As-Is to a full specification of business requirements for the To-Be.
If you're expecting to find Agile techniques covered, you'll be disappointed. This guide is about Business Analysis, not Systems Analysis. Systems analysis is where specification of a computer system is the result and that's where Agile can come into its own.