P050401a: ODMref1.0 Plan Update

A running diary and job jar of work items and notes on the ODMref 1.0 Plan Update

Status	Date	Description





	2005-05-14	I'm not sure that this folio fits, and I am unclear how it can fit into rolling development and original tracking. There's more than one plan update (we've been adjusting as we go and there was an exception review and update on 2005-05-11). This needs a different structure that is easier to maintain and that can also be followed. It looks like it should fit into a progression. [dh:2005-05-14 Oops! This was a project, and it needs to be marked as completed when it was completed. That's all that is needed. Make sure that happened. See what's needed to declare this completed. It happened on some plan. Update the version and history (which see) in doing that.]
done	2005-05-14	Double-check the folio cover to make sure that it presents all right.
done 2005-05-14	2005-05-13	Correct the last description in this column to be left-adjusted, not centered.
	2005-04-09	Go live with what we've got and review all planning job jars afterwards for follow-on tasks.
done 2005-04-09	2005-04-08	Get some simple sensible tracking to get us going.
	2005-04-08	Review the objectives and conditions of satisfaction for more measurability and add an account for this at some point during a review activity. For now, allow the plan update project to be completed and work other elements in as we march along.
done	2005-04-08	Add a TROSTing folder to cover those tasks related to TROSTing the ODMref 1.0 development and implementation.
	2005-04-08	Review the engagement task folios for form and for wave-edge expansion.
done	2005-04-08	Add /envision under ODMref 1.0 and introduce a task folio for the envisioning activity.
done	2005-04-08	Add Tools folder for the half of tools identification that matters here. (This is the project part and not the tools development. Not sure what the split is between ODMA /dev/tools but I think it is rather different.
done	2005-04-08	Add conditions of satisfaction for what least must be here to be done.
	2005-04-07	Add the identification of outputs to the related-material block in project summary tables. Or else identify inputs and outputs in adjacent columns of a new row. Figure it out. [dh:2005-04-08 I am using the new row above the assignment info. I am also adding conditions of satisfaction.] Do for P050401, P050402, P050403, P050404, P050405
done 2005-04-07	2005-04-06	There needs to be a work breakdown folio, including material from the TROST Specification level that is about ODMref 1.0.
	2005-04-06	The references to TROSTing in the materials here need to be linked to targets on that site. That should be an activity there, too, to make links as there is linkable material.
done 2005-04-06	2005-04-05	The ODMref 1.0 announcement and ODMref 1.0 engagement should be managed with project folios here. There can be an /engage activity folder, since it is so important. Put them there.
done 2005-04-09	2005-04-05	Provide a context for the project somewhere, that shows the stages and the progression of the ODMref 1.0 planning as an embedded activity of the TROST Pilot Project.
done 2005-04-09	2005-04-05	Create a tracking activity for ODMref, starting now, and have it include the point of departure and how we are proceeding. There needs to be some recovery for the earlier activities: Identification of Tools and the ODMref Mitigation (which has a project). There is also the gathering of ODMA materials, etc.
done 2005-04-06	2005-04-05	Make sure there is a place for the introduction of CVS and other activities under SourceForge. These may go under the ODMref engagement task identified in the TROST communication plan.
	2005-04-05	Review the 03-07 Journal and bring any items noticed there under ODMA.info in appropriate places.
	2005-04-05	On the identification of tools for this part, I need to separate the different kinds. There are confirmation and assessment tools, and there are development and testing tools. Some tools may be used in multiple categories, but the information about the specific usage, and the prerequisites, may differ.
done	2005-04-05	Create this page with the Lab Notebook style