dbmetrics reeks

Ketenbeheer in de praktijk € 51,45
Ketenbeheer in de praktijk

Dit boek definieert ketenbeheer als de verzameling van beheerprocessen en beheerproducten die ervoor zorgdragen dat een set bij elkaar horende en aansluitende bedrijfsprocessen als geheel efficiënt en effectief functioneren.Ketenbeheer is een fenomeen dat vele gezichten heeft. Voor de een is het een aaneenschakeling van informatiesystemen, voor de ander een samenhangend geheel van beheerprocessen of bedrijfsprocessen. Dit boek definieert ketenbeheer als de verzameling van beheerprocessen en beheerproducten die ervoor zorgdragen dat een set bij elkaar horende en aansluitende bedrijfsprocessen als geheel efficiënt en effectief functioneren. Hierbij worden drie ketens onderkend: op beheerprocesniveau, informatiesysteemniveau en bedrijfsprocesniveau. De nadruk ligt op het verkrijgen van synergie door het zoveel mogelijk uitwisselen van statusinformatie over de ketens die zich op deze drie niveaus bevinden: integraal ketenbeheer. Ketenbesturing is nog jong. Dit boek geeft in een vogelvlucht de stand van zaken weer aan de hand van een onderzoek, in opdracht van Qforce door de auteur uitgevoerd, naar de functionaliteit van vier innovatieve leveranciers van tools voor ketenbeheer met elk hun eigen specialisatie. Tegelijkertijd is het boek een bruikbare hands-on, als aanvulling op de managementtheorieën over dit onderwerp. Een goed beeld van ketenbeheer in de praktijk is de in dit boek opgenomen casus waarin Fortis Nederland ketens monitort. Deze organisatie heeft ook een praktijkvoorbeeld gegeven van het inrichten van een ketenbeheerorganisatie. Dit eerste werk in Nederland over integraal ketenbeheer is een onmisbaar hulpmiddel bij de integratie van bedrijfs- en beheerprocessen.

Agile Design Best Practices € 35,95
Agile Design Best Practices

With the Agile approach to design, you have a powerful tool in your hands to get grip on an Agile development project.In recent years the need for a design for an information system has been questioned by many organizations. The classic justification for bundling information about an information system and thinking upfront about the contours of the information system to be realized are seen as obsolete by the Agile way of working and the idea of ‘the three amigo development strategy’. Capturing the design of the information system (emerging design) during an Agile project is also omitted by many organizations. However, a design is also essential for safeguarding the transfer of knowledge, support for service management and compliance with laws and regulations. Elements that guarantee the continuity of an organization. This book describes how an Agile design can be implemented so that both the elements for business continuity and flexibility are guaranteed. The design is divided into the following views: business, solution, design, requirements, test and code view. The Agile design encompasses the entire lifecycle of the information system. The first three views are completed based on modern design techniques such as value stream mapping and use cases. However, the emphasis of the effective use of an Agile design lies in the realization of the information system, namely by integrating the Agile design, the test driven development and continuous documentation. With the Agile approach to design, you have a powerful tool in your hands to get grip on an Agile development project.

DevOps Architecture € 51,45
DevOps Architecture

This work on DevOps architecture is an indispensable tool in the design and implementation of a DevOps service organization.The world of system development is changing at a rapid pace. Development (Dev) and Operations (Ops) are being integrated more and more so that solutions can be offered to customers faster and with better quality. The question is how within this new view of DevOps there is room for Agile architecture. This book provides an answer to this question by giving many examples of architectural principles and models that give direction to the design and operation of a DevOps organization. Throughout the book an explanation is given as much as possible per paragraph based on an imaginary Assuritas company. This book consists of various parts, which makes the book modular. So, it does not have to be read from A to Z. After the brief outline of the case company an explanation of how to construct the DevOps organization from an architectural perspective is given. The DevOps service management is then discussed. Both aspects are made clear on the basis of the case company. After explaining how the Dev and Ops roles can be integrated, two useful assessment tools to determine the maturity of DevOps are described. The book concludes with a case in which the choice for an Agile documentation is made based on architectural principles and models. This work on DevOps architecture is an indispensable tool in the design and implementation of a DevOps service organization.

DevOps Assessments € 35,95
DevOps Assessments

This assessment book is an excellent mirror for every DevOps team that wants to quickly obtain a complete picture of the DevOps best practices to be addressed.DevOps teams organize themselves and improve the Development (Dev) and Operations (Ops) aspects that are still underexposed. On the other hand, DevOps teams share knowledge and skills with other DevOps teams so that they reinforce each other. This book provides a tool to make the DevOps teams aware of where they stand in terms of maturity and the next steps they can take to develop. To this end, this book offers two assessments. The first assessment is the DevOps Cube assessment based on ‘The Three Ways” by Gene Kim. The second assessment is based on Continuous Everything whereby all aspects of DevOps are measured using the CMMI model. The DevOps Cube assessment is based on the idea that DevOps can be viewed from six different perspectives. Each gives a specific picture of the design of the DevOps philosophy. The fronts of the cube are based on “The Three Ways”: “Flow”, “Feedback” and “Continuous Learning”, the back of the cube include: “Governance”, “Pipeline” and “QA”. The Continuous Everything assessment comprises six lists of questions that make the DevOps maturity measurable on five levels. The following dimensions are included: “Continuous Integration”, “Continuous Delivery”, “Continuous Testing”, “Continuous Monitoring”, “Continuous Documentation”, and “Continuous Learning”. This assessment book is an excellent mirror for every DevOps team that wants to quickly obtain a complete picture of the DevOps best practices to be addressed.

DevOps Best Practices Pocket Guide € 20,95
DevOps Best Practices Pocket Guide

DevOps Best Practices - POCKET GUIDE In recent years, many organisations have experienced the benefits of using Agile approaches such as Scrum and Kanban. The software is delivered faster whilst quality increases and cost decrease. The fact that many organisations that applied the Agile approach did not take into account the traditional service management techniques, in terms of information management, application management and infrastructure management, is a major disadvantage. The solution to this problem has been found in the Dev (Development) Ops (Operations) approach. Both worlds are merged into one team, thus sharing the knowledge and skills. This book is about sharing knowledge on how DevOps teams work together. For each aspect of the DevOps process best practices are given in 30 separate articles. The covered aspects are: Plan, Code, Build, Test, Release, Deply, Operate and Monitor. Each article starts with the definition of the specifically used terms and one or more concepts. The body of each article is kept simple, short and easy to read.

Agile Service Management with Scrum Researched € 51,45
Agile Service Management with Scrum Researched

This book is the report about the research of the collaboration of Agile software development and service management processes in practice.Many companies are starting to apply Agile software development using Scrum or Kanban or have already implemented the new development process. Sooner or later the question arises how this development process relates to the service management processes. The book “Agile Service Management with Scrum” has already addressed this interface and a number of risks per service management process have been identified. Countermeasures that can be taken are also defined. In a research at ten organisations these risks were presented, and they were asked how they deal with these risks. The research included the investigation into which Agile aspects are applied and in particular those of Scrum or Kanban. Finally, each organization has carried out a maturity assessment for both the Agile development process and the change management process. This book is the report about the research of the collaboration of Agile software development and service management processes in practice. The target group of this book includes all parties involved in the application of Agile software development and who would like to know how colleagues have shaped this crucial interface for successful service provision. In this book a short description is given of each organization about how the Agile development process has been designed.

Agile Service Management with Scrum € 51,45
Agile Service Management with Scrum

This book first defines the risk areas when implementing Scrum and Kanban. The content of Agile service management is described at both the organizational- as the process level.Using Agile software development is taking off. The terms Scrum and Kanban are already common to many organizations. Agile software development needs different requirements for the management of software. Many organizations are mastering this new challenge. In particular, the interaction between the Scrum development process and the support of the software that the Scrum development process has produced, is an important aspect. This book specifically discusses this interaction. Examples of topics that are discussed here are the service portfolio, SLAs and the handling of incidents and change requests. This book first defines the risk areas when implementing Scrum and Kanban. Next the various Agile terms and concepts are discussed. The content of Agile service management is described at both the organizational- as the process level. The relevant risks are specified for each service management process. In addition, the implementation of each process within the context of scrum is indicated. This book is just one of the practical reads of best practices that have been published by this author in a series of publications.

SLA Templates - Pocket Guide € 22,95
SLA Templates - Pocket Guide

This pocket guide gives both a template and an explanation for this template for all common service level management documents.Most important in providing a service is customer satisfaction with the delivered performance. Resulting from this satisfaction, the supplier will benefit from repurchases, market promotions and recurring revenue. But as a result of this customer satisfaction, perhaps the most important benefit for the supplier is the drive for his employees to enhance their knowledge and skills, in order to satisfy even more customers. This pocket guide describes the Service Level Agreement templates needed, in order to meet customer service level requirements and gives both a template and an explanation for this template for all common service level management documents. The following templates ae included in this pocket guide: • Service Level Agreement (SLA) • Underpinning Contract (UC) • Operational Level Agreement (OLA) • Document Agreements and Procedures (DAP) • Service Catalogue • External Spec Sheet (ESS) • Internal Spec Sheet (ISS) • Service Quality Plan (SQP) • Service Improvements Program (SQP)

SLA Templates € 35,95
SLA Templates

Most important in providing a service is customer satisfaction with the delivered performance. Resulting from this satisfaction, the supplier will benefit from repurchases, market promotions and recurring revenue. But as a result of this customer satisfaction, perhaps the most important benefit for de supplier is the drive for his employees to enhance their knowledge and skills, in order to satisfy even more customers. This book describes the Service Level Agreement templates needed, in order to meet customer service level requirements. This book gives booth a template and an explanation for this template for all common service level management documents.Most important in providing a service is customer satisfaction with the delivered performance. Resulting from this satisfaction, the supplier will benefit from repurchases, market promotions and recurring revenue. But as a result of this customer satisfaction, perhaps the most important benefit for de supplier is the drive for his employees to enhance their knowledge and skills, in order to satisfy even more customers. This book describes the Service Level Agreement templates needed, in order to meet customer service level requirements. This book gives booth a template and an explanation for this template for all common service level management documents. The following templates are included in this book: • Service Level Agreement (SLA) • Underpinning Contract (UC) • Operational Level Agreement (OLA) • Document Agreement and Procedures (DAP) • Document Financial Agreements (DFA) • Service Cataloque • External Spec Sheets (ESS) • Internal Spec Sheers (ISS) • Service Quality Plan (SQP) • Service Improvement Program (SQP)

DevOps Best Practices € 51,45
DevOps Best Practices

This book is about sharing knowledge on how DevOps teams work together. For each aspect of the DevOps process best practices are given in 30 separate articles. The covered aspects are: Plan, Code, Build, Test, Release, Deploy, Operate and Monitor. Each article starts with the definition of the specifically used terms and one or more concepts. The body of each article is kept simple, short en easy to read.In recent years, many organisations have experienced the benefits of using Agile approaches such as Scrum and Kanban. The software is delivered faster whilst quality increases and costs decrease. The fact that many organisations that applied the Agile approach did not take into account the traditional service management techniques, in terms of information management, application management and infrastructure management, is a major disadvantage. The solutions to this problem has been found in the Dev (Development) Ops (Operations) approach. Both worlds are merged into one team, thus sharing the knowledge and skills.