Wiki
This website is a wiki. If you like and use our processes, techniques and tools, please add your experience and best practices. Just register and share.

Contents


User


Smart


Community

Forum






The sub-stage Plan in most cases consists of a single workshop. Primary goal for this stage is to establish the smart use cases that will be delivered at the end of the upcoming iteration.

Introduction

Smart

Smart


Goals

  • Goal. Describe goal
  • Goal. Describe goal

Steps

  • Step. Step that contributes to realizing goals.
  • Step. Step that contributes to realizing goals.
  • Step. Step that contributes to realizing goals.

Techniques used

  • Nice technique, such as smart estimate, or use case diagram
  • Nice technique, such as smart estimate, or use case diagram
  • Nice technique, such as smart estimate, or use case diagram

Additional info.

Picking smart use cases

There is a straightforward scenario for picking the smart use cases for an iteration:

Establish iteration velocity

You will need to know the iteration velocity of the project, expressed in the number of smart use case point the team is able to handle during an iteration. At best, this velocity is calculated over the previous iterations in the same project. For instance, if 3 iterations have been done, and during these iteration the total number of 36 smart use case points was realized, the velocity for the next iteration will be 12 smart use case points.

Suggest smart use cases

Next, the project team suggests to the customer the smart use cases to be done. This suggestion can be based on a large number of criteria, for instance the use cases that have the highest business value, or that exclude the largest (technical or functional) risks, or perhaps the use cases that test a new architecture the best. How many smart use cases are suggested depends upon the iteration velocity. Because each of the remaining smart use cases was estimated at a specific smart use case complexity, you will be able to suggest a number of use cases such that their total complexity more or less matches the iteration velocity. That is, if your iteration velocity equals 12, suggest a couple of smart use cases that sum up to about 12 smart use case points.

Select smart use cases

In the end, the customer decides. So, either following the suggestion made by the team, or alternatively selecting smart use cases that match his or her criteria, the customer picks the smart use cases he or she wants to realize during the upcoming iteration. Under normal circumstances, our experience is that customer are very happy with the suggestions made by the team.
  Name Size