Workshop: Creating a Vision
Document
Most beneficial done early in the Inception Phase. After a
short presentation on the purpose, usage, and format of the Vision Document, the
workshop would work section-by-section in creating a first draft. At the end of
the workshop, the state of the Vision Document would be reviewed and team
assignments made to go forward. The workshop is also useful if a straw man
document exists as an input to the workshop.
Workshop: Addressing Stakeholder
Comments
Most beneficial done in the Inception Phase after first
comments have been received by the project team from key stakeholders. This
workshop helps the Vision Document author to properly disposition stakeholder
comments. Particular emphasis is placed on whether comments on features is best
contained within the Vision Document or more appropriately reserved for lower
levels of specifications (e.g. use cases or supplemental specification).
Workshop: RequisitePro
Configuration Check
Most beneficial done in the Inception Phase. This workshop
works predominately with the RequisitePro tool administrator and the lead
analyst (should they be different). The consistency of the requirement types and
document templates within the tool with the project needs will be reviewed and
adjusted, if necessary. Attributes associated with requirement types will be
reviewed and discussed. The method by which project personnel will be added to
the RequisitePro project and associated security considerations will also be
reviewed. At the end of the workshop, the state of the tool schema would be
reviewed and team assignments made to go forward.
Workshop: Identification of Actors
and Use Cases
Most beneficial when done in the Inception Phase after a draft
Vision Document is in existence. After a short presentation on what use cases
are, the workshop would proceed to identify system actors, the goals they seek
to realize by interacting with the system, and a set of base use cases. For each
identified use case, 2-4 sentences describing the use case will be developed.
The information would be captured in UML format with the project team’s
visualization tool. At the end of the workshop, the state of the UML survey
would be reviewed and team assignments made to go forward.
Workshop: Prioritizing Use Cases
Most beneficial when done in the Inception Phase and must have
at least first drafts of Identified Use Cases and a Notional Architecture. After
a short presentation on how Architecture Significance and Business Value are
used in allocating use case scenarios to Iterations, the workshop would work
through each identified use case and prioritize them (High, Medium, or Low) in
the two dimensions: Architecture Significance and Business Value. Viewpoints
into the notional architecture will be needed to help support the Architectural
Significance related discussions. At the end of the workshop, the state of the
Use Case prioritization would be reviewed and team assignments made to go
forward. This workshop can be repeated after Use Cases have been outlined.
Workshop: Outlining Use Cases
Most beneficial when done whenever outlining begins. Typically
outlining will be done either late in the Inception Phase for use cases
allocated to the first Elaboration Iteration or early in the Elaboration Phase.
After a short presentation on what outlining use cases is and how it plays in
between Identification and Detailing, the workshop begins to outline use cases
in a JAD session manner. In a typical ½ day workshop, 2-4 use cases can be
outlined. At the end of the workshop, the state of the Use Case outlining would
be reviewed and team assignments made to go forward. This workshop can be
repeated for different sets of use cases.
Workshop: Refactoring the Use Case Model
Most beneficial when done after outlining of use cases has
begun and the project team has begun to refactor base use cases into a
collection of base use cases and abstract use cases associated by Includes and
Extends. After a short presentation on what constitutes base and abstract use
cases, includes and extends, the project’s use case model will be reviewed in
the context of industry best practices. Recommendations will be made on how to
refactor the model to both satisfy team goals and to be more consistent with
best practices. At the end of the workshop, the state of the Use Case Model
would be reviewed and team assignments made to go forward.
Workshop: Detailing Use Cases
Most beneficial when done after an initial set of use cases
has been outlined. Typically detailing will be done during the Elaboration
Phase, though one may be done prior to Inception end to gain agreement within
the team as to what constitutes a detailed use case. After a short presentation
on what detailing use cases is and how it plays in with Identification and
Outlining, the workshop begins to detail use cases in a JAD session manner.
Special attention would be given to how to deal with business rules, data
dictionary, preconditions, post conditions, and how to couple other related use
cases. In a typical 1 day workshop, 1-3 use cases can be detailed to a rough
draft quality. At the end of the workshop, the state of the Use Case detailing
would be reviewed and team assignments made to go forward. This workshop can be
repeated for different sets of use cases.
Workshop: Supplementary Spec 101
Most beneficial when done after Use Cases have been
identified. After a short presentation on what the Supplemental Specification is
and how it plays with the Vision Doc and the Use Cases, the workshop begins to
walk through the Supplemental Spec template. For each section of the template,
the applicability to the program and how best it should be leveraged will be
discussed. Special attention will be given to the treatment of business rules,
data dictionary, and interface specifications (or interface control documents).
At the end of the workshop, the state of the Supplemental Spec would be reviewed
and team assignments made to go forward.
|
