The Sprint Process for this Workshop

1. The Sprint Process for this Workshop

2. Sprint Process • This workshop will be using a process borrowed from the GSIM Sprints • Several attendees here were also involved in that work • The term “Sprint” is taken from the Agile style of software development methodologies • The key idea is that a Sprint is self-organizing • Priorities are adjusted on an on-going basis • The group is “self-organizing” • Frequent plenaries and flexible assignments of participants

3. “Sprintmeisters” • There will be a small number of individuals who will acts as facilitators • Bill Block is the main facilitator • Johann Finn will stand in for him today (Bill arives late) • The organizers will also act in this capacity • If you have concerns of any type, contact a facilitator • Facilitators are there to make sure that issues and concerns are adressed, within the framework of the workshop priorities

4. Organization of Groups • Groups will be organized and re-organized based on the perceived rate of progress and priorities of the deliverables • You may be asked to join a specific group or work on a specific deliverable based on your skills and knowledge • This typically happens after a plenary, which occur in the morning each day, and after lunch each day, and may be called more frequently if needed

5. The Soap Box • Each morning, we will allow up to four presentations of no more than 3 minutes in length • These may be brilliant ideas you had while drinking in the wine cellar the preceding evening • These may be rants about specific issues • They may be a combination of the above, or other things… • If you want to do a soap-box presentation, contact a facilitator before the morning plenary starts

6. The “Parking Lot” • We will have a pad of paper available in the main room at all times where participants may suggest ideas for discussion • Just put a brief outline of the idea (a bullet point) on the list • Talk to the facilitator – they will write it up! • This helps us to make sure we don’t lose ideas during the sometimes chaotic work going on within the Sprint

7. Deliverables 1. Completed model templates for the 4 identified functional areas 2. First draft of common model documentation based on the completed templates 3. Draft design and specification of production process 4. Draft design principles for DDI work products 5. Documentation of DDI Alliance workflows 6. Draft XML syntax binding specification 7. Draft RDF syntax binding specification 8. Draft business rules specification for model transformations 9. Documentation of modeling style (includes UML profile)

8. Notes • The deliverables from DDI will be better designed to allow granular review and release • Some outputs from this workshop may be released sooner than you might expect • We are using a “core-plus-extensions” style, so core has to exist first (the functional areas identified for this workshop) • Content modeling has been de-coupled from technical production and binding for this workshop • We will present the modeling template (Word) • We will be modeling whatever content is generated during the workshop to validate modeling style and bindings

9. Modeling Template • For each object, we will need to create a full description • This is captured (for now) in a Word template • There will be a document per object • There are a lot of objects!