While a number of books on the market deal with software requirements, this is the first resource to offer you a methodology for discovering and testing the real business requirements that software products must meet in order to provide value. The book provides you with practical techniques that help prevent the main causes of requirements creep, which in turn enhances software development success and satisfaction among the organizations that apply these approaches. Complementing discovery methods, you also learn more than 21 ways to test business requirements from the perspectives of assessing suitability of form, identifying overlooked requirements, and evaluating substance and content. The powerful techniques and methods presented are applied to a real business case from a company recognized for world-class excellence. You are introduced to the innovative Problem Pyramidtm technique which helps you more reliably identify the real problem and requirements content. From an examination of key methods for gathering and understanding information about requirements, to seven guidelines for documenting and communicating requirements, while avoiding analysis paralysis, this book is a comprehensive, single source for uncovering the real business requirements for your software development projects.

"This book is not only of practical value. It's also a lot of fun to read." Michael Jackson, The Open University. Do you need to know how to create good requirements? Discovering Requirements offers a set of simple, robust, and effective cognitive tools for building requirements. Using worked examples throughout the text, it shows you how to develop an understanding of any problem, leading to questions such as: What are you trying to achieve? Who is involved, and how? What do those people want? Do they agree? How do you envisage this working? What could go wrong? Why are you making these decisions? What are you assuming? The established author team of Ian Alexander and Ljerka Beus-Dukic answer these and related questions, using a set of complementary techniques, including stakeholder analysis, goal modelling, context modelling, storytelling and scenario modelling, identifying risks and threats, describing rationales, defining terms in a project dictionary, and prioritizing. This easy to read guide is full of carefully-checked tips and tricks. Illustrated with worked examples, checklists, summaries, keywords and exercises, this book will encourage you to move closer to the real problems you're trying to solve. Guest boxes from other experts give you additional hints for your projects. Invaluable for anyone specifying requirements including IT practitioners, engineers, developers, business analysts, test engineers, configuration managers, quality engineers and project managers. A practical sourcebook for lecturers as well as students studying software engineering who want to learn about requirements work in industry. Once you've read this book you will be ready to create good requirements!

Step by step, Facilitating the Project Lifecycle guides theproject manager/facilitator in making smart choices about when andhow to pull key talent together to spell success for the projectand ultimately the organization. The authors will help youunderstand the benefits of using facilitated group work sessions toget real work done during a project and get it done better and moreefficiently than more traditional individual work approaches. Inaddition, the book includes: Recommendations for capitalizing on group knowledge toaccelerate the building of key project deliverables and ensuretheir quality as they are built A work session structure for planning, delivering, andfollowing up facilitated work sessions Guides for building key project deliverables Sample agendas Proven techniques for managing the group dynamics

Have you ever been involved in a project that didn’t require a meeting? Neither have we. Well-run project meetings allow teams to get through the maze of distractions and obstacles to achieve results. Unfortunately, many project meetings aren’t well-run—they are viewed, by team members, as unproductive, tedious, wastes of precious time. But you can change that. The Project Meeting Facilitator contains practical techniques and practices that will help you facilitate our meetings more effectively, transforming them into well-planned, well-managed journeys that engage the team while achieving the intended goals.

Project Requirements: A Guide to Best Practices gives project managers tools they can assimilate and apply easily to improve project success rates, reduce development costs, reduce rework, and accelerate time to market. Based on experience and best practices, this valuable reference will help you: • Clarify real requirements before you initiate project work • Improve management of project requirements • Save time and effort • Manage to your schedule • Improve the quality of deliverables • Increase customer satisfaction and drive repeat business Project Requirements: A Guide to Best Practices provides project managers with a direct, practical strategy to overcome requirements challenges and manage requirements successfully.

EBOOK: Information Systems Development

To build reliable, industry-applicable software products, large-scale software project groups must continuously improve software engineering processes to increase product quality, facilitate cost reductions, and adhere to tight schedules. Emphasizing the critical components of successful large-scale software projects, Software Project Management: A Process-Driven Approach discusses human resources, software engineering, and technology to a level that exceeds most university-level courses on the subject. The book is organized into five parts. Part I defines project management with information on project and process specifics and choices, the skills and experience needed, the tools available, and the human resources organization and management that brings it all together. Part II explores software life-cycle management. Part III tackles software engineering processes and the range of processing models devised by several domestic and international organizations. Part IV reveals the human side of project management with chapters on managing the team, the suppliers, and the customers themselves. Part V wraps up coverage with a look at the technology, techniques, templates, and checklists that can help your project teams meet and exceed their goals. A running case study provides authoritative insight and insider information on the tools and techniques required to ensure product quality, reduce costs, and meet project deadlines. Praise for the book: This book presents all aspects of modern project management practices ... includes a wealth of quality templates that practitioners can use to build their own tools. ... equally useful to students and professionals alike. —Maqbool Patel, PhD, SVP/CTO/Partner, Acuitec

Requirements are a crucial ingredient of any successful project. This is true for any product--software, hardware, consumer appliance, or large-scale construction. You have to understand its requirements--what is needed and desired--if you are to build the right product. Most developers recognize the truth in this statement, even if they don't always live up to it. Far less obvious, however, is the contribution that the requirements activity makes to project management. Requirements, along with other outputs from the requirements activity, are potent project management tools. In "Requirements-Led Project Management, " Suzanne and James Robertson show how to use requirements to manage the development lifecycle. They show program managers, product and project managers, team leaders, and business analysts specifically how to: Use requirements as input to project planning and decision-makingDetermine whether to invest in a projectDeliver more appropriate products with a quick cycle timeMeasure and estimate the requirements effortDefine the most effective requirements process for a projectManage stakeholder involvement and expectationsSet requirements prioritiesManage requirements across multiple domains and technologiesUse requirements to communicate across business and technological boundaries In their previous book, "Mastering the Requirements Process, " the Robertsons defined Volere--their groundbreaking and now widely adopted requirements process. In this second book, they look at the outputs from the requirements process and demonstrate how you can take advantage of the all-important links between requirements and project success.

Taking you beyond the Capability Maturity Model° to the integrated world of systems and software, this comprehensive resource presents CMMI° in a manner that easy to comprehend by higher-level managers and practitioners alike. The book gives you a clear picture of the activities an organization would be engaged in if their systems and software engineering processes were based on CMMI°. You learn the roles and responsibilities of professionals at all levels, from senior and middle management to project leaders and quality assurance personnel.