Analyzing information and acting accordingly is a key strategic goal of every business. But vast quantities of data are of little use if they are not structured and kept in such a way as to be readily accessible and applicable. Only optimally organized information can drive maximum productivity. Blissful Data is a reader-friendly book that reveals what it takes to achieve a state of perfect organization within the environment of a successful data warehouse. This timely book will help the reader: * understand how data evolves into information that drives better decision making * recognize the pitfalls, caused by people and politics, that lead to short-sighted solutions and long-term problems * manage data warehousing costs, performance, and expectations effectively * apply project management fundamentals to data warehouse endeavors. Blissful Data includes dozens of examples, as well as case studies illustrating successful, unsuccessful, and disastrous data warehouse strategies.

When software development teams move to agile methods, experienced project managers often struggle—doubtful about the new approach and uncertain about their new roles and responsibilities. In this book, two long-time certified Project Management Professionals (PMPRs) and Scrum trainers have built a bridge to this dynamic new paradigm. They show experienced project managers how to successfully transition to agile by refocusing on facilitation and collaboration, not “command and control.” The authors begin by explaining how agile works: how it differs from traditional “plan-driven” methodologies, the benefits it promises, and the real-world results it delivers. Next, they systematically map the Project Management Institute’s classic, methodology-independent techniques and terminology to agile practices. They cover both process and project lifecycles and carefully address vital issues ranging from scope and time to cost management and stakeholder communication. Finally, drawing on their own extensive personal experience, they put a human face on your personal transition to agile--covering the emotional challenges, personal values, and key leadership traits you’ll need to succeed. Coverage includes Relating the PMBOKR Guide ideals to agile practices: similarities, overlaps, and differences Understanding the role and value of agile techniques such as iteration/release planning and retrospectives Using agile techniques to systematically and continually reduce risk Implementing quality assurance (QA) where it belongs: in analysis, design, defect prevention, and continuous improvement Learning to trust your teams and listen for their discoveries Procuring, purchasing, and contracting for software in agile, collaborative environments Avoiding the common mistakes software teams make in transitioning to agile Coordinating with project management offices and non-agile teams “Selling” agile within your teams and throughout your organization For every project manager who wants to become more agile. Part I An Agile Overview 7 Chapter 1 What is "Agile"? 9 Chapter 2 Mapping from the PMBOKR Guide to Agile 25 Chapter 3 The Agile Project Lifecycle in Detail 37 Part II The Bridge: Relating PMBOKR Guide Practices to Agile Practices 49 Chapter 4 Integration Management 51 Chapter 5 Scope Management 67 Chapter 6 Time Management 83 Chapter 7 Cost Management 111 Chapter 8 Quality Management 129 Chapter 9 Human Resources Management 143 Chapter 10 Communications Management 159 Chapter 11 Risk Management 177 Chapter 12 Procurement Management 197 Part III Crossing the Bridge to Agile 215 Chapter 13 How Will My Responsibilities Change? 217 Chapter 14 How Will I Work with Other Teams Who Aren't Agile? 233 Chapter 15 How Can a Project Management Office Support Agile? 249 Chapter 16 Selling the Benefits of Agile 265 Chapter 17 Common Mistakes 285 Appendix A Agile Methodologies 295 Appendix B Agile Artifacts 301 Glossary 321 Bibliography 327 Index 333

Incomplete or missed requirements, omissions, ambiguous product features, lack of user involvement, unrealistic customer expectations, and the proverbial scope creep can result in cost overruns, missed deadlines, poor product quality, and can very well ruin a project. Project Scope Management: A Practical Guide to Requirements for Engineering, Product, Construction, IT and Enterprise Projects describes how to elicit, document, and manage requirements to control project scope creep. It also explains how to manage project stakeholders to minimize the risk of an ever-growing list of user requirements. The book begins by discussing how to collect project requirements and define the project scope. Next, it considers the creation of work breakdown structures and examines the verification and control of the scope. Most of the book is dedicated to explaining how to collect requirements and how to define product and project scope inasmuch as they represent the bulk of the project scope management work undertaken on any project regardless of the industry or the nature of the work involved. The book maintains a focus on practical and sensible tools and techniques rather than academic theories. It examines five different projects and traces their development from a project scope management perspective—from project initiation to the end of the execution and control phases. The types of projects considered include CRM system implementation, mobile number portability, port upgrade, energy-efficient house design, and airport check-in kiosk software. After reading this book, you will learn how to create project charters, high-level scope, detailed requirements specifications, requirements management plans, traceability matrices, and a work breakdown structure for the projects covered.

In this book, best selling author, Paul Sanghera, offers cohesive, concise, yet comprehensive coverage of all the topics included in the PgMP exam. With a laser sharp focus on the exam objectives, the Study Guide goes beyond just being an "exam cram." The material is presented in a logical learning sequence: a section builds upon previous sections and a chapter on previous chapters. All concepts, simple and complex, are defined and explained when they appear the first time. There is no hopping from topic to topic and no technical jargon without explanation. Because no prior knowledge of program management is assumed, this book will be useful for both: those new to program management, as well as individuals with years of experience. Although the primary purpose of the book is to help you pass the PgMP exam, it will also serve as a great reference for the program managers before and after the exam. Special Features: Hundreds of review questions with fully explained answers A complete practice exam with fully explained answers The real world scenarios to help you deal with the program management issues in the real world and also to answer the scenario based questions in the exam Notes and tips to highlight the crucial points Exam’s Eye View section at the end of each chapter to emphasize the important points from the exam’s perspective Key Terms section at the end of each chapter that lists the important terms and concepts introduced in the chapter along with their definitions The exam objectives fully explained before their coverage in each chapter