Software project managers and their team members work individually towards a common goal. This book guides both, emphasizing basic principles that work at work. Software at work should be pleasant and productive, not just one or the other. This book emphasizes software project management at work. The author's unique approach concentrates on the concept that success on software projects has more to do with how people think individually and in groups than with programming. He summarizes past successful projects and why others failed. Visibility and communication are more important than SQL and C. The book discusses the technical and people aspects of software and how they relate to one another. The first part of the text discusses four themes: (1) people, process, product, (2) visibility, (3) configuration management, and (4) IEEE Standards. These themes stress thinking, organization, using what others have built, and people. The second part describes the software management principles of process, planning, and risk management. Part three discusses software engineering principles, the technical aspects of software projects. The fourth part examines software practices giving practical meaning to the individual topics covered in the preceding chapters. The final part of this book continues these practical aspects by illustrating a sample project through seven distinctive documents.

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

Written for researchers, professors, practitioners, students, and other computing professionals, this book covers Basics that Work at Work; People, Process, and Product; Visibility; Configuration Management Process; Planning; Risk Management; Requirements; Design; Testing; Managing a Project Day by Day; Managing Software Maintenance; and more.

The trusted handbook—now in a new edition This newly revised handbook presents a multifaceted view of systems engineering from process and systems management perspectives. It begins with a comprehensive introduction to the subject and provides a brief overview of the thirty-four chapters that follow. This introductory chapter is intended to serve as a "field guide" that indicates why, when, and how to use the material that follows in the handbook. Topical coverage includes: systems engineering life cycles and management; risk management; discovering system requirements; configuration management; cost management; total quality management; reliability, maintainability, and availability; concurrent engineering; standards in systems engineering; system architectures; systems design; systems integration; systematic measurements; human supervisory control; managing organizational and individual decision-making; systems reengineering; project planning; human systems integration; information technology and knowledge management; and more. The handbook is written and edited for systems engineers in industry and government, and to serve as a university reference handbook in systems engineering and management courses. By focusing on systems engineering processes and systems management, the editors have produced a long-lasting handbook that will make a difference in the design of systems of all types that are large in scale and/or scope.

This book presents a guide to navigating the complicated issues of quality and process improvement in enterprise software implementation, and the effect these have on the software development life cycle (SDLC). Offering an integrated approach that includes important management and decision practices, the text explains how to create successful automated solutions that fit user and customer needs, by mixing different SDLC methodologies. With an emphasis on the realities of practice, the book offers essential advice on defining business requirements, and managing change. This revised and expanded second edition includes new content on such areas as cybersecurity, big data, and digital transformation. Features: presents examples, case studies, and chapter-ending problems and exercises; concentrates on the skills needed to distinguish successful software implementations; considers the political and cultural realities in organizations; suggests many alternatives for how to manage and model a system.

THE PROJECT MANAGER’S GUIDE TO MASTERING AGILE Updated guide to Agile methodologies, with real-world case studies and valuable frameworks for project managers moving to Agile The Project Manager’s Guide to Mastering Agile helps project managers who are faced with the challenge of adapting their project management approach to an Agile environment, showing how these approaches can work jointly to improve project outcomes in any project, with discussion topics and real-world case studies that facilitate hands-on learning. It also provides project managers with the fundamental knowledge to take a leadership role in working with companies to develop a well-integrated, enterprise-level Agile Project Management approach to fit their business. The original edition of this book has been very successful and is used as a graduate-level textbook in several universities. This new edition builds on the success of the original edition and includes updated content from the latest PMBOK Guide, updated sections on stakeholder management, value-driven delivery, adaptive planning, and distributed project management, with an all-new chapter on Hybrid project management. It also includes new case studies on applying an Agile Hardware Development at Tesla and Project Management in a non-software environment. Sample topics covered in The Project Manager’s Guide to Mastering Agile include: Bridging the chasm in project management philosophies, impact on the project management profession, evolution of Agile and Waterfall, and learning to see Agile and traditional plan-driven project management as complementary to each other rather than competitive The roots of Agile and understanding Agile at a deeper level including the Agile manifesto from 2001, adapting an Agile approach to fit a business, and Scrum overview, roles, framework, principles, and values Time-boxing, Kanban, and theory of constraints, Agile estimation overview and estimation practices, and velocity and burn-down/burn-up charts Scaling Agile to an enterprise level, including challenges, obstacles to overcome, implementation considerations, management practices, and enterprise-level Agile transformations With comprehensive, accessible, and highly practical coverage of Agile, a leading project management platform, The Project Manager’s Guide to Mastering Agile is a highly valuable resource for professional project managers, students studying project management, and those studying for PMI’s Agile Certified Practitioner Certification (PMI-ACP).

This book focuses on providing information on project management specific for software implementations within the healthcare industry. It can be used as a guide for beginners as well as a reference for current project managers who might be new to software implementations. Utilizing the Project Management Institute’s (PMI) methodology, process groups and knowledge areas are defined as they relate to implementing custom and commercial off-the-shelf (COTS) software. The Software Development Life Cycle (SDLC) is a standard for developing custom software, but can also be followed for implementing COTS applications as well. How will the system be set up from an architecture and hardware standpoint? What environments will be needed and why? How are changes managed throughout the project and after? These questions and more will be reviewed. The differences between types of testing are defined as well as when each are utilized. Planning for the activation and measuring the success of the project and how well the strategic need has been met are key activities that are often not given the time and effort as the other parts of the implementation project. This new edition updates the current content to better align with the newest version of the PMI’s Project Management Body of Knowledge (PMBOK), as well as the latest technology and concepts. In addition, this new edition includes additional chapters on agile management, stakeholder management, and choosing the right methodology.

Equip yourself with SOFTWARE PROJECT SURVIVAL GUIDE. It's for everyone with a stake in the outcome of a development project--and especially for those without formal software project management training. That includes top managers, executives, clients, investors, end-user representatives, project managers, and technical leads. Here you'll find guidance from the acclaimed author of the classics CODE COMPLETE and RAPID DEVELOPMENT. Steve McConnell draws on solid research and a career's worth of hard-won experience to map the surest path to your goal--what he calls "one specific approach to software development that works pretty well most of the time for most projects." Nineteen chapters in four sections cover the concepts and strategies you need for mastering the development process, including planning, design, management, quality assurance, testing, and archiving. For newcomers and seasoned project managers alike, SOFTWARE PROJECT SURVIVAL GUIDE draws on a vast store of techniques to create an elegantly simplified and reliable framework for project management success. So don't worry about wandering among complex sets of project management techniques that require years to sort out and master. SOFTWARE PROJECT SURVIVAL GUIDE goes straight to the heart of the matter to help your projects succeed. And that makes it a required addition to every professional's bookshelf.

CD-ROM contains samples of software packages.