Three Benefits of Use Cases

I recommend each person to use the use cases particular in Agile projects.

Below three are basic advantages that I think will convince you to use the use cases in Agile projects

1. Thanks to use cases, the context is gained

Even in Agile projects, use cases are a mechanism that allows companies to achieve their goals. An approach that uses structured requirements provides this context. In other words, usage cases let you determine what systems or other resources our system will work with.

2. Thanks to use cases, information about the scope of the project is gained

From the political point of view, the biggest problem with running an Agile project in a waterfall organization is improper determination of expectations regarding the project in terms of its duration and costs. Establishing expectations and securing both financing and support for the project may be more important than the implementation itself.

Scoping is primarily about setting the priorities of the people ordering the product and setting the time frame and delivery schedules.

The key here is to first review the scope of the project and then its thorough understanding by conducting iterations.

3. Thanks to use cases, a natural decomposition is gained

The proper approach to defining use cases for software development using the Agile method is to start with the scope definition. Once the scope has been defined, you must define the names of use cases and then gradually assign priorities and define in more detail the use cases when they are included in the project schedule. You also refactor use cases, consolidating and defining subordinate use cases as needed, and defining extensions of use cases if necessary.

More from my site

  • When is it worth modeling in UML? For some time, there has been a discussion about the value of modeling. Advocates of agile approach are not very happy to see models. Conservatives preferring the classic approach to the […]
  • Registration of Problems Identified During the Analysis I received an interesting question by e-mail: According to your knowledge, is there an object in EA that would be best suited for registering problems identified during business or […]
  • KANBAN – basic terms and rules This article opens a series of texts on Kanban. I am planning 7-8 texts in this area, which will be posted every two weeks. Let us start from the beginning. What is […]
  • Categorization of Requirements According to the Kano Model Defining the requirements that will increase the satisfaction of stakeholders from the system being created is crucial for the process of acquiring requirements. Implementation of too many […]
  • Requirements Management – Best Practices Ian Sommerville and Pete Sawyer in "Requirements Engineering: A Good Practice Guide" described, over 15 years ago, the method of assessing and improving requirements engineering […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top