Requirements are easy, people are not. It's great talking about user stories and use cases and rapid prototyping - but how do you know you have the RIGHT use ca

Requirements are easy, people are not. It's great talking about user stories and use cases and rapid prototyping - but how do you know you have the RIGHT use cases and user stories...? What follows is one way to get requierments right - ¹ Current State Assess the situation. Understand the transformation (one or more processes) the client seeks to address, and find out what the technology landscape looks like. Start identifying stakeholders, and familiarise yourself with the client's worldview, environment, and the power and political landscape. ² Objective Identify who the client is, and define the client's objective. The objective is specific, measurable, agreed to by the client,realistic, and time-boxed. It is guided by the results of the situational analysis. ³ Scope Bound the solution by outlining it's features and functions, by defining what's out of scope, and by discussing the criteria by which success is measured. The scope delineates what stakeholders expect the project to deliver. It's not hard but it's not going to fall into your lap without a little effort. ¹ https://www.wittenburg.co.uk/Work/Transformation.aspx https://www.wittenburg.co.uk/Work/Transformation.aspx ² https://www.wittenburg.co.uk/Work/Objectives.aspx https://www.wittenburg.co.uk/Work/Objectives.aspx ³ https://www.wittenburg.co.uk/Work/Scope.aspx https://www.wittenburg.co.uk/Work/Scope.aspx (Being nice helps too - people like helping nice people -- https://www.wittenburg.co.uk/Work/Trust.aspx https://www.wittenburg.co.uk/Work/Trust.aspx)