Filters

2016 - 20173

More filters

20193
Reset filters

Settings

Author: Strobel, Sven × Subject: collaborative working ×

Search Results

Now showing 1 - 3 of 3
  • Thumbnail Image
    Item
    Workflow management of sprints and software tests: Coordination, consensus, and cooperation in the enterprise wiki of the German National Library of Science and Technology
    (New York, NY : International Institute for Science, Technology and Education, 2016) Strobel, Sven
    This paper discusses the workflow management of sprints and software tests at the German National Library of Science and Technology (TIB) and pays special attention to how the enterprise wiki can be used to support forms of group interaction such as coordination, consensus (finding), and cooperation. The enterprise wiki helps to organize who has to do what by when (coordination). At TIB, it essentially supports the project managers in planning, organizing, and controlling the workflows of the project. Moreover, it facilitates and accelerates the decision making within the team (consensus) and helps the team members to share knowledge and develop ideas by editing common documents (cooperation). The workflows for sprints and software tests as well as their management are illustrated by the example of the TIB project relaunching the TIB|AV-Portal. The paper argues that establishing workflows in the wiki makes collaborative working more efficient and easier to handle. This is shown with respect to the team’s coordination, consensus finding, and cooperation in the project. The paper also specifies the TIB concepts for sprints – a method to develop concepts collaboratively – and software tests. The topic discussed here relates to subject areas such as knowledge management and project management and, more specifically, to collaborative working and computer-supported cooperative work.
  • Thumbnail Image
    Item
    Collaborative Working and Knowledge Sharing in the Enterprise Wiki: How Teams Develop Concepts Using Sprints
    (Den Haag : IFLA, 2017) Strobel, Sven
    Wikis have long been established in the library sector. Yet, librarians tend to only use them when compiling lists of links or files. The Competence Centre for Non-Textual Materials (KNM) at the German National Library of Science and Technology (TIB) rather uses the wiki as a working platform for collaboration, knowledge sharing, and management of tasks and workflows. The KNM team defined an agile sprint workflow and implemented it in the wiki in order to develop requirements specifications for the TIB AV-Portal. The KNM method combines a wiki-based management of workflows with agile methods. This method accelerates complex decision making, structures and standardises the processes, intensifies collaboration, and documents everything in the wiki. The paper presents the execution, roles and artefacts of the KNM sprint workflow. It also shows what the KNM method has in common with Scrum and how it differs from it. The KNM method is not limited to software development. It can be applied to concepts other than requirements specifications, such as research applications, guidelines or manuals.
  • Thumbnail Image
    Item
    Developing the web portals of the German National Library of Science and Technology: Tools and workflows used
    (ISAST, 2016) Strobel, Sven
    Teams working on the development of software systems use certain tools and workflows of product and knowledge management. These tools and workflows help them plan, monitor and control the product at all stages of the product lifecycle as well as capture, develop and share project-related knowledge. This paper discusses the tools and workflows development teams of the German National Library of Science and Technology (TIB) use when developing the web portals. The use case illustrated here is a project, in which the interaction concept and screen design of the video portal of TIB (TIB|AV-Portal) had to be adapted to the new look and feel of the main portal (TIB-Portal). In the course of the project, the team gathered and structured preliminary requirements in the enterprise wiki, created an Axure user interface prototype, evaluated the prototype and specified the requirements using sprints from the Scrum framework, commissioned external screen designers and software developers to create a new screen design based on the prototype and implement the requirements, tested the implementations in a collaborative workflow and approved their deployment after debugging.