Everyone can ask questions, right? Unfortunately, that's not the case. Interviewing Users provides invaluable interviewing techniques and tools that enable you to conduct informative interviews with anyone. You'll move from simply gathering data to uncovering powerful insights about people.Interviewing Users will explain how to succeed with interviewing, including:* Embracing how other people see the world* Building rapport to create engaging and exciting interactions* Listening in order to build rapport.With this book, Steve Portigal uses stories and examples from his 15 years of experience to show how interviewing can be incorporated into the design process, helping you learn the best and right information to inform and inspire your design.

    It is written in a conversational tone, doesn't take itself too seriously, and avoids extraneous fluff."- Eric Ries, Author & Creator of the Lean Startup methodology"Get the CustDev book to dive deep into customer interviews and understand how your product can be developed to meet your customers' needs."- Dan Martell, Founder of Flowtown, angel investorCustomer Development is a four-step framework for helping startups discover and validate their customers, product, and go-to-market strategy, developed by Steve Blank and an integral part of Eric Ries' Lean Startup methodology. Focused on the Customer Discovery step, The Entrepreneur's Guide to Customer Development is an easy to follow guide for finding early adopters, building a Minimum Viable Product, finding Product-Market fit, and establishing a sales and marketing roadmap.Deemed a "must-read" by Steve Blank and Eric Ries, inside you will find detailed customer development and lean startup concept definitions, a step-by-step approach to best practices, a business model analysis guide, case studies, rich graphics, as well as worksheets and exercises. No matter the stage of your business, you will return often to this guide to learn how to build a product people want;"get out of the building;" foster strong customer relationships; test business model risk; reach out to early adopters; conduct startup marketing; create a customer funnel based on buyers' process; and prepare your startup to scale up.The Entrepreneur's Guide to Customer Development: A Cheat Sheet to The Four Steps to the Epiphany, affectionately known as the "CustDev book," serves as course text for classes at Stanford University, University of Chicago, Boston University, DePaul University, University of Minnesota and University of Norway."Our UCL (University College London) students love The Entrepreneur's Guide to Customer Development. Thanks to Brant & Patrick for writing this helpful book. "- Dave Chapman, Deputy Head of the Department of Management Science and Innovation at UCL (University College London)"Love it! Required reading for all NYU entrepreneurs."- Frank Rimalovski, Managing Director of NYU Innovation Venture FundThis book is both an introduction for those unfamiliar with lean concepts and highly actionable for lean practitioners. It is a user friendly guide, written to be accessible to marketing professionals, Engineers startup founders and entrepreneurs, VCs, angels, and anyone else involved in building scalable startups.Existing companies will benefit to from applying Customer Development principles described in detail herein: for example, startups struggling to achieve market traction, or well established companies seeking to spark new innovation.This is a business book for startups like no other. No fluff, but rather sound principles and concrete steps to take to build your business. Get up to speed on Customer Development now.

    However, large-scale agile development is difficult, and publicly available case studies have been scarce. Now, three agile pioneers at Hewlett-Packard present a candid, start-to-finish insider's look at how they've succeeded with agile in one of the company's most mission-critical software environments: firmware for HP LaserJet printers.This book tells the story of an extraordinary experiment and journey. Could agile principles be applied to re-architect an enormous legacy code base? Could agile enable both timely delivery and ongoing innovation? Could it really be applied to 400+ developers distributed across four states, three continents, and four business units? Could it go beyond delivering incremental gains, to meet the stretch goal of 10x developer productivity improvements?It could, and it did--but getting there was not easy.Writing for both managers and technologists, the authors candidly discuss both their successes and failures, presenting actionable lessons for other development organizations, as well as approaches that have proven themselves repeatedly in HP's challenging environment. They not only illuminate the potential benefits of agile in large-scale development, they also systematically show how these benefits can actually be achieved.Coverage includes: - Tightly linking agile methods and enterprise architecture with business objectives- Focusing agile practices on your worst development pain points to get the most bang for your buck- Abandoning classic agile methods that don't work at the largest scale- Employing agile methods to establish a new architecture- Using metrics as a "conversation starter" around agile process improvements- Leveraging continuous integration and quality systems to reduce costs, accelerate schedules, and automate the delivery pipeline- Taming the planning beast with "light-touch" agile planning and lightweight long-range forecasting- Implementing effective project management and ensuring accountability in large agile projects- Managing tradeoffs associated with key decisions about organizational structure- Overcoming U.S./India cultural differences that can complicate offshore development- Selecting tools to support quantum leaps in productivity in your organization- Using change management disciplines to support greater enterprise agility

    If you're a desktop, mobile or web developer, this book is your blueprint to getting your startup off the ground with no outside investment.This book intentionally avoids topics restricted to venture-backed startups such as: honing your investment pitch, securing funding, and figuring out how to use the piles of cash investors keep placing in your lap.This book assumes:* You don't have $6M of investor funds sitting in your bank account* You're not going to relocate to the handful of startup hubs in the world* You're not going to work 70 hour weeks for low pay with the hope of someday making millions from stock optionsThere's nothing wrong with pursuing venture funding and attempting to grow fast like Amazon, Google, Twitter, and Facebook. It just so happened that most people are not in a place to do this.

    Kerth guides readers through productive, empowering retrospectives of project performance.Whether your shop calls them postmortems or postpartums or something else, project retrospectives offer organizations a formal method for preserving the valuable lessons learned from the successes and failures of every project. These lessons and the changes identified by the community will foster stronger teams and savings on subsequent efforts.For a retrospective to be effective and successful, though, it needs to be safe. Kerth shows facilitators and participants how to defeat the fear of retribution and establish an air of mutual trust. One tool is Kerth's Prime Directive:Regardless of what we discover, we must understand and truly believe that everyone did the best job he or she could, given what was known at the time, his or her skills and abilities, the resources available, and the situation at hand.Applying years of experience as a project retrospective facilitator for software organizations, Kerth reveals his secrets for managing the sensitive, often emotionally charged issues that arise as teams relive and learn from each project.Don't move on to your next project without consulting and using this readable, practical handbook. Each member of your team will be better prepared for the next deadline.

    How do you present large volumes of information to people who need to find what they're looking for quickly? This classic primer shows information architects, designers, and web site developers how to build large-scale and maintainable web sites that are appealing and easy to navigate. The new edition is thoroughly updated to address emerging technologies -- with recent examples, new scenarios, and information on best practices -- while maintaining its focus on fundamentals. With topics that range from aesthetics to mechanics, Information Architecture for the World Wide Web explains how to create interfaces that users can understand right away. Inside, you'll find:* An overview of information architecture for both newcomers and experienced practitioners* The fundamental components of an architecture, illustrating the interconnected nature of these systems. Updated, with updates for tagging, folksonomies, social classification, and guided navigation* Tools, techniques, and methods that take you from research to strategy and design to implementation. This edition discusses blueprints, wireframes and the role of diagrams in the design phase* A series of short essays that provide practical tips and philosophical advice for those who work on information architecture* The business context of practicing and promoting information architecture, including recent lessons on how to handle enterprise architecture* Case studies on the evolution of two large and very different information architectures, illustrating best practices along the way* How do you document the rich interfaces of web applications? How do you design for multiple platforms and mobile devices? With emphasis on goals and approaches over tactics or technologies, this enormously popular book gives you knowledge about information architecture with a framework that allows you to learn new approaches -- and unlearn outmoded ones.

    A developer-friendly, practical and pragmatic guide to lightweight software architecture, technical leadership and the balance with agility.This book is a practical, pragmatic and lightweight guide to software architecture, specifically aimed at developers, and focused around the software architecture role and process.

    Easy to digest and highly visual, you can read it in a weekend...and use it for an entire career. Drawing on 15 years of pioneering experience implementing Agile and Scrum and helping others do so, Zuzana Sochova guides you step by step through all key facets of success as a ScrumMaster in any context. Sochova reviews the ScrumMaster's responsibilities, introduces her powerful State of Mind model and #ScrumMasterWay approach, and teaches crucial metaskills that every ScrumMaster needs. Learn how to build more effective teams, manage change in Agile environments, and take fulladvantage of the immensely powerful ScrumMaster toolbox. Throughout, Sochova illuminates each concept with practical, proven examples that show how to move from idea to successful execution.Understand the ScrumMaster's key role in creating high-performance self-organizing teams Master all components of the ScrumMaster State of Mind: teaching/mentoring, removing impediments, facilitation, and coaching Operate effectively as a ScrumMaster at all levels: team, relationships, and the entire system Sharpen key ScrumMaster cognitive strategies and core competencies Build great teams, and improve teams that are currently dysfunctional Drive deeper change in a safer environment with better support for those affected Make the most of Shu Ha Ri, System Rule, Root Cause Analysis, Impact Mapping, and other ScrumMaster tools Whether you're a long-time Certified ScrumMaster (CSM) or participating in your first Scrum project, this guide will help you leverage world-class insight in all you do and get the outstanding results you're looking for. Register your product at informit.com/register for convenient access to downloads, updates, and corrections as they become available Normal 0 false false false EN-US X-NONE X-NONE

    In 1999, "Refactoring" revolutionized design by introducing an effective process for improving code. With the highly anticipated " Refactoring to Patterns ," Joshua Kerievsky has changed our approach to design by forever uniting patterns with the evolutionary process of refactoring.This book introduces the theory and practice of pattern-directed refactorings: sequences of low-level refactorings that allow designers to safely move designs to, towards, or away from pattern implementations. Using code from real-world projects, Kerievsky documents the thinking and steps underlying over two dozen pattern-based design transformations. Along the way he offers insights into pattern differences and how to implement patterns in the simplest possible ways.Coverage includes: A catalog of twenty-seven pattern-directed refactorings, featuring real-world code examples Descriptions of twelve design smells that indicate the need for this book s refactorings General information and new insights about patterns and refactoringDetailed implementation mechanics: how low-level refactorings are combined to implement high-level patterns Multiple ways to implement the same pattern and when to use each Practical ways to get started even if you have little experience with patterns or refactoring"Refactoring to Patterns" reflects three years of refinement and the insights of more than sixty software engineering thought leaders in the global patterns, refactoring, and agile development communities. Whether you re focused on legacy or greenfield development, this book will make you a better software designer by helping you learn how to make important design changes safely and effectively. "

    If the facts don't hang together on a latticework of theory, you don't have them in a usable form. You've got to have models in your head."- Charlie Munger, investor, vice chairman of Berkshire HathawayThe world's greatest problem-solvers, forecasters, and decision-makers all rely on a set of frameworks and shortcuts that help them cut through complexity and separate good ideas from bad ones. They're called mental models, and you can find them in dense textbooks on psychology, physics, economics, and more.Or, you can just read Super Thinking, a fun, illustrated guide to every mental model you could possibly need. How can mental models help you? Well, here are just a few examples... • If you've ever been overwhelmed by a to-do list that's grown too long, maybe you need the Eisenhower Decision Matrix to help you prioritize. • Use the 5 Whys model to better understand people's motivations or get to the root cause of a problem. • Before concluding that your colleague who messes up your projects is out to sabotage you, consider Hanlon's Razor for an alternative explanation. • Ever sat through a bad movie just because you paid a lot for the ticket? You might be falling prey to Sunk Cost Fallacy. • Set up Forcing Functions, like standing meeting or deadlines, to help grease the wheels for changes you want to occur.So, the next time you find yourself faced with a difficult decision or just trying to understand a complex situation, let Super Thinking upgrade your brain with mental models.Note: in the US the subtitle is The Big Book of Mental Models and outside it is Upgrade Your Reasoning and Make Better Decisions with Mental Models.

    Whether you agree or disagree with him, and you're likely to do both, the essays in this book will always give you something worth thinking about.Mike Cohn, author of Succeeding with Agile: Software Development using ScrumTobias Mayer’s signature move is to pick up a stone and throw it through our glass house, smashing our old paradigms and causing us, after some pain and turmoil, to say, “OK, my comfortable way doesn’t work anymore. Now what?”Lyssa Adkins, author of Coaching Agile TeamsTobias Mayer has a really interesting mind: wide, deep, imaginative, and quirky. I value the quirky most because it's unpredictable. But in hindsight his jumps reveal themselves as the result of intelligence and rigor. What's more, he gets those jumps gracefully down on paper so that we can all participate.Lee Devin, author of Artrful Making and The Soul of DesignTobias Mayer is known in the agile community as a brilliant and evangelical orator, an innovative trainer and an extraordinary trouble maker. You could call him the Hunter S. Thompson of the software arena, and no one who knows him would laugh. This book is a collection of essays drawn from his writing over the past seven years on the blogs Agile Thinking and Agile Anarchy, missives from the front lines of agile practice that represent the next generation of thinking on conventional agile topics like self-organization, technical debt and estimation–and utterly original writing on new topics like organizational anarchy, corporate oppression, the effect of testosterone on business practices, and artisanal product development.Moving beyond the mere how-to, this is a book to excite the emotions and the intellect in those of us who have chosen the path of scrum to guide us in our work lives. Not since Paul Graham’s Hackers and Painters has the discussion of software development been elevated to this level of world-view-changing discourse. In Tobias Mayer, technology has an exciting new voice to lead us into the brave new world of agile practice.

    Now, pioneering ThoughtWorks software engineering expert Sriram Narayan shows how to do just that. Drawing on 15+ years working with leaders in telecommunications, finance, energy, retail, and beyond, he introduces a comprehensive agile approach to "Business-IT Effectiveness" that is as practical as it is valuable. Narayan demonstrates how to integrate agility throughout sales, marketing, product development, engineering, and operations, helping each function deliver more value individually and through its linkages with the rest of the business. Addressing people, process, and technology, he guides you in improving both the dynamic and static aspects of organization design, addressing team structure, accountability structures, organizational norms and culture, knowledge management, and more. Using real examples, Narayan helps you evaluate and improve organization designs to enhance autonomy, mastery, and purpose. You'll learn how to eliminate the specific organizational silos that cause the most problems... improve communication in organizations that claim to be (but aren't really) non-hierarchical... optimize the way you build teams, design office space, and even choose tools. Simply put, Agile IT Organization Design will help you improve improving the performance of any software organization by propagating agile wherever it makes sense and offers value.

    You've just been introduced to your new team as their Agile Coach. The team calls themselves The Dream Team. You are responsible for coming up with a plan to get the team back on track to achieve their project goals.Shortly after the initial product launch, The Dream Team was set a challenge by the Management Team to try out an alternative way of working called Agile. Eighteen months on and the team is working anything but like a dream. In fact, life's become a bit of a nightmare. Morale is low. Productivity has ground to a halt. Quality has become a taboo subject.Management believes the project has reached an impasse. They demand results and are prepared to outsource the remainder of the project. You have 5 days to figure out how to help the team move forward.Your fate and that of your team is entirely in your hands. What choices will you make? Choose badly and you’ll come to a sticky end. Choose wisely and you and your team stand a chance of living happily ever after. What will you choose to do?

    The modern economy—the world itself—relies on technology. Demand for the people who can produce it far outweighs the supply. So why do developers occupy largely subordinate roles in the corporate structure? Developer Hegemony explores the past, present, and future of the corporation and what it means for developers. While it outlines problems with the modern corporate structure, it’s ultimately a play-by-play of how to leave the corporate carnival and control your own destiny. And it’s an emboldening, specific vision of what software development looks like in the world of developer hegemony—one where developers band together into partner firms of “efficiencers,” finally able to command the pay, respect, and freedom that’s earned by solving problems no one else can. Developers, if you grow tired of being treated like geeks who can only be trusted to take orders and churn out code, consider this your call to arms. Bring about the autonomous future that’s rightfully yours. It’s time for developer hegemony.

    Readers new to Kanban will understand why and how it works, while those with experience will appreciate its fresh perspective and the connections it makes with a range of related models.