A strategic requirement is something an organisation sets out to achieve; it could be the long-term vision the organisation sets itself, the key business condition for a specific project to be a success or a business strategy to achieve a goal. A set of strategic requirements defines the goals, strategies and tactics that organisations need to put in place to give them direction and impetus. Business analysts and consultants have to understand strategic requirements to know where projects can deliver business benefits and where not. The ability of the analyst to interview, gather, analyse, model and present strategic requirements is key to success. The primary tool consultants and business analysts use for communication is talking; but, if you cannot present all that incredible information back to your client effectively, it is hard for them and you to get to grips quickly enough with what is going on. Being able to present a model is really powerful because it provides a visual format and structure on one page to reason about those strategic requirements. Dr Karl A. Cox offers a process, guidelines and ideas - that have been tried and tested in practice - for conducting interviews and shows you how to rapidly turn interview findings into strategic requirements models all on one page, to present to your clients, customers, team and / or supervisors.
Table of Contents
2. The plan
3. What questions are you going to ask?
4. Conducting the interview: what to say
5. Interview analysis
6. Strategic modelling
7. Presenting your work
8. Concluding remarks
’Karl Cox is the world's foremost expert on strategic requirements. He’s helped countless businesses achieve success where other analysts have failed. If you reside at the pointy tip where business strategy and technology meet, this book is a must-read. For those who wish to be at the top of their game and masters of their domain, this book shows you how.’ Steven Bleistein, CEO, Relansa, Inc., Japan ’What I love about this book is the thorough coverage of probably the most important part of the requirements process, the art of gaining knowledge from the client. Even better, is the clear and accessible style, guiding the reader through by reference to real cases. I would recommend this book to any student of software requirements, and will definitely recommend it to my own students.’ Keith Phalp, Bournemouth University, UK