Prozesse für Publication Management. T. Grün

Transcription

1 Prozesse für Publication Management T. Grün escidoc Partizipation, Klausurtagung Berlin, 20./21. Februar 2006 V0.7

2 Agenda Weiterer Prozess Publications Management Vorstellung Projektplan Vorstellung Prozess Change Request Vorstellung der weiteren Zusammenarbeit mit Piloten Vorstellung der Zielsetzungen für das Meeting Anfang April 2

3 Agenda Weiterer Prozess Publications Management Vorstellung Projektplan Vorstellung Prozess Change Request Vorstellung der weiteren Zusammenarbeit mit Piloten Vorstellung der Zielsetzungen für das Meeting Anfang April 3

4 1. Usage Scenarios Publication Manager Scholarly Workbench 2. Mapping against requirements Approach Steering Committee Decision 12/ Identified Use Cases Adv. Board escidoc Decision 13/01/ Functional Design 4. Validation of Requirements with Pilots Priorization Completed Completed Completed Started Started Develop high level architecture concept Develop platform decision Develop detailed architecture concept Completed Completed Started 4

5 Release Definition Fixed Milestones for escidoc For Scholarly Workbench (SWB) a showcase will be presented during the Digitale Welten Conference in September 2006 For Publications Management the first version will be released at the end of 2006 Process of Release Definition Priorization of Requirements Estimation of Effort Definition of Scope of individual releases (process may take several iterations) 5

6 Assumptions for Time Schedule 2006 escidoc team is able to produce a stable framework for SWB Showcase and PubMan Basic within 4,5 months. Until mid march the functionality for Publication Management (Basic Functionality) and Scholarly Workbench (Showcase) must be fixed. Coordination with the pilots will be defined in the Participation Concept. Utilization of parallel work streams and building upon work in progress speeds up development, while increasing risk. The SWB Showcase realizes selected requirements out of the set of requirements for SWB productive release. This could be: Management a Collection Upload of Content Items Search functionality Integration of Language Technology The Publication Management (Basic Functionality) Release implements requirements, which are currently supported by edoc. 6

7 escidoc Time Schedule 2006 A B Priorization and Effort Estimates 1-6 Sign-off Jan Feb Mär Apr Mai Jun Jul Aug Sep Okt Nov Dez Scholarly Workbench Publication Management Planning of the specification phase Ramp up Phase Participation Concept and Coordination with Pilots 1 A SWB (Showcase) 3 Detailed Specification (Showcase & prod. release) Design Build Test Planning of the implementation B 4 Detailed Specification Publication Management (Basic Functionality) (Basic & enhanced functionality) Design Build Test 2 Participation Concept and Coordination with Pilots 3 months Piloting Application Architecture Integration Framework Coordination of Interfaces and Develop. Env. Specify and develop technical architecture Planning of the architecture implementation Application Architecture D B T Update of Interfaces and Test Preparation Framework (SWB) D B T Framework (PM Basic) D B T Application Architecture Support Joint Testing (SWB & Publication Management) 5 6 7

8 Agenda Weiterer Prozess Publications Management Vorstellung Projektplan Vorstellung Prozess Change Request Vorstellung der weiteren Zusammenarbeit mit Piloten Vorstellung der Zielsetzungen für das Meeting Anfang April 8

9 Purpose Issue Management and Defect Tracking Update according to customization for pilots Need to keep track of Issues and Enhancements during Design, Build and Test Defects during Test Need to introduce and enforce a process for Enhancement Decisions Defect Fixing A detailed introduction to the Issue Management and Defect Tracking Tool and procedures will be given during the individual meetings between Pilots and ZIM. A compehensive manual will also be provided. 9

10 The Issue Lifecycle Status and Resolutions During its lifecycle, an issue changes status For resolved, verified or closed issues, an issue has several possible resolutions 10

11 Bugzilla Presentation Screenshot illustrative - requires updating Standard Process Report new Issue Solve Issue Verify Solution Close Issue Saved Searches Suggested Reports 11

