[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-245347-105":53,"doc-detail-245347-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","agile-working-to-adapt-the-usability-of-swisscovery","Agile working to adapt the usability of swisscovery","","Swiss Library Service Platform (SLSP) continued preparing swisscovery for the Rapido go-live using an agile approach to balance structured delivery with punctual stakeholder requests. The presentation explains how the agile method was organized, what advantages it provided, and where its limitations appear. It also highlights prototyping as a support technique for an iterative development process, enabling parallel view redesign and responsive backlog execution.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/agile-working-to-adapt-the-usability-of-swisscovery/245347/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/agile-working-to-adapt-the-usability-of-swisscovery/245347.png","ImageObject",442,249,{"name":88,"@type":89},"Mason","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-19","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":15},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What goal did SLSP pursue with an agile approach for swisscovery?","Question",{"text":108,"@type":109},"SLSP aimed to prepare swisscovery for the Rapido go-live while supporting both view redesign and timely stakeholder requests through an organized agile structure.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"How was the Agile PrimoVE Customization Project organized in terms of roles?",{"text":113,"@type":109},"It involved a product owner to manage vision, roadmap, backlog prioritization, and releases; a Scrum master to facilitate methodology and remove blockers; and teams of developers plus library-side participants working together on product and UI design.",{"name":115,"@type":106,"acceptedAnswer":116},"Why was prototyping used during the iterative process?",{"text":117,"@type":109},"Prototyping supported iteration by helping validate changes early, making it easier to refine the redesign while meeting evolving requirements.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},245347,1791735688,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":15,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":15},5909887256941,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Agile working to adapt the usability of swisscovery  \nFabiano Fiero, Team leader Discovery  \nNikol Stepan, Data and System Specialist / Business Analyst  \n13.09.2023  \n1  \nSession abstract  \nThanks to good experiences in the past, the Swiss Library Service Platform (SLSP) decided to keep on working with an agile approach for preparing its view (swisscovery) for the golive of Rapido.  \nThis presentation aims to show how this agile approach was structured, its advantages and its limits, and how this allowed the team to both work on the re-design of the view and, atthe same time, fulfill the stakeholders’ punctual requests.  \nThe speakers will also describe the benefits of the method of prototyping to support the iterative process.  \nOverview  \n1. Introduction  \n2. The Agile PrimoVE Customization Project  \n3. Prototyping to support the iterative process  \n4. Conclusions  \n5. Questions  \n1. Introduction  \nSLSP and swisscovery  \nNational platform bringing together the academic information in Switzerland  \nSLSP runs the national library platform  \nLaunch of swisscovery in December 2020  \nOver 490 affiliated libraries in 31 IZs  \nSLSP and swisscovery  \n[swisscovery.slsp.ch](swisscovery.slsp.ch)  \nAgile projects  \n• Agile/traditional project management at SLSP depending on the project scope and organisational context  \n• 2021, shortly after go live of swisscovery: Agile Primo VE Customization Project (APC)  \n• discovery configurations (features, local fields for display and search) 3 times per year after decision process and definition of SLSP standard settings and according services  \n• Continuation oftheAPC in 2022 and 2023  \n2. The Agile PrimoVE Customization Project  \nContext  \nBefore the APC:  \n• „In house“ management: collection of requirements and attempt to fix them  \n• Irregular and time-consuming updates ofthe swisscovery and the central package  \n• All pressure and responsibility on a few people  \nRoles and Composition  \n3-4 people working for SLSP 3-4 people working in libraries  \nProduct owner  \nRepresentative of the  \nstakeholders and customers  \n• Define the product vision and manage stakeholders  \n• Manage the product roadmap and prioritize the backlog  \n• Release management  \nTeam  \nDevelopers  \n• Build the product: Programming, testing, debugging the product  \n• Design the product and its user interface  \nScrum master  \nResponsible for the implementation of the methodology  \n• Facilitate the scrum project management  \n• Ensuring the team works together to achieve their goals  \n• Remove blockers for the team","cbCaiu8P4mnK1WCk","https://ap.wps.com/l/cbCaiu8P4mnK1WCk","pdf",2418944,34,"English","# Introduction\n# The Agile PrimoVE Customization Project\n# Prototyping to support the iterative process\n# Conclusions\n# Questions","[{\"question\":\"What goal did SLSP pursue with an agile approach for swisscovery?\",\"answer\":\"SLSP aimed to prepare swisscovery for the Rapido go-live while supporting both view redesign and timely stakeholder requests through an organized agile structure.\"},{\"question\":\"How was the Agile PrimoVE Customization Project organized in terms of roles?\",\"answer\":\"It involved a product owner to manage vision, roadmap, backlog prioritization, and releases; a Scrum master to facilitate methodology and remove blockers; and teams of developers plus library-side participants working together on product and UI design.\"},{\"question\":\"Why was prototyping used during the iterative process?\",\"answer\":\"Prototyping supported iteration by helping validate changes early, making it easier to refine the redesign while meeting evolving requirements.\"}]","Agile working to adapt the usability of swisscovery | PDF",1789227734]