Accelerate Your Pursuit of Software Excellence by Learning from Others' Hard-Won Experience "Karl is one of the most thoughtful software people I know. He has reflected deeply on the software development irritants he has encountered over his career, and this book contains 60 of his most valuable responses." -- From the Foreword by&nbsp; Steve McConnell, Construx Software and author of &nbsp;Code Complete "Wouldn't it be great to gain a lifetime's experience without having to pay for the inevitable errors of your own experience? Karl Wiegers is well versed in the best techniques of business analysis, software engineering, and project management. You'll gain concise but important insights into how to recover from setbacks as well as how to avoid them in the first place." --Meilir Page-Jones, Senior Business Analyst, Wayland Systems Inc. Experience is a powerful teacher, but it's also slow and painful. You can't afford to make every mistake yourself! Software Development Pearls helps you improve faster and bypass much of the pain by learning from others who already climbed the learning curves. Drawing on 25+ years helping software teams succeed, Karl Wiegers has crystallized 60 concise, practical lessons for all your projects, regardless of your role, industry, technology, or methodology. Wiegers's insights and specific recommendations cover six crucial elements of success: requirements, design, project management, culture and teamwork, quality, and process improvement. For each, Wiegers offers First Steps for reflecting on your own experiences before you start; detailed Lessons with core insights, real case studies, and actionable solutions; and Next Steps for planning adoption in your project, team, or organization. This is knowledge you weren't taught in college or boot camp. It can boost your performance as a developer, business analyst, quality professional, or manager. <ul> <li>Clarify requirements to gain a shared vision and understanding of your real problem</li> <li>Create robust designs that implement the right functionality and quality attributes and can evolve</li> <li>Anticipate and avoid ubiquitous project management pitfalls</li> <li>Grow a culture in which behaviors actually align with what people claim to value</li> <li>Plan realistically for quality and build it in from the outset</li> <li>Use process improvement to achieve desired business results, not as an end in itself</li> <li>Choose your next steps to get full value from all these lessons</li> </ul> Register your book for convenient access to downloads, updates, and/or corrections as they become available. See inside book for details.

Software Development Pearls: Lessons from Fifty Years of Software Experience

Computers & Technology

Wiegers, Karl

Computer Science

Addison-Wesley Professional

<h4>20 Best Practices for Developing and Managing Requirements on Any Project</h4> Software Requirements Essentials presents 20 core practices for successful requirements planning, elicitation, analysis, specification, validation, and management. Leading requirements experts Karl Wiegers and Candase Hokanson focus on the practices most likely to deliver superior value in both traditional and agile projects, in any application domain. These core practices help teams understand business problems, engage the right participants, articulate better solutions, improve communication, implement the most valuable functionality in the right sequence, and adapt to change and growth. Concise and tightly focused, this book offers just enough pragmatic "how-to" detail for you to apply the core practices with confidence, whether you're a business analyst, requirements engineer, product manager, product owner, or developer. Using it, your entire team can build a shared understanding of key concepts, terminology, techniques, and rationales--and work together more effectively on every project. You'll learn how to: <ul> <li>Clarify problems, define business objectives, and set solution boundaries</li> <li>Identify stakeholders and decision makers</li> <li>Explore user tasks, events, and responses</li> <li>Assess data concepts and relationships</li> <li>Elicit and evaluate quality attributes</li> <li>Analyze requirements and requirement sets, create models and prototypes, and set priorities</li> <li>Specify requirements in a consistent, structured, well-documented fashion</li> <li>Review, test, and manage change to requirements</li> </ul> "I once read the ten best-selling requirements engineering books of the prior ten years. This one book succinctly presents more useful information than those ten books combined." --Mike Cohn, author of User Stories Applied and co-founder, Scrum Alliance

Software Requirements Essentials: Core Practices for Successful Business Analysis

Hokanson, Candase

Programming

A practical introduction to peer reviews. It covers different methods of peer review, from the formal method of inspection to other less formal methods, and addresses the cultural and practical aspects of both. It presents the reader with a flexible set of approaches that they can use to meet their quality improvement goals. Whether they are performing inspection or other less formal methods of peer review, software development professionals should be able to use this text as a guide to learn from the experience of others and conduct more effective reviews.

Peer Reviews in Software: A Practical Guide

No matter how much instruction you've had on managing software requirements, there's no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project. Discover how to: 
<ul>
<li>Make the business case for investing in better requirements practices</li> <li>Generate estimates using three specific techniques</li> <li>Conduct inquiries to elicit meaningful business and user requirements</li> <li>Clearly document project scope</li> <li>Implement use cases, scenarios, and user stories effectively</li> <li>Improve inspections and peer reviews</li> <li>Write requirements that avoid ambiguity</li> </ul>

More About Software Requirements: Thorny Issues and Practical Advice

Microsoft Press

Now in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects. <ul>
<li>Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end.</li> <li>Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs.</li> <li>Fully updated with contemporary examples and many new practices and techniques.</li> <li>Describes how to apply effective requirements practices to agile projects and numerous other special project situations.</li> <li>Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process.</li> <li>Shares the insights gleaned from the authors’ extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars.</li> </ul>
 New chapters are included on specifying data requirements, writing high-quality functional requirements, and requirements reuse. Considerable depth has been added on business requirements, elicitation techniques, and nonfunctional requirements. In addition, new chapters recommend effective requirements practices for various special project situations, including enhancement and replacement, packaged solutions, outsourced, business process automation, analytics and reporting, and embedded and other real-time systems projects.

Software Requirements (Developer Best Practices)

Beatty, Joy

When 34-year-old forensic sculptor Jessica Sanford of Portland, Oregon, completes a forensic facial reconstruction on unidentified remains found in a forest, she discovers that she has a shocking personal connection to the victim. Jessica is then driven to identify the victim, to confirm their relationship, and to deliver justice for her death. Adopted as an infant, Jessica cleverly exploits connections with other adoptees and their families in her quest for the victim’s identity. Once she understands her link to the victim, Jessica finds herself more immersed in this case than in anything she has done before. Those involved in the apparent homicide are still out there—and Jessica intends to find them. Her relationships, her career, and her life are at risk as she strives to reconstruct the victim’s last days. Not just about uncovering a crime and hunting the suspects, The Reconstruction is also about a young woman’s search for her own identity. Though the reader knows from the outset who the victim is and who was involved with her death, Jessica does not. The reader accompanies Jessica as she applies all of her skills and all of her smarts to try to solve the mystery of a lifetime. Readers who enjoy suspenseful mysteries, forensics procedurals, and mysteries featuring a strong female protagonist will find The Reconstruction engrossing.

The Reconstruction

Mystery, Thriller & Suspense

Mystery

Agent Q Bookworks

<div>Have you ever noticed how many products appear to be designed by someone who has never used a product of that kind before? Nearly everyone has encountered websites, software apps, cars, appliances, and other products that made them wonder what the designers were thinking. The Thoughtless Design of Everyday Things presents more than 150 examples of products that violate nine fundamental design principles, along with suggestions for improving many of the flawed user interfaces and other design problems. These examples of thoughtless design reveal 70 specific lessons that designers ought to heed as they craft the user experience. This book describes numerous specific practices for enhancing product usability through usage-centered design strategies. You'll also see more than 40 products that exhibit particularly thoughtful designs, the kinds of products that surprise and delight users. Whether you're a designer, a product development manager, or a thoughtful and curious consumer, you'll find The Thoughtless Design of Everyday Things engaging, informative, and insightful.</div>

The Thoughtless Design of Everyday Things

Engineering & Transportation

Engineering

J. Ross Publishing

See the best price to sell, buy, or rent books by Wiegers, Karl. BookScouter helps to compare book prices from 25+ online bookstores and 30+ buyback vendors with a single search.

Books by Wiegers, Karl