PAHMA Deployment Questions and Concerns

Questions

What are the latest release date projections? (The roadmap is dateless and the release dates are off by at least a month.)
Where do we stand on having a PAHMA slice and tenant?
What's the status of SVN?
Who should do which changes required for PAHMA customizations?
What are the plans for domain customizations? (Would like to break up PAHMA vs. Anthro customizations sooner rather than later)
What about "customizations" that are really changes that should be made to Core? (e.g., ISO 639-2 codes for languages)
What's the best way to get from mappings to migration? (i.e., which ETL tool(s) should be used, and who should do what?)
Will there be ETL tool familiarization/best practice guidelines and/or training?
Does a 3-version deployment (v1.8, v1.11, v2.0) sound reasonable?
How long will the real migration take from TMS to CollectionSpace? (Will have to lock down TMS from start of migration until release of working v2.0.)
Are there concerns about the PAHMA deployment timetable?

Timetable

Date	Milestone	notes
now–mid-July, 2011	Jiras created and assigned for all v1.8 customization work	who should do what work?
mid–late July, 2011	Work on closing assigned Jiras
late July, 2011	Deploy a partially customized version of CollectionSpace 1.8	emphasis will be on functionality and customizations. includes: * custom relabeling of fields on Cataloging UI * customization of existing (or creation of custom) controlled vocabularies for Cataloging * customization of existing (or creation of custom) authorities for Cataloging * creation of custom fields for Cataloging * custom placement of core and custom fields on Cataloging UI
July 26-29, 2011	First of two sprints to finish data mapping
August 9, 2011	Director has requested staff-wide demonstration of PAHMA-CSpace 1.8	45-minute presentation
August 16-19, 2011	Second of two sprints to finish data mapping
mid-August, 2011 to September, 2011	User testing of customized v1.8
September, 2011	Further customization of 1.8 according to outcome of user testing	iterative adjustments will be made according to user feedback
late October, 2011	Deploy a more fully customized version of CollectionSpace (based on v1.11	includes: * all mapped data * additional required customizations identified by user testing cycles * majority of remaining UI customizations * creation of custom procedures (e.g., NAGPRA Compliance Information)
November, 2011	User training for Museum staff	includes: * continuing user testing, feedback, and tweaking
mid-December, 2011	Deploy CollectionSpace 2.0	Final pre-migration testing and tweaking
mid-late December, 2011	Full migration of PAHMA data to CollectionSpace 2.0	includes: * lock-down of TMS (no new data)