This new edition of the best-selling PMP: Project Management Professional Study Guide covers the 2005 updates to both the Project Management Body of Knowledge (PMBOK) and the PMP exam. Author Kim Heldman presents the material in a clear and accessible manner, taking you through the process groups in their logical order so you understand the parts and the whole equally well.KEY TOPICS INCLUDE:Project Initiation. Determining project goals, determining deliverables, determining process outputs, documenting constraints, documenting assumptions, defining strategies, producing formal documentation.Project Planning. Refining a project, creating a WBS, developing a resource management plan, determining resource requirements, defining budgets, refining time and costs estimates, establishing project controls, obtaining plan approval.Project Execution. Committing and implementing resources, managing and communicating progress, implementing quality assurance procedures.Project Control. Measuring performance, refining control links, taking corrective action, evaluating effectiveness of corrective action, ensuring plan compliance, reassessing control plans, responding to risk event triggers, monitor project activity.Project Closing. Obtaining acceptance of deliverables, documenting lessons learned, facilitating closure, preserving product records and tools, releasing resources.Professional Responsibility. Ensuring integrity, contributing to knowledge base, balancing stakeholder interests, respecting differences.

    The key, as the authors show, is to integrate regularly and often using continuous integration (CI) practices and techniques. The authors first examine the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as database integration, testing, inspection, deployment, and feedback. Through more than forty CI-related practices using application examples in different languages, readers learn that CI leads to more rapid software development, produces deployable software at every step in the development lifecycle, and reduces the time between defect introduction and detection, saving time and lowering costs. With successful implementation of CI, developers reduce risks and repetitive manual processes, and teams receive better project visibility. The book covers How to make integration a "non-event" on your software development projects How to reduce the amount of repetitive processes you perform when building your software Practices and techniques for using CI effectively with your teams Reducing the risks of late defect discovery, low-quality software, lack of visibility, and lack of deployable software Assessments of different CI servers and related tools on the market The book's companion Web site, www.integratebutton.com, provides updates and code examples

    You may not like Facebook, but you can't deny its success. And to a large degree, that success stems from the "move fast" ethos. The entire culture of Facebook is built for speed.Move Fast is an exploration of modern software strategies and tactics through the lens of Facebook. Relying on in-depth interviews with more than two dozen Facebook engineers, this book explores the product strategy, cultural principles, and technologies that made Facebook the dominant social networking company. Most importantly, Move Fast investigates how you can apply those strategies to your creative projects.It's not easy to build a software company, but once you know how to move fast, your company will be prepared to build a strategy that benefits from the world's rapid changes, rather than suffering from them.

    Written by one of the best-known authorities on the subject, this extraordinary edition gives a profound understanding of project management. Content from this book is available as an online continuing professional education course at http: //www.wiley.com/WileyCDA/Section/id-320.... WileyCPE courses are available on demand, 24 hours a day, and are approved by the American Institute of Architects.(PMBOK, PMP, Project Management Professional, and CAPM are registered marks of the Project Management Institute, Inc.)

    Some of these are brands that have come from nowhere and created new categories, some have challenged the hegemony of long-standing leaders, and some are decades-old brands which have continuously reinvented themselves to stay on top.Drawing from her rich experience with brands in India, Anisha Motwani has created a powerful package of inspiration and methodology. With a Foreword by insights specialist Santosh Desai and an Afterword by innovation specialist Ranjan Malik, Storm the Norm will leave you altered. This book is replete with crucial untold secrets of businesses that made all the difference.

    Developers of any kind of application should read this book." Grady Booch"A comprehensive solution to the requirements challenges faced by every development team. Full of insight and ideas all developers can learn from." Ivar JacobsonDespite the wealth of development knowledge, experience, and tools available today, a substantial percentage of software projects fail, often because requirements are not correctly determined and defined at the outset, or are not managed correctly as the project unfolds. This second edition of the popular text Managing Software Requirements focuses on this critical cause of failure and offers a practical, proven approach to building systems that meet customers' needs on time and within budget.Using an accessible style, their own war stories, and a comprehensive case study, the authors show how analysts and developers can effectively identify requirements by applying a variety of techniques, centered on the power of use cases. The book illustrates proven techniques for determining, implementing, and validating requirements. It describes six vital Team Skills for managing requirements throughout the lifecycle of a project: Analyzing the Problem, Understanding User Needs, Defining the System, Managing Scope, Refining the System Definition, and Building the Right System. Managing Software Requirements, Second Edition, specifically addresses the ongoing challenge of managing change and describes a process for assuring that project scope is successfully defined and agreed upon by all stakeholders.Topics covered include:The five steps in problem analysisBusiness modeling and system engineeringTechniques for eliciting requirements from customers and stakeholdersEstablishing and managing project scopeApplying and refining use casesProduct managementTransitioning from requirements to design and implementationTransitioning from use cases to test casesAgile requirements methods

    In this book, author Gojko Adzic distills interviews with successful teams worldwide, sharing how they specify, develop, and deliver software, without defects, in short iterative delivery cycles.About the Technology Specification by Example is a collaborative method for specifying requirements and tests. Seven patterns, fully explored in this book, are key to making the method effective. The method has four main benefits: it produces living, reliable documentation; it defines expectations clearly and makes validation efficient; it reduces rework; and, above all, it assures delivery teams and business stakeholders that the software that's built is right for its purpose.About the Book This book distills from the experience of leading teams worldwide effective ways to specify, test, and deliver software in short, iterative delivery cycles. Case studies in this book range from small web startups to large financial institutions, working in many processes including XP, Scrum, and Kanban.This book is written for developers, testers, analysts, and business people working together to build great software.Purchase of the print book comes with an offer of a free PDF, ePub, and Kindle eBook from Manning. Also available is all code from the book.What's InsideCommon process patterns How to avoid bad practices Fitting SBE in your process 50+ case studies For additional resources go to specificationbyexample.com.

    The Mikado Method is a process for surfacing the dependencies in a codebase, so that you can systematically eliminate technical debt and get things done.It gets its name from a simple game commonly known as "pick-up sticks." You start with a jumbled pile of sticks. The goal is to remove the Mikado, or Emperor, stick without disturbing the others. Players carefully remove sticks one at a time, leaving the rest of the heap intact, slowly exposing the Mikado. The game is a great metaphor for eliminating technical debt—carefully extracting each intertwined dependency until you're able to successfully resolve the central issue and move on.The Mikado Method is a book by the creators of this process. It describes a pragmatic, straightforward, and empirical method to plan and perform non-trivial technical improvements on an existing software system. The method has simple rules, but the applicability is vast. As you read, you'll practice a step-by-step system for identifying the scope and nature of your technical debt, mapping the key dependencies, and determining the safest way to approach the "Mikado"-your goal. A natural byproduct of this process is the Mikado Graph, a minimalistic, relevant, just-in-time roadmap and information radiator that reflects deep understanding of how your system works.

    In doing so, they considerably enhance this book which continues at its core to be about the subject that Anita and Harsha are best-equipped to write on: Winning!As has been proven many times over, ability is not a major distinguishing factor in success, especially as the level of competition increases. But if you combine your ability with the right attitude and the passion to excel, you too can become the best that you can be; which is indeed what winning is all about and is the universal formula for winning that The Winning Way 2.0 explores.

    Everything you need to be fully prepared to take the PRINCE2Foundation and Practitioner examAs an internationally recognized certification which focuses onthe Foundation and Practitioner levels along with being recommendedby the Project Management Institute, the PRINCE2 accreditationgives a bolster to any resume.The author, David Hinde, has trained hundreds of individualsfrom many different backgrounds to prepare for the PRINCE2 exams.The book provides explanations of all parts of the PRINCE2approach, lots of practical examples, and a whole range of mockexamination questions to test your knowledge.Explains all the PRINCE2 themes, processes, principles, rolesand management products for the very latest version of PRINCE2(PRINCE2 2009 Edition)Features full coverage of all Foundation and Practitioner levelexam objectivesPresents real-world scenarios, showing how the method isused in business and the public sectorIncludes challenging review questions and electronic flashcardsto sharpen your knowledgeCovers tips and techniques for tackling the PRINCE2accreditation examinations and shows you how and where to take theexamsIncorporates over 300 sample Foundation-level and over 100sample Practitioner-level questions, with answers and fullexplanationsContains a glossary of all PRINCE2 terminology and a quickreference to all the PRINCE2 management productsGives a web link to a set of on-line tools with more bonusexamsPRINCE2 Study Guide covers all the necessary topics youneed to know in order to confidently take the PRINCE2 Foundationand Practitioner exams.

    So how do they relate to each other? The purpose of this book is to clear up the fog, so you can figure out how Kanban and Scrum might be useful in your environment. Part I illustrates the similarities and differences between Kanban and Scrum, comparing for understanding, not for judgement. There is no such thing as a good or bad tool - just good or bad decisions about when and how to use which tool. This book includes: - Kanban and Scrum in a nutshell - Comparison of Kanban and Scrum and other Agile methods - Practical examples and pitfalls - Cartoons and diagrams illustrating day-to-day work - Detailed case study of a Kanban implementation within a Scrum organization Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams.

    In fact, Serve to Be Great: Leadership Lessons from a Prison, a Monastery, and a Boardroom will train you to make this a reality. Although it’s not an easy process, it is a worthwhile one.By making a shift in your approach to leadership, you can become a highly effective leader who enjoys your work and makes the world a better place. The shift is simply a matter of gradually becoming more focused on how you can serve others and increase your capacity to do so.Matt Tenney introduces us to the principles in this book through the story of going from selfish to servant while on his journey from prisoner to monk to social entrepreneur. He also cites numerous business case studies and research that demonstrate how putting serving first results in: - Attracting top talent - Increased engagement and lower turnover - A more innovative team culture - Better customer service - A better ROI on marketing efforts The book also offers practical, actionable guidance for making the shift to becoming an extraordinary leader who is devoted to serving and inspiring greatness in others.All of the author proceeds from the sale of this book are donated to charity.

    Today, Total Quality is an integral component of management success in today's complex business environment. This text presents an overview of the key principles of total quality and links those concepts to traditional management practices and organizational models in management theory. This book has three objectives: 1) to familiarize readers with the basic principles and methods associated with total quality management; 2) to show readers how these principles and methods have been put into effect in a variety of organizations; and, 3) to illustrate the relationship between total quality principles and the theories and models studied in management courses.

    Enjoy a journey through the eyes of a geek working at one of the most important companies in the world as he walks you through events both large and small. Just don't get caught in the Redmond reality distortion field! What others are saying about "A Microsoft Life": "Any self-respecting geek needs to read this book. Stepto provides an enjoyable and entertaining insight of life inside Microsoft." - Larry "Major Nelson" Hryb, Director of Programming for Xbox LIVE "Anyone who lived through the adolescent years of the computer revolution will alternate between laughing and crying (from laughing) at these great stories from inside the monolith. - Ken Denmead, NYT Bestselling Author, and editor of Geekdad.com

    Plenty of books describe what agile development is or why it helps software projects succeed, but very few combine information for developers, managers, testers, and customers into a single package that they can apply directly. This book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors' many years of experience with Extreme Programming (XP). You get a gestalt view of the agile development process, including comprehensive guidance for non-technical readers and hands-on technical practices for developers and testers. The Art of Agile Development gives you clear answers to questions such as:How can we adopt agile development? Do we really need to pair program? What metrics should we report? What if I can't get my customer to participate? How much documentation should we write? When do we design and architect? As a non-developer, how should I work with my agile team? Where is my product roadmap? How does QA fit in? The book teaches you how to adopt XP practices, describes each practice in detail, then discusses principles that will allow you to modify XP and create your own agile method. In particular, this book tackles the difficult aspects of agile development: the need for cooperation and trust among team members. Whether you're currently part of an agile team, working with an agile team, or interested in agile development, this book provides the practical tips you need to start practicing agile development. As your experience grows, the book will grow with you, providing exercises and information that will teach you first to understand the rules of agile development, break them, and ultimately abandon rules altogether as you master the art of agile development. "Jim Shore and Shane Warden expertly explain the practices and benefits of Extreme Programming. They offer advice from their real-world experiences in leading teams. They answer questions about the practices and show contraindications - ways that a practice may be mis-applied. They offer alternatives you can try if there are impediments to applying a practice, such as the lack of an on-site customer. --Ken Pugh, Author of Jolt Award Winner, Prefactoring "I will leave a copy of this book with every team I visit." --Brian Marick, Exampler Consulting