Differences between revisions 1 and 2
Revision 1 as of 2008-06-26 12:26:09
Size: 4623
Editor: kfc
Comment: Created by the PackagePages action.
Revision 2 as of 2010-03-17 13:08:50
Size: 4623
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
'''KFC''' follows up by adding the Milestones to the Milestone plan. '''''Now done. See ["Milestones"]''''' '''KFC''' follows up by adding the Milestones to the Milestone plan. '''''Now done. See [[Milestones]]'''''
Line 27: Line 27:
The iteration has been put into the ["Iteration4"] page. The iteration has been put into the [[Iteration4]] page.

2007-10-08

1. Suggested Milestones

The suggested milestones were discussed. It was generally agreed that we would be able to reach milestone 2 as suggested in early 2008, but we would be pressed.

Some time was moved from the ingest system to the allocation of working out the meatadata model and contents.

It was agreed to ingest one collection into the DOMS during implementation of that milestone.

The later milestones were agreed upon in the conceptual idea, details were not discussed.

KFC follows up by adding the Milestones to the Milestone plan. Now done. See Milestones

2. Followup on estimation

Some general discussion on the addressed points. These were the conclusions:

  1. We will not estimate any tasks concerning Preservation or Rights before we address the issues directly later in the DOMS development.
  2. The A2.2 task is still unclear. We will reestimate after milestone 2
  3. Task D3.3 had it's estimate by Toke lowered, after we had discussed making end-users write part of the documetnation. Misunderstadning about this task being deprecated was squashed.

3. Planning iteration 4

The iteration was planned in very great detail, down to the point where we allocated time for each half day per person. This was to avoid once again not having the actions done by the end of the iteration.

The iteration has been put into the Iteration4 page.

Note that each action contains when each person should do what. Please check to see it is correct.

The iteration will end for BAM on Monday 2007-10-15, for MKE and TE on 2007-10-16 and for TSH and KFC on 2007-10-17. A final end-of-iteration meeting is scheduled for Thursday 2007-10-18, 9:00, for those who are here.

Iteration 5 starts Monday 2007-10-29.

4. Introduction plan for Jeppe.

It was agreed that a meeting presenting DOMS, the OAIS/preservation book Thomas got as introduction, and the Fedora tutorial, the wiki plus a meeting presenting DOMS would be a good introduction.

We should plan this in more detail when starting iteration 5.

5. Evt.

Nothing

2007-09-24

1. Presentation of results from TDR requirement identification

BAM+KFC presented results of TDR requirement identification. Major highlights:

  • Some requirements adds to existing WBS tasks
  • Important new requirement: Active logical integrity check
  • Inportant new requirements: Extra documentation tasks

Some requirements are out of scope for DOMS, and should only be handled by communicating that a TDR process is needed on the organisational level.

Also, we aim at delaying actual characterisation/migration plans until Planets have results to work with. KFC will ratify this with BJA and BCD.

KFC will update WBS with information from the TDR requirement work as agreed on the meeting.

2. Evaluation of iteration 3

1. Communicating results of TDR requirement analysis

Status DONE

Task C.1 status: 100%

Spent time: KFC 1 md BAM ½ md

2. Add preingesting to test deployment system

Status - missing ½ md. Will be done before ending iteration 3 completely

Task F.5 status: 60%

Spent time: TE: 3½ md. (+ ½ before end). MKE: 1½ md

3. Review of documentation

4. Review of guidelines

(treated as one task)

Status - not OK. Framework ready, no reviews done

Spent time: MKE: 2 md

5. Revise the descriptions of the WBS tasks

Status - Almost updated, missing review, some outstanding issues.

Spent time: TSH: 3 md, KFC: 3 md

6. Review and estimate final WBS tasks

Status - Not started

7. Identify the current stakeholders of the project.

Status - Not started

8. Identify the current risks of the project.

Status - Not started

9. Clarify any issues with IT regarding bit storage.

Status - Not started

10. Releasetest definition

Status - Not started

11. Releasetest

Status - Not started

Conclusions

Spent time is way over estimates.

Reviews are continually delayed.

We need better estimates, and when starting a task we need to raise a flag on bad estimates or lower the ambitions to avoid spending too much time.

We need to push some tasks to next itrations.

3. Iteration 4

Next iteration starts October 5.

Will be a very short iteration of finishing the reviews and doing Stakeholder analysis/Risk analysis

KFC will prepare iteration plan before iteration start.

Minutes/2007-10-08 (last edited 2010-03-17 13:08:50 by localhost)