12 Startscreen (after login) Screenshot illustrative - requires updating 12

13 Create new Issue Screenshot illustrative - requires updating 13

14 Search Issue Screenshot illustrative - requires updating 14

15 Agenda Weiterer Prozess Publications Management Vorstellung Projektplan Vorstellung Prozess Change Request Vorstellung der weiteren Zusammenarbeit mit Piloten Vorstellung der Zielsetzungen für das Meeting Anfang April 15

16 Development of Service bases on Continuous Input of Pilots Pilot Institutes Feedback / Validation / Functional Input / Sign-Offs ZIM escidoc Project Team Identification of Requirements and Creation of Usage Scenarios Detailed Requirements Release Definition Detailed Design/ Specification Development, Testing, Deployment Operations Current Status Transition Point April

17 Draft Plan: Participation for PubMan Validation of Concepts Validation of Scope of Service and Functionality on the basis of Usage Scenarios and conceptual papers 26 January 2006 Kick-off Meeting Objectives: Validation of Service Description Create understanding of pilots for fundamental concepts Present list of features and functionalities setup workgroups February 2006 Klausurtagung - Objectives Detailed discussion of Usage Scenarios, concepts and functionalities with respective workgroups March 2006 Visit of individual insitutes to discuss and validate USCs and detailed requirements 17 Transition Point 4-5 April 2006 (planned) final Validation Sign-off of Service Description, incl. concepts and features Development Final discussion of results Sign-off of priorized and extended list of features and functionalities Testing

18 Agenda Weiterer Prozess Publications Management Vorstellung Projektplan Vorstellung Prozess Change Request Vorstellung der weiteren Zusammenarbeit mit Piloten Vorstellung der Zielsetzungen für das Meeting Anfang April 18

19 Transition Point 4/5 April for PubMan Aproach: During March 2006, escidoc project offers to visit all Pilot Institutes for a detailed discussion, during which feedback on Usage Scenarios and Requirements can be provided. Target: By 4/5 April the following objectives should be achieved: Sign-off of Service Description, incl. concepts and features Sign-off of priorized and list of features and functionalities Define Release Plan 19

20 BACKUP 20

21 KONKRETISIEREN Definition of Workgroups, Dates, Communication Focal point for each Pilot Which points are critical to my Institute? Where can I or my colleagues contribute? Have we made positive or negative experiences? In which multi-institutional Workgroup can I contribute? Possible Dates in February/March Visit of Institutes (Attendance contact person, rest of pilot group) Multi-institutional Workgroup (logistics, one-day Workshop) Communication Mailing list Webpage: Protected access - ID: escidoc-pilot; PW: p!lotescidoc Dates, Agenda, Protocols, Material, Overview pilots planned: online-glossary 21

22 Issue Reporter New Issue Team member Issue Resolver The Issue Lifecycle Process 1 / 2 escidoc Issue Management Process Functional Issue Admin Reviewer - Team Lead, Project Mgt or Program Mgt Identify/Enter Issue Check Issue for confirmation Confirm as new issue Not confirmed-no new issue - DUPLICATE - WONTFIX - WORKSFORME - INVALID - REMIND - LATER Check Severity Severity Level Blocker, Critical, Major or Enhancement Check Issue Severity Lvl Normal, Minor, Trivial Assign Issue Further escalation 22 No further escalation

23 The Issue Lifecycle Process 2 / 2 No further escalation Resolve Issue Check Issue Check Issue (Higher Hierarchy Lvl) Mark as resolved Delegate for final review - FIXED - WONTFIX - INVALID - WORKSFORME Solution satisfactory Verifiy Solution Solution non-satisfactory - REOPEN Delegate Assignm ent Drop Issue: - WONTFIX - WORKSFORME - INVALID Directly Assign Issue Direct closing Assign Issue Verify Solution Close issue Solution non-satisfactory Solution satisfactory Close issue CLOSED 23