Information Technology Reference
In-Depth Information
Revision and review accomplish the code development/modification and review
of the objectives of the increment. These two activities are carried out in all the
iterations.
Monitoring involves monitoring the increment progress. The monitoring is carried
out by means of reaching the milestones, defined in the staging step. The result of
monitoring may be that the product is mature for reviewing or it is still in development.
Parallelism and flux indicate that teams can work in parallel, especially in
Crystal Orange or Red projects. When working in parallel, the synchronization
becomes important. Careful monitoring would ensure synchronization of work
between parallel teams.
Holistic diversity strategy splits large functional teams into cross-functional
groups so that each team would have specialists from multiple disciplines. This
allows the project to have smaller teams with required specialties. Instead of
having specialists at a central place and being used by all teams on a need-basis,
they are allocated to the team itself.
The methodology tuning technique uses team workshops and meetings to select
a development methodology and tune it to the needs of the project. In each
increment the team can draw lessons from the present increment and use it to
improve the performance for the next increment.
The user viewing techniques are basically reviews by end users ahead of the
software release. Crystal recommends two user viewings per increment. This
ensures that all user requirements are met by the release.
The reflection workshops are held twice: the pre-increment reflection workshop
and the post-increment workshop. Pre-increment reflection workshops facilitate
reflection on the experience of the previous increments so that the present increment
could be executed efficiently. The post-increment workshops facilitate reflection of
the events of the increment and to draw lessons for the future increments.
Crystal methods do not prescribe any development life cycle. So, the team can
choose any life cycle. Since there are no set phases, requirements are not restricted
to any one phase. However, the staging activity would have to consider require-
ments. Normally Crystal clear uses informal use cases to record requirements.
These would be traced through the software development using release plan and
test cases. Normally a user manual is also prepared and it would also contain proof
that requirements are indeed implemented.
15.11 Establishment of Requirements in Agile Projects
All agile projects do have some common aspects:
1. They all believe in the agile manifesto
2. They all require the full involvement of the customer or customer-representative
in the software development. Most specify co-locating the customer with the
Search WWH ::
Custom Search