It’s time to extend the benefits of Scrum—greater agility, higher-quality products, and lower costs—from individual teams to your entire enterprise. However, with Scrum’s lack of prescribed rules, the friction of change can be challenging as people struggle to break from old project management habits. In this book, agile-process revolution leader Ken Schwaber takes you through change management—for your organizational and interpersonal processes—explaining how to successfully adopt Scrum across your entire organization. A cofounder of Scrum, Ken draws from decades of experience, answering your questions through case studies of proven practices and processes. With them, you’ll learn how to adopt—and adapt—Scrum in the enterprise. And gain profound levels of transparency into your development processes. Discover how to: Evaluate the benefits of adopting Scrum in any size organization Initiate an enterprise transition project Implement a single, prioritized Product Backlog Organize effective Scrum teams using a top-down approach Adapt and apply solutions for integrating engineering practices across multiple teams Shorten release times by managing high-value increments Refine your Scrum practices and help reduce the length of Sprints
Diplomarbeit aus dem Jahr 2011 im Fachbereich Informatik - Wirtschaftsinformatik, Note: 1,3, Hochschule Darmstadt, Sprache: Deutsch, Abstract: Thema: Erarbeitung eines Vorgehensmodells zur Einfuhrung von Scrum in Grossunternehmen Autor: Tino Volbracht Deskriptives Abstract - Deutsch Eine Einfuhrung von Scrum in Grossunternehmen, mit der Absicht das gesamte Potential von Scrum auszuschopfen, ist weitreichend und bedeutet tiefgreifende Verhaltensanderungen fur viele Mitarbeiter. Der organisatorische Wandel von traditionellen Vorgehensweisen im Bereich des Software-Engineering hin zu Scrum und die damit notwendigen Anderungen von Gewohnheiten und Arbeitsweisen werden hochstwahrscheinlich bei vielen Mitarbeitern auf Widerstand stossen, so dass das Vorhaben als riskant beschrieben werden kann und dessen Umsetzung geplant und gezielt gesteuert werden sollte. Aktuell existiert kein integratives Vorgehensmodell, welches eine Einfuhrung von Scrum in Grossunternehmen beschreibt und zeitgleich einen organisatorischen Wandel angemessen berucksichtigt, so dass hier Nachholbedarf besteht. Auf Basis des Anderungsmanagement-Modells Eight-Stage Process' von John P. Kotter und des Enterprise Transition Process' von Ken Schwaber wird ein integratives Vorgehensmodell entworfen, um das Risiko eines Scheiterns zu minimieren. Dazu werden die zu durchlaufenden Schritte sowie die moglichen Handlungsalternativen fur Grossunternehmen im Detail aufgezeigt. Daruber hinaus wird beschrieben, wie mit Widerstanden konstruktiv umgegangen werden kann. Descriptive Abstract - English The introduction of Scrum in big enterprises implicates extensive and drastic changes of attitude for most employees, especially if the potential of Scrum shall be fully utilized. The organisational change from traditional methods of software engineering to Scrum requires changes of habits and working methods and might therefore lead to rejection by many employees. Due to this, the change to Scrum is risky and demands
Succeed with Scrum in Even the Largest, Most Complex Distributed Development Projects Forewords by Ken Schwaber, Scott Ambler, Roman Pichler, and Matthew Wang This is the first comprehensive, practical guide for Scrum practitioners working in large-scale distributed environments. Written by three of IBM’s leading Scrum practitioners—in close collaboration with the IBM QSE Scrum Community of more than 1000 members worldwide—this book offers specific, actionable guidance for everyone who wants to succeed with Scrum in the enterprise. Readers will follow a journey through the lifecycle of a distributed Scrum project, from envisioning products and setting up teams to preparing for Sprint planning and running retrospectives. Each chapter presents a baseline drawn from “conventional” Scrum, then discusses additional issues faced by distributed teams, and presents specific best-practice solutions, alternatives, and tips the authors have identified through hard, empirical experience. Using real-world examples, the book demonstrates how to apply key Scrum practices, such as look-ahead planning in geographically distributed environments. Readers will also gain valuable new insights into the agile management of complex problem and technical domains. Coverage includes Developing user stories and working with Product Owners as a distributed team Recognizing and fixing the flaws Scrum may reveal in existing processes Engaging in more efficient Release and Sprint planning Conducting intense, brief daily Scrum meetings in distributed environments Managing cultural and language differences Resolving dependencies, performing frequent integration, and maintaining transparency in geographically distributed environments Successfully running remote software reviews and demos Brainstorming what worked and what didn’t, to improve future Sprints This book will be an indispensable resource for every team leader, member, product owner, or manager working with Scrum or other agile methods in any distributed software development organization.
Scrum in der Praxis einführen und leben Boris Gloger beschreibt leicht verständlich die Werte, Regeln, Strukturen und Rollen von Scrum. Egal ob Sie als Kunde, Führungskraft, ScrumMaster, Product Owner oder Teammitglied an einem Scrum-Projekt beteiligt sind oder aber erst wissen wollen, was Scrum eigentlich ist: - Sie erfahren, wie Teams durch weitgehende Selbstorganisation und kontinuierliches Planen Produkte schneller und erfolgreicher liefern können. - Umfassend wird dargestellt, wie Scrum mit mehreren Teams, die über viele Standorte verteilt sind, eingesetzt wird. - Zudem ist dieses Praxisbuch eine hervorragende Unterstützung für die Zertifizierung zum ScrumMaster. Hier erhalten Sie einen umfassenden Überblick und wertvolle Tipps, wie Sie Scrum in der Praxis einführen und leben können.
The future of business will be determined by its effectiveness in performing knowledge-based work. Scrum has proven itself in one exceptionally important form of knowledge-based work: software development. Now, Enterprise Scrum is increasingly proving itself in large-scale knowledge work of all kinds: not just software development, but team and multi-team projects and business processes at all levels, including enterprise-wide. In this book, Scrum/agile pioneer Mike Beedle introduces Enterprise Scrum, and demonstrates how to apply it to achieve unprecedented levels of productivity and transparency across your organization. Beedle begins with the big picture, introducing Scrum from the standpoint of knowledge-based decision-makers and process owners. Next, he systematically introduces powerful techniques for applying and scaling Scrum in new environments, both within the enterprise and beyond to clients/customers, service providers, suppliers, and even to SaaS and mobile platforms. Drawing on his extensive “in the trenches” experience, Beedle presents patterns for successfully utilizing Enterprise Scrum, and walks through several start-to-finish case studies -- in software development, marketing, operational strategy, and product development. The techniques he presents in this book are applicable in a wide range of industries, from pharmaceuticals to fashion to finance, and are relevant in any business process where knowledge, creativity, and change come together.
Discover how to implement and operate in an Agile manner at every level of your enterprise and at every point from idea to delivery. Learn how Agile-mature organizations adapt nimbly to microchanges in market conditions. Learn cutting-edge practices and concepts as you extend your implementation of Agile through the entire enterprise to meet customer needs. Veteran Agile coach Mario Moreira argues that two critical conditions must be conscientiously cultivated at a company before it can expect to reap in full measure the business benefits of mature Agile. First, individuals at every level must be committed to the mindset and the implementation of practices rigorously focused on delivering value to the customer. Second, all employees must be empowered to take ownership. This holistic transformation wrenches the status quo and provokes a strong focus where customers and employees matter. What You'll Learn Establish an idea pipeline to quickly and productively evolve customer value through all levels of the enterprise Incorporate a discovery mindset—experimental, incremental, design, and divergent thinking—and fast feedback loops to increase the odds that what you build aligns more closely to what customer wants Leverage Lean Canvas, personas, story mapping, value stream mapping, Cost of Delay, servant leadership, self-organization, and more to deliver optimum value to customers Use continuous agile budgeting and idea pipelines at the senior levels of the enterprise to enable you to adapt to the speed of the market Reinvent human resources, portfolio management, finance, and many areas of management toward new roles in the enablement of customer value Map a top-to-bottom and end-to-end holistic view of your Agile galaxy to gauge where you are today and where you’d like to go in your Agile future Be truly Agile throughout your enterprise, focused on customer value and employees above all else Who This Book Is For Executives and senior management; sponsors of Agile within a company; ScrumMasters and Agile coaches, champions, and consultants; project management and quality assurance officers (PMOs and AMOs); portfolio managers; product managers and product owners; marketing and business managers; functional, middle, and resource managers; engineering heads and managers; cross-functional engineering/scrum teams; and entrepreneurs and venture capitalists
Enterprise-Scale Agile Software Development is the collective sum of knowledge accumulated during the full-scale transition of a 1400-person organization to agile development—considered the largest implementation of agile development and Scrum ever attempted anywhere in the world. Now James Schiel, a certified Scrum trainer and member of the Scrum Alliance, draws from his experience at the helm of that global four-year project to guide you and your organization through the transition. He lends his insight on how you can use Scrum as an organizational framework and implement XP practices to define how software is written and tested. He provides key information and tools to assess potential outcomes and then make the best corresponding choices in any given situation. Schiel sequences chapters to match typical developmental progression, and in addition to practical guidance, he provides a tool kit from which you can take ideas and select what works for you. Covering quality development practices based on ISO 9001, which help you create consistently high-quality software in a cost-efficient manner, this invaluable resource shows you how to— Improve project management practices and product quality assurance Adopt new management methods and requirements Involve your current customers in development, while inviting new ones Much more than a mere "body of knowledge," this volume goes beyond standardizing agile and Scrum practices. It breaks up the process into manageable tasks, illustrating how to set the stage for the change, plan it, and then initiate it. Using the methods and information presented, any organization should be able to achieve a nearly seamless transition to agile.
“We need better approaches to understanding and managing software requirements, and Dean provides them in this book. He draws ideas from three very useful intellectual pools: classical management practices, Agile methods, and lean product development. By combining the strengths of these three approaches, he has produced something that works better than any one in isolation.” –From the Foreword by Don Reinertsen, President of Reinertsen & Associates; author of Managing the Design Factory; and leading expert on rapid product development Effective requirements discovery and analysis is a critical best practice for serious application development. Until now, however, requirements and Agile methods have rarely coexisted peacefully. For many enterprises considering Agile approaches, the absence of effective and scalable Agile requirements processes has been a showstopper for Agile adoption. In Agile Software Requirements, Dean Leffingwell shows exactly how to create effective requirements in Agile environments. Part I presents the “big picture” of Agile requirements in the enterprise, and describes an overall process model for Agile requirements at the project team, program, and portfolio levels Part II describes a simple and lightweight, yet comprehensive model that Agile project teams can use to manage requirements Part III shows how to develop Agile requirements for complex systems that require the cooperation of multiple teams Part IV guides enterprises in developing Agile requirements for ever-larger “systems of systems,” application suites, and product portfolios This book will help you leverage the benefits of Agile without sacrificing the value of effective requirements discovery and analysis. You’ll find proven solutions you can apply right now–whether you’re a software developer or tester, executive, project/program manager, architect, or team leader.
Summarizes the Agile and Scrum software development method, which allows creation of software in just 30 days.
Dieses Buch soll Projektmanagern, Geschäftsführern und Chefs in KMU den Einstieg in neue Denkweisen und Arbeitsmethoden erleichtern. Scrum soll Unternehmen innovativer werden lassen und neue Arbeits- und Entwicklungsprozesse erleichtern Viele kleine Schritte führen zur Optimierung! Scrum beschreibt auch neue Rollen der Mitarbeiter. Innovativ sein bedeutet neue Produkte auf dem Markt zu etablieren. Als Startpunkt sehen wir Normen wie z.B. die EN 61508. Die klassischen Themen Innovation und Arbeitszufriedenheit werden anhand der Definitionen von Schumpeter dargestellt und eine schnell anwendbare Methode vorgeführt. Und die ungeliebte Dokumentation.... wird auch strukturiert!
Scrum ist ein agiles Projektmanagement-Framework, das sich auf alle Arten der Softwareentwicklung anwenden lässt. Richtig eingesetzt hilft es, Kundenzufriedenheit und Wertschöpfung nachhaltig zu steigern. Roman Pichler vermittelt Ihnen das notwendige Wissen, um Scrum erfolgreich anzuwenden. Er beschreibt das Framework umfassend, systematisch und leicht verständlich. Das Buch wendet sich an Einsteiger in Scrum und agiles Projektmanagement sowie an Fortgeschrittene bzw. an Leser, die sich auf Scrum-Zertifizierungen wie Certified ScrumMaster und Certified Scrum Product Owner vorbereiten.
Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. 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.
Project Management the Agile Way was written for experienced project managers, architects and systems analysts who are comfortable in traditional methods of project management but now need to learn about agile methods for software projects and understand how to make agile work effectively in the enterprise. The methodologies included under the agile umbrella go by many names such as Scrum, XP, Crystal and EVO, to name a few. Project managers will gain practical day-to-day tips and advice on how to apply these practices to mainstream projects and how to integrate these methods with other methodologies used in the enterprise. Key Features: • Offers a review of most of the popular agile and iterative methodologies for project management • Presents practical tips and application advice for how to harmonize agile and iterative methods with mainstream project processes • Describes how earned value can work with non-traditional methods • Explains how to scale agile and iterative methods for enterprise projects • Shows the means to contract and outsource with agile and iterative methods • Provides guidance to build a business case and track post-project benefits
Building upon his earlier book that detailed agile data warehousing programming techniques for the Scrum master, Ralph's latest work illustrates the agile interpretations of the remaining software engineering disciplines: Requirements management benefits from streamlined templates that not only define projects quickly, but ensure nothing essential is overlooked. Data engineering receives two new "hyper modeling" techniques, yielding data warehouses that can be easily adapted when requirements change without having to invest in ruinously expensive data-conversion programs. Quality assurance advances with not only a stereoscopic top-down and bottom-up planning method, but also the incorporation of the latest in automated test engines. Use this step-by-step guide to deepen your own application development skills through self-study, show your teammates the world's fastest and most reliable techniques for creating business intelligence systems, or ensure that the IT department working for you is building your next decision support system the right way. Learn how to quickly define scope and architecture before programming starts Includes techniques of process and data engineering that enable iterative and incremental delivery Demonstrates how to plan and execute quality assurance plans and includes a guide to continuous integration and automated regression testing Presents program management strategies for coordinating multiple agile data mart projects so that over time an enterprise data warehouse emerges Use the provided 120-day road map to establish a robust, agile data warehousing program
Masterarbeit aus dem Jahr 2018 im Fachbereich BWL - Unternehmensführung, Management, Organisation, Note: 1,3, FOM Hochschule für Oekonomie & Management gemeinnützige GmbH, Frankfurt früher Fachhochschule, Sprache: Deutsch, Abstract: Das Vorgehen nach agilen Methoden genießt zurzeit große Aufmerksamkeit. Innerhalb der letzten Jahre hat sich aus einer Idee ein handfester Trend entwickelt, der in immer mehr Unternehmen jeglicher Größe und Branche Anklang findet. Auch die Methodik hat sich stetig weiterentwickelt und wird oft an die spezifischen Bedürfnisse des Anwenders angepasst. Man verbindet mit agilen Methoden wie Scrum eine schnelle Reaktionsfähigkeit auf Probleme, flexible Anpassungen an wechselnde Anforderungen und die Loslösung von starren Projektplänen, die nach ein paar Monaten unter Umständen nicht mehr aktuell sind. Gerade für kleine Unternehmen und kreative Branchen klingt dies nach einem echten Mehrwert. Doch wie kann Scrum in größeren Maßstäben angewandt werden? In großen Unternehmen und Projekten scheint es nicht möglich zu sein, von umfangreicher, langfristiger Planung abzusehen. Welche Methodiken gibt es für Scrum im „large-scale“- Umfeld und wie gehen diese mit dem vermeintlichen Widerspruch um? Eine weitere Herausforderung stellt die Anwendung in vermeintlich konservativen, starren Branchen wie dem Bankensektor dar.Die oben genannten Kriterien harmonieren nicht mit kurzfristigen, reaktionsfreudigen Plänen, wechselnden Erwartungen und unklaren Fertigstellungsterminen. Welche Anwendungsmöglichkeiten gibt es also für Scrum und skalierte Versionen von Scrum in diesem Spannungsfeld? Wo liegen Potentiale und welche Grenzen bilden diese Rahmenbedingungen? Welche Abläufe, Werkzeuge und Methoden aus skalierten Versionen von Scrum sind hier sinnvoll und welche lassen sich nur schwer in die Praxis übertragen? Ist es möglich und sinnvoll, Scaled Scrum in großen Unternehmen der Finanzbranche anzuwenden? Im Rahmen dieser Arbeit sollen diese Punkte näher beleuchtet und beurteilt werden. Anschließend wird eine Gesamtkonzeption erarbeitet, wie Scrum in globalen Unternehmen aus der Finanzbranche angewendet kann. Als Basis dient Fachliteratur aus den Disziplinen Agile Methoden, Scrum und Projektmanagement sowie aktuelle Beiträge aus dem Finanzsektor.
Streamline project workflow with expert agile implementation The Project Management Profession is beginning to go throughrapid and profound transformation due to the widespread adoption ofagile methodologies. Those changes are likely to dramaticallychange the role of project managers in many environments as we haveknown them and raise the bar for the entire project managementprofession; however, we are in the early stages of thattransformation and there is a lot of confusion about the impact ithas on project managers: There are many stereotypes and misconceptions that exist aboutboth Agile and traditional plan-driven project management, Agile and traditional project management principles andpractices are treated as separate and independent domains ofknowledge with little or no integration between the two andsometimes seen as in conflict with each other Agile and "Waterfall" are thought of as two binary,mutually-exclusive choices and companies sometimes try to force-fittheir business and projects to one of those extremes when the rightsolution is to fit the approach to the project It’s no wonder that many Project Managers might beconfused by all of this! This book will help project managersunravel a lot of the confusion that exists; develop a totally newperspective to see Agile and traditional plan-driven projectmanagement principles and practices in a new light as complementaryto each other rather than competitive; and learn to develop anadaptive approach to blend those principles and practices togetherin the right proportions to fit any situation. There are many books on Agile and many books on traditionalproject management but what’s very unique about this book isthat it takes an objective approach to help you understand thestrengths and weaknesses of both of those areas to see how they canwork synergistically to improve project outcomes in anyproject. The book includes discussion topics, real world casestudies, and sample enterprise-level agile frameworks thatfacilitate hands-on learning as well as an in-depth discussion ofthe principles behind both Agile and traditional plan-drivenproject management practices to provide a more thorough level ofunderstanding.
Agile techniques have demonstrated immense potential for developing more effective, higher-quality software. However,scaling these techniques to the enterprise presents many challenges. The solution is to integrate the principles and practices of Lean Software Development with Agile’s ideology and methods. By doing so, software organizations leverage Lean’s powerful capabilities for “optimizing the whole” and managing complex enterprise projects. A combined “Lean-Agile” approach can dramatically improve both developer productivity and the software’s business value.In this book, three expert Lean software consultants draw from their unparalleled experience to gather all the insights, knowledge, and new skills you need to succeed with Lean-Agile development. Lean-Agile Software Development shows how to extend Scrum processes with an Enterprise view based on Lean principles. The authors present crucial technical insight into emergent design, and demonstrate how to apply it to make iterative development more effective. They also identify several common development “anti-patterns” that can work against your goals, and they offer actionable, proven alternatives. Lean-Agile Software Development shows how to Transition to Lean Software Development quickly and successfully Manage the initiation of product enhancements Help project managers work together to manage product portfolios more effectively Manage dependencies across the software development organization and with its partners and colleagues Integrate development and QA roles to improve quality and eliminate waste Determine best practices for different software development teams The book’s companion Web site, www.netobjectives.com/lasd, provides updates, links to related materials, and support for discussions of the book’s content.

Best Books