From Bram Stoker Award-nominated author, Ross Jeffery, comes a new horror novel focused on a father's journey to find his missing daughter.Henry's daughter was fourteen when she went missing and he's been burying pieces of her ever since. Each totem Henry places in the ground is a memento mori of his daughter's life that he's desperate to forget. Surviving with the guilt of his possible role in her disappearance, and more than likely her death, Henry is unable to move forward.All is not lost though, when a stranger appears at Henry's grief counseling group with a dark and disturbing proposition for him. "Have you ever tried to make contact with your daughter, to see if she's passed?" What follows is a tale of deception and possession like no other. With thriller pacing and words that bleed off the page, Ross Jeffery delivers a terrifying nightmare of how grief can climb inside and bury itself in the human heart.

Software effort estimation is one of the oldest and most important problems in software project management, and thus today there are a large number of models, each with its own unique strengths and weaknesses in general, and even more importantly, in relation to the environment and context in which it is to be applied. Trendowicz and Jeffery present a comprehensive look at the principles of software effort estimation and support software practitioners in systematically selecting and applying the most suitable effort estimation approach. Their book not only presents what approach to take and how to apply and improve it, but also explains why certain approaches should be used in specific project situations. Moreover, it explains popular estimation methods, summarizes estimation best-practices, and provides guidelines for continuously improving estimation capability. Additionally, the book offers invaluable insights into project management in general, discussing issues including project trade-offs, risk assessment, and organizational learning. Overall, the authors deliver an essential reference work for software practitioners responsible for software effort estimation and planning in their daily work and who want to improve their estimation skills. At the same time, for lecturers and students the book can serve as the basis of a course in software processes, software estimation, or project management.

Software effort estimation is one of the oldest and most important problems in software project management, and thus today there are a large number of models, each with its own unique strengths and weaknesses in general, and even more importantly, in relation to the environment and context in which it is to be applied.

Trendowicz and Jeffery present a comprehensive look at the principles of software effort estimation and support software practitioners in systematically selecting and applying the most suitable effort estimation approach. Their book not only presents "what" approach to take and "how" to apply and improve it, but also explains "why" certain approaches should be used in specific project situations. Moreover, it explains popular estimation methods, summarizes estimation best-practices, and provides guidelines for continuously improving estimation capability. Additionally, the book offers invaluable insights into project management in general, discussing issues including project trade-offs, risk assessment, and organizational learning.

Overall, the authors deliver an essential reference work for software practitioners responsible for software effort estimation and planning in their daily work and who want to improve their estimation skills. At the same time, for lecturers and students the book can serve as the basis of a course in software processes, software estimation, or project management.

Software development is a complex problem-solving activity with a high level of uncertainty. There are many technical challenges concerning scheduling, cost estimation, reliability, performance, etc, which are further aggravated by weaknesses such as changing requirements, team dynamics, and high staff turnover. Thus the management of knowledge and experience is a key means of systematic software development and process improvement. "Managing Software Engineering Knowledge" illustrates several theoretical examples of this vision and solutions applied to industrial practice. It is structured in four parts addressing the motives for knowledge management, the concepts and models used in knowledge management for software engineering, their application to software engineering, and practical guidelines for managing software engineering knowledge. This book provides a comprehensive overview of the state of the art and best practice in knowledge management applied to software engineering. While researchers and graduate students will benefit from the interdisciplinary approach leading to basic frameworks and methodologies, professional software developers and project managers will also profit from industrial experience reports and practical guidelines.

Software development is a complex problem-solving activity with a high level of uncertainty. There are many technical challenges concerning scheduling, cost estimation, reliability, performance, etc, which are further aggravated by weaknesses such as changing requirements, team dynamics, and high staff turnover. Thus the management of knowledge and experience is a key means of systematic software development and process improvement. "Managing Software Engineering Knowledge" illustrates several theoretical examples of this vision and solutions applied to industrial practice. It is structured in four parts addressing the motives for knowledge management, the concepts and models used in knowledge management for software engineering, their application to software engineering, and practical guidelines for managing software engineering knowledge. This book provides a comprehensive overview of the state of the art and best practice in knowledge management applied to software engineering. While researchers and graduate students will benefit from the interdisciplinary approach leading to basic frameworks and methodologies, professional software developers and project managers will also profit from industrial experience reports and practical guidelines.

Lost Voices is a horror collection of tales left by the wayside: stories recorded on abandoned VHS tapes, horrors found in lifeless towns, voices silenced by the encroaching darkness. Born from a conversation about screwed up stories that'd been rejected from various anthologies, magazines, and callouts for being too weird, freaky, and dark, Lost Voices dredges these lost tales from a past better forgotten. Featuring twelve dark tales by Joseph Sale, Emily Harrison, Christa Wojciechowski and Ross Jeffery, Lost Voices promises to push the boundaries of what horror can be and do. Foreword by Steve Stred.