Project Organization

• The fictitious company SEP consisting of two staff members has defined software engineering projects to be executed by groups of students.

• Each project has an external customer (initiator).

• A project consists of a group of approximately 8 students.

Project Management

• The organigram of each project is more or less like in the example.
  Each group has a project manager (a student that follows 2IP45).
  Furthermore, each group has a technical advisor (staff member) to advise in technical questions and to review the technical documents.

• Each group should have a regular internal progress meeting every week (e.g. on Monday).
  Topics of these meeting are the work done last week, deviations to the plan(ning), and the work to be done in the coming week.

• Progress meetings between project manager and senior management will be held once every 14 days.
  A progress report must be prepared for each progress meeting.

• All project members should keep track of the hours they spend on each work package.
  The list of packages is shown below.

  The Project metrics should be sent weekly to senior management.
  This amounts to two lists:

  Activity	Hours spent this week
  Non project related	...
  General project related (progress meetings, SPMP writing, etc)	...
  Documentation, specification, design (all activities leading to such results)	...
  Source code	...
  Testing, verification, consolidation	...
  Rework	...
  Total	40 * group size (includes project manager)

  and

  Work package	Hours spent this week	Hours to go till end of project (new estimation)
  SPMP	...	...
  SVVP	...	...
  UTP	...	...
  ITP	...	...
  STP	...	...
  ATP	...	...
  SCMP	...	...
  SQAP	...	...
  URD	...	...
  SRD	...	...
  Prototype	...	...
  Research	...	...
  ADD	...	...
  DDD	...	...
  Code	...	...
  SUM	...	...
  IT,ST,AT	...	...
  STD	...	...
  Formal reviews	...	...
  Meetings	...	...
  Presentations	...	...

  The last column ("hours to go till end of project") should contain the hours that are left according to the reported status of the project: an up-to-date reliable estimate, not just the original number of planned hours minus the hours spent.

• The SR, AD, DD and TR sections of the Software Project Management Plan (SPMP) will be combined into one document to avoid overlap.

• Peer evaluations will take place halfway and at the end of the project.
  Peer Evaluation Forms are available.

Verification and Validation

• To save preparation time, the reviews (UR/R, SR/R, AD/R, DD/R) are organized as walkthroughs, rather than as technical reviews.
  The advisor decides whether a document is acceptable for the final ("external") review.
  There are checklists for requirements reviews and design reviews.
  Review results and metrics (like number and severity of defects) should be sent to senior management.

  Customer or advisor sign for the acceptance of the reviewed product documents.
  The customer signs for the URD, SRD, SUM, SVVP/AT.

  The customer is involved in the external review of URD, SRD, SUM, and SVVP/AT.
  The advisor is involved in the external review of all product documents.

Coding Phase

• The code is delivered in six increments of one week.

• At the start of each increment, an increment feature list is made containing all features that will be delivered at the end of the week.
  The list is preferably in terms of user or software requirements.

• At the beginning of the next week, the working program is delivered to senior management.

• Once delivered, each feature should be stable in the next increments (no regression).

• Project management templates (latex): zip archive.

• Documents of some finished projects:

  bICEPS (2006)	URD	SRD	ADD	DDD	SUM	STD	SPMP	SCMP	SVVP SVVP/UT SVVP/IT SVVP/ST SVVP/AT	SQAP	zip archive
  SPINGRID (2006)	URD	SRD	ADD	DDD	SUM	STD	SPMP	SCMP	SVVP SVVP/UT SVVP/IT SVVP/ST SVVP/AT	SQAP	zip archive
  Horus (2007)	URD	SRD	ADD	DDD	SUM	STD	SPMP	SCMP	SVVP SVVP/UT SVVP/IT SVVP/ST SVVP/AT	SQAP	zip archive
  QIS (2010)	URD	SRD	ADD	DDD	SUM	STD	SPMP	SCMP	SVVP SVVP/UT SVVP/IT SVVP/ST SVVP/AT	SQAP	zip archive