Annotation Great technology alone is rarely sufficient today to ensure a products success. At Microsoft, scenario-focused engineering is a customer-centric, iterative approach used to design and deliver the deeper experiences and emotional engagement customers demand in new products. In this book, youll discover the proven practices and lessons learned from real-world implementations of this approach, including:Why design matters: Understand a competitive landscape where customers are no longer satisfied by products that are merely useful, but respond instead to products they crave using. What it means to be customer focused: Recognize that you are not the customer, understand customers can have difficulty articulating what they want, and apply techniques that uncover their unspoken needs. How to iterate effectively: Implement a development system that is flexible enough to respond to early and continuous feedback, and enables experimentation with multiple ideas and feedback loops simultaneously. How to bridge the culture gap: In an engineering environment traditionally rooted in strong analytics, the ideas and practices for scenario-focused engineering may not be intuitive. Learn how to change team mindset from deciding what a product, service, or device will do, to discovering what customers actually want and what will work for them in real-life scenarios. Connections with Lean and Agile approaches: See the connections, gaps, and overlaps among the Lean, Agile, and Scenario-Focused Engineering methodologies, and achieve a more holistic view of software development.

Usability engineering is about designing products that are easy to use. This text provides an introduction to human computer interaction principles, and how to apply them in ways that make software and hardware more effective and easier to use.

John Carroll shows how a pervasive but underused element of design practice, the scenario, can transform information systems design. Difficult to learn and awkward to use, today's information systems often change our activities in ways that we do not need or want. The problem lies in the software development process. In this book John Carroll shows how a pervasive but underused element of design practice, the scenario, can transform information systems design. Traditional textbook approaches manage the complexity of the design process via abstraction, treating design problems as if they were composites of puzzles. Scenario-based design uses concretization. A scenario is a concrete story about use. For example: "A person turned on a computer; the screen displayed a button labeled Start; the person used the mouse to select the button." Scenarios are a vocabulary for coordinating the central tasks of system development—understanding people's needs, envisioning new activities and technologies, designing effective systems and software, and drawing general lessons from systems as they are developed and used. Instead of designing software by listing requirements, functions, and code modules, the designer focuses first on the activities that need to be supported and then allows descriptions of those activities to drive everything else. In addition to a comprehensive discussion of the principles of scenario-based design, the book includes in-depth examples of its application.

This volume is based on a workshop sponsored by the editor at IBM, and includes contributions from an international group of researchers in the field of human computer interaction.

A human-centric guide to solving complex problems in engineering management, from sizing teams to handling technical debt. There’s a saying that people don’t leave companies, they leave managers. Management is a key part of any organization, yet the discipline is often self-taught and unstructured. Getting to the good solutions for complex management challenges can make the difference between fulfillment and frustration for teams—and, ultimately, between the success and failure of companies. Will Larson’s An Elegant Puzzle focuses on the particular challenges of engineering management—from sizing teams to handling technical debt to performing succession planning—and provides a path to the good solutions. Drawing from his experience at Digg, Uber, and Stripe, Larson has developed a thoughtful approach to engineering management for leaders of all levels at companies of all sizes. An Elegant Puzzle balances structured principles and human-centric thinking to help any leader create more effective and rewarding organizations for engineers to thrive in.

Extending the scenario method beyond interface design, this important book shows developers how to design more effective systems by soliciting, analyzing, and elaborating stories from end-users Contributions from leading industry consultants and opinion-makers present a range of scenario techniques, from the light, sketchy, and agile to the careful and systematic Includes real-world case studies from Philips, DaimlerChrysler, and Nokia, and covers systems ranging from custom software to embedded hardware-software systems

This book introduces a generic and systematic design-time/run-time methodology for handling the dynamic nature of modern embedded systems, without adding large safety margins in the design. The techniques introduced can be utilized on top of most existing static mapping methodologies to deal effectively with dynamism and to increase drastically their efficiency. This methodology is based on the concept of system scenarios, which group system behaviors that are similar from a multi-dimensional cost perspective, such as resource requirements, delay, and energy consumption. Readers will be enabled to design systems capable to adapt to current inputs, improving system quality and/or reducing cost, possibly learning on-the-fly during execution. Provides an effective solution to deal with dynamic system design Includes a broad survey of the state-of-the-art approaches in this domain Enables readers to design for substantial cost improvements (e.g. energy reductions), by exploiting system scenarios Demonstrates how the methodology has been applied effectively on various, real design problems in the embedded system context