Difference between revisions of "Infrastructure SD Agenda item list"
| Line 7: | Line 7: | ||
=== Project Approval Process === | === Project Approval Process === | ||
| + | *The project approval process was updated to reflect the new organizational structure | ||
| + | *Charlie McCay would like to add some sort of capability to publish the scope statements during the approval process | ||
[[Image:Project_Initiation_and_Approval_draft_V.2.gif]] | [[Image:Project_Initiation_and_Approval_draft_V.2.gif]] | ||
Revision as of 02:12, 30 October 2007
Contents
Future Agenda Items
Document and approve the current rules and processes for harmonization
Project Approval Process
- The project approval process was updated to reflect the new organizational structure
- Charlie McCay would like to add some sort of capability to publish the scope statements during the approval process
Infrastructure Release
Please could the SD discuss the positioning of the various infrastructure revision projects that are underway. At the WGM I was tasked by INM TC and ITS SIG to raise this issue. There are a number of infrastructure improvements currently being worked on, that are likely to be published as DSTU in the next 6 months. It would seem sensible to promote these as a combined "major release", that is made normative and marketed as a single platform enhancement. Maybe other product lines could also be timed to be released at the same time.
So far the technical work on what changes are worthwhile is being done, learning from over five years of implementation experience -- but the work on how to position those changes in the marketplace has not been done
