In this article, you will find a Scotland Email List of a use case, its advantages and its methodology. I wrote a blog post in September on the importance of asking the business needs of users regardless of solutions and technologies . And yes !!! Not all people working in companies are tech-savvy or tech-savvy. It is not for them to say which solutions will solve their problems. It is up to IS architects, project managers or IT managers to identify the solutions. And it is also up to them to formalize the needs in the form of a use case or a user story.

Two common mistakes can send a project straight into the sky Error 1: No longer involving users until the end of the project and the delivery of the product. My colleague Eric wrote a great article on this topic Error 2: Badly formalizing the need with the user, therefore choosing a bad solution. This usually leads to a double frustration when presenting the solution: The user will think that the project manager has misunderstood his need … or worse that he is not able to meet his need The project manager will say to himself that he worked for nothing… or worse will say that the users do not know what they need. Hello Steve Jobs!

Two common mistakes can send a project

This situation is far from rare and it is one of the main causes of project failure! It’s like realizing after 100km that you’ve gone in the wrong direction… it’s hard! So you have to check your itinerary before you go. How to avoid the error: correctly formalize the need with the user and make him validate it (or iterate with him) There are 2 tools to properly formalize the business needs of a user: use cases and user stories. I present to you today the use cases. A use case is a text describing a set of actions to cover a need. A use case must be able to evolve throughout the project or the product life cycle. In addition, in French we can also hear the following translations: use case or use case

Scotland-Email-List

When building a restaurant, an architect must formalize the use case of the following customer need: ” Go to the bathroom without disturbing the service or other customers”. Action 1: The customer moves. In order to prevent the customer from getting lost in the restaurant or obstructing the service and other customers, the position of the toilet must be obvious or the display must be clear and visible regardless of the customer’s position in the room Action 2: If the toilets are occupied, the customer must be able to wait in an area, close to the door, without being an obstacle

How to avoid the error: correctly formalize

Action 3: The customer opens the bathroom door. The door should ideally open outward if it does not bother anyone, otherwise open inward Action 4: … I’ll spare you the rest, if I had done the exercise to the end I would easily have gone up to 20 actions. Nevertheless we can see the advantages of a use case on these 3 examples of actions The need is understandable by everyone, whether it be future users, customers, architects, technical studies, project management, project managers … all stakeholders can easily project themselves: For customers: There is a good chance that you have found yourself in action 1 and action 2. Personally 1 time out of 2 I wander in the restaurants to find the toilets and I end up disturbing the waiter for him ask for help

For technical experts and architects: they can understand the context without knowing anything about the job of a restaurateur or a waiter and offer the right solutions For project managers or salespeople: thanks to this use case, they can quantify the effort or cost of each action Formatting allows stakeholders to define in the list of actions, those which are priority, imperative or optional There is no hole in the racket, the whole experience is taken into account in this use case, which makes it possible to anticipate potential subjects or identify opportunities Within Semeia we have the Banque des Territoires as a shareholder.

Leave a Reply

Your email address will not be published.