The highly competitive and globalized software market is creating pressure on software companies. Given the current boundary conditions, it is critical to continuously increase time-to-market and reduce development costs. In parallel, driven by private life experiences with mobile computing devices, the World Wide Web and software-based services, peoples’ general expectations with regards to software are growing. They expect software that is simple and joyful to use. In the light of the changes that have taken place in recent years, software companies need to fundamentally reconsider the way they develop and deliver software to their customers. This book introduces fundamentals, trends and best practices in the software industry from a threefold perspective which equally takes into account design, management, and development of software. It demonstrates how cross-functional integration can be leveraged by software companies to successfully build software for people. Professionals from business and academia give an overview on state-of-the-art knowledge and report on key insights from their real-life experience. They provide guidance and hands-on recommendation on how to create winning products. This combined perspective fosters the transfer of knowledge between research and practice and offers a high practical value for both sides. The book targets both, practitioners and academics looking for successfully building software in the future. It is directed at Managing Directors of software companies, Software Project Managers, Product Managers and Designers, Software Developers as well as academics and students in the area of Software and Information Systems Engineering, Human Computer Interaction (HCI), and Innovation Management.​

This book provides key insights into current trends of software product management, software development and user-centered design of software. Includes cross-industry best practice cases from well-known companies.

Well-known author and long-time manager Watts Humphrey offers keen insight into the special challenge of identifying, motivating, and organizing creative technical people, and the opportunities involved in managing these people.

This is the digital version of hte printed book (Copyright © 1997). Software testers require technical and political skills to survive what can often be a lose-lose relationship with developers and managers. Whether testing is your specialty or your stepping stone to a career as a developer, there's no better way to survive the pressures put on testers than to meet the ten challenges described in this practical handbook. This book goes beyond the technical skills required for effective testing to address the political realities that can't be solved by technical knowledge alone. Communication and negotiation skills must be in every tester's tool kit. Authors Perry and Rice compile a "top ten" list of the challenges faced by testers and offer tactics for success. They combine their years of experience in developing testing processes, writing books and newsletters on testing, and teaching seminars on how to test. The challenges are addressed in light of the way testing fits into the context of software development and how testers can maximize their relationships with managers, developers, and customers. In fact, anyone who works with software testers should read this book for insight into the unique pressures put on this part of the software development process. "Somewhere between the agony of rushed deadlines and the luxury of all the time in the world has got to be a reasonable approach to testing."—from Chapter 8 The Top Ten People Challenges Facing Testers Challenge #10: Getting Trained in Testing Challenge #9: Building Relationships with Developers Challenge #8: Testing Without Tools Challenge #7: Explaining Testing to Managers Challenge #6: Communicating with Customers—And Users Challenge #5: Making Time for Testing Challenge #4: Testing What's Thrown Over the Wall Challenge #3: Hitting a Moving Target Challenge #2: Fighting a Lose-Lose Situation Challenge #1: Having to Say No

Through a set of lively anecdotes and essays, Nathaniel Borenstein traces the divergence between the fields of software engineering and user-centered software design, and attempts to reconcile the needs of people in both camps. Originally published in 1991. The Princeton Legacy Library uses the latest print-on-demand technology to again make available previously out-of-print books from the distinguished backlist of Princeton University Press. These editions preserve the original texts of these important books while presenting them in durable paperback and hardcover editions. The goal of the Princeton Legacy Library is to vastly increase access to the rich scholarly heritage found in the thousands of books published by Princeton University Press since its founding in 1905.

Based on highly confidential interviews with personnel, internal memos, and top-secret company documents, this compelling portrait reveals the philosophy, style, and competitive strategies that have taken Microsoft to the heights of the high-tech industry.

It’s been said that software is eating the planet. 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.

A radical approach to getting IT projects done faster andcheaper than anyone thinks possible Software in 30 Days summarizes the Agile and Scrumsoftware development method, which allows creation of game-changingsoftware, in just 30 days. Projects that use it are three timesmore successful than those that don't. Software in 30 Daysis for the business manager, the entrepreneur, the productdevelopment manager, or IT manager who wants to develop softwarebetter and faster than they now believe possible. Learn how thisunorthodox process works, how to get started, and how to succeed.Control risk, manage projects, and have your people succeed withsimple but profound shifts in the thinking. The authors explain powerful concepts such as the art of thepossible, bottom-up intelligence, and why it's good to failearly—all with no risk greater than thirty days. The productivity gain vs traditional "waterfall" methods hasbeen over 100% on many projects Author Ken Schwaber is a co-founder of the Agile softwaremovement, and co-creator, with Jeff Sutherland, of the "Scrum"technique for building software in 30 days Coauthor Jeff Sutherland was cosigner of the Agile Manifesto,which marked the start of the Agile movement Software in 30 Days is a must-read for all managers andbusiness owners who use software in their organizations or in theirproducts and want to stop the cycle of slow, expensive softwaredevelopment. Programmers will want to buy copies for their managersand their customers so they will know how to collaborate to get thebest work possible.