Roles have activities that define the work they perform. An activity is something that a role does
that provides a meaningful result in the context of the project.
An activity is a unit of work that an individual playing the described role might be asked to
The activity has a very clear purpose, normally expressed in terms of creating or updating some
artifacts,like a model, a class, a plan. Each and every activity is assigned for a specific role. The
granularity of an activity is basically a few hours to a few days, it generally involves one role,
and affects one or only a small number of the artifacts. An activity must be used as an element of
planning and progress.If it is too small, then it will be neglected, and if it is too large, then the
progress would have to be expressed in terms of an activity’s parts.
Activities should be repeated number of times on same artifact, especially when going from one
of the iteration to another, refining and expanding the system, by means of the same role, but not
necessarily of the same individual.
Activities are broken down into several steps. Steps fall into the three main categories: