Information Technology Reference
In-Depth Information
Table 11.4
Agenda of
Time
Activity
presentation
8:30 a.m.
Start
QARs overview
Business drivers
Architecture plans
Purpose of meeting and expected outcomes
9:30 a.m.
Presentation of analysis of test cases #1 and #2
11:45 a.m.
Review of first two test cases and tailoring
of afternoon objectives
Noon
Lunch
1:00 p.m.
Presentation of analysis of two or more additional
test cases
4:00 p.m.
Wrap-up
Review of test cases
Summary
Review future activities
5:00 p.m.
End
the test case analysis. A sample agenda is shown below in Table
11.4
. During the
presentation, the facilitators and stakeholders should probe architectural approa-
ches from the point of view of specific quality attribute requirements. In addition
to the specific questions included in the test cases, the participants might generate
additional quality-attribute-specific questions for high-priority quality attribute
requirements. The conclusions, recommendations and action items resulting from
the presentation must be captured in a short report and distributed to the partici-
pants (Barbacci et al.
2002
).
11.3.1 Postmortem Review
Postmortem reviews focus on extracting lessons from the development team since
the software is delivered. Postmortem reviews need to be conducted shortly after
the end of the project so that minimal information is lost or distorted by subsequent
experience. The end of the project is usually a good time to assess which tech-
niques, methods and tools have worked and have been critical to the success of the
system. Even if the results of post mortems are not disseminated through the
company via formal channels, they can still be disseminated indirectly to the
project participants. Project participants are frequently reassigned to different
projects and often disseminate the lessons learned from the old project to other
parts of the company.
• Question about problems: What kinds of communication and negotiation
problems, that occurred, have emerged in the development of the system?
