All of the agile cards have been pulled, and nonetheless new products still do not get faster to the market. If this situation seems familiar, you should read this story about a company that prepared their agile transition in exemplary fashion: 600 employees reorganized into cross-functional teams, their work visualized and practically perfect Standups and Retrospectives held. The result: Time-to-Market for the products became worse - and not a trace of business agility.This book shows you what goes wrong with many agile transitions and why the desired improvements fail to materialize. You also learn how to get out of a dead end and what can be done before starting a transformation in order to prevent heading down a dead end to begin with.A little preview: Do not start by making teams agile - this will save your nerves and lots of money!

As organizations strive to meet stringent budgets, the mandate to produce greater results with fewer resources is no longer sufficient. Rather than accepting less, managers and executives must strive for better--evaluating every process and every role and doing away with assumptions about how work gets done and who does it in order to streamline processes and maximize efficiency. William Rothwell, who was honored with the ASTD Distinguished Contribution Award in Workplace Learning and Peformance, presents a system for analyzing work and selecting the ideal combination of cost-effective resources--employees, consultants, contractors, temporary workers, and vendors--to accomplish it. Lean but Agile does this by teaching readers to focus on outcomes and work backwards--exploring the introduction, implementation, and management of lean work and agile staffing methods that will produce those outcomes. You’ll also learn about advantageous changes in hiring, goal-setting, learning and development, and performance management, and the fundamental role technology can play in transforming your processes. Packed with practical advice, examples, guides, worksheets, diagrams, and metrics, Lean but Agile will help leaders, managers, and human resource professionals optimize their workforces while still achieving superior results.

Agile Strategy is a practical guide for managers responsible for setting the strategic direction of their organisations in increasingly dynamic markets. Through its frameworks, tools and real-world examples, it explains how to transform business performance through greater organisational agility. LEADERSHIP AND MANAGEMENT STRATEGY BUSINESS TRANSFORMATION Why do we need a new book on strategy? The pace of change is increasing, and strategic management is not keeping up. More than one in four (28%) strategic initiatives fail to meet their original goals and business intent[1], with insufficient agility identified as one of the top three barriers to successful strategy implementation[2]. The square peg of traditional strategy — vision, mission and blue-sky exercises; the separation of strategy from “implementation” — no longer fits the round hole of increasingly dynamic markets. It is time for a new approach. How is Agile Strategy different? Agile Strategy distinguishes itself from other strategy and agile books currently available in that it is: Designed for large organisations: Much of the writing on agile techniques addresses start-ups or small and medium-sized enterprises (SMEs), which operate under very different constraints and freedoms. Agile Strategy is written for large organisations who want to be more agile. Commercially-led: The approach is not a lightly airbrushed business rewrite of agile software development practices, but rather a fundamental rethinking of commercial and operational business practices. Practical: It is anchored in innovative and robust concepts but designed as a practical “how-to” guide: a book for practitioners, written by a practitioner. Results-focused: Whilst addressing a broad range of organisational topics, the book is grounded in the definition and delivery of measurable business benefits. Why should I read it? Agile Strategy offers four key benefits to its readers: A clear framework ("RADAR") A single, easy-to-grasp guiding principle: The Horizon Measurable benefits A practical approach I hope you not only enjoy reading about this innovative new approach, but also go on to realise the full potential of your organisation by implementing it. Good luck! Ralph Fernando [1] Project Management Institute (2017) Pulse of the Profession [2] The Economist Intelligence Unit (2017) Closing the Gap: Designing and Delivering a Strategy that Works"

In this comprehensive yet accessible overview for software leaders, the author presents an impactful, action-oriented prescription-covering the practical considerations needed to ensure you reap the full benefits of effective Agile

Get the most out of this foundational reference and improve the productivity of your software teams. This open access book collects the wisdom of the 2017 "Dagstuhl" seminar on productivity in software engineering, a meeting of community leaders, who came together with the goal of rethinking traditional definitions and measures of productivity. The results of their work, Rethinking Productivity in Software Engineering, includes chapters covering definitions and core concepts related to productivity, guidelines for measuring productivity in specific contexts, best practices and pitfalls, and theories and open questions on productivity. You'll benefit from the many short chapters, each offering a focused discussion on one aspect of productivity in software engineering. Readers in many fields and industries will benefit from their collected work. Developers wanting to improve their personal productivity, will learn effective strategies for overcoming common issues that interfere with progress. Organizations thinking about building internal programs for measuring productivity of programmers and teams will learn best practices from industry and researchers in measuring productivity. And researchers can leverage the conceptual frameworks and rich body of literature in the book to effectively pursue new research directions. What You'll LearnReview the definitions and dimensions of software productivity See how time management is having the opposite of the intended effect Develop valuable dashboards Understand the impact of sensors on productivity Avoid software development waste Work with human-centered methods to measure productivity Look at the intersection of neuroscience and productivity Manage interruptions and context-switching Who Book Is For Industry developers and those responsible for seminar-style courses that include a segment on software developer productivity. Chapters are written for a generalist audience, without excessive use of technical terminology.

Digital tools have long been a transformative part of academia, enhancing the classroom and changing the way we teach. Yet there is a way that academia may be able to benefit more from the digital revolution: by adopting the project management techniques used by software developers. Agile work strategies are a staple of the software development world, developed out of the need to be flexible and responsive to fast-paced change at times when “business as usual” could not work. These techniques call for breaking projects into phases and short-term goals, managing assignments collectively, and tracking progress openly. Agile Faculty is a comprehensive roadmap for scholars who want to incorporate Agile practices into all aspects of their academic careers, be it research, service, or teaching. Rebecca Pope-Ruark covers the basic principles of Scrum, one of the most widely used models, and then through individual chapters shows how to apply that framework to everything from individual research to running faculty committees to overseeing student class work. Practical and forward-thinking, Agile Faculty will help readers not only manage their time and projects but also foster productivity, balance, and personal and professional growth.

Estimating software development often produces more angst than value, but it doesn't have to. Identify the needs behind estimate requests and determine how to meet those needs simply and easily. Choose estimation techniques based on current needs and available information, gaining benefit while reducing cost and effort. Detect bad assumptions that might sink your project if you don't adjust your plans. Discover what to do when an estimate is wrong, how to recover, and how to use that knowledge for future planning. Learn to communicate about estimates in a healthy and productive way, maximizing advantage to the organization and minimizing damage to the people. In a world where most developers hate estimation and most managers fear disappointment with the results, there is hope for both. It requires giving up some widely held misconceptions. Let go of the notion that "an estimate is an estimate" and estimate for the particular need you, and your organization, have. Realize that estimates have a limited shelf-life, and reestimate frequently if it's important. When reality differs from your estimate, don't lament; mine that disappointment for the gold that can be the longer-term jackpot. Estimate in comparison to past experience, by modeling the work mathematically, or a hybrid of both. Learn strategies for effective decomposition of work and aspects of the work that likely affect your estimates. Hedge your bets by comparing the results of different approaches. Find out what to do when an estimate proves wrong. And they will. They're estimates, after all. You'll discover that you can use estimates to warn you of danger so you can take appropriate action in time. Learn some crucial techniques to understand and communicate with those who need to understand. Address both the technical and sociological aspects of estimation, and you'll help your organization achieve its desired goals with less drama and more benefit. What You Need: No software needed, just your past experience and concern for the outcomes.

Agile is broken. Most Agile transformations struggle. According to an Allied Market Research study, "63% of respondents stated the failure of agile implementation in their organizations." The problems with Agile start at the top of most organizations with executive leadership not getting what agile is or even knowing the difference between success and failure in agile. Agile transformation is a journey, and most of that journey consists of people learning and trying new approaches in their own work. An agile organization can make use of coaches and training to improve their chances of success. But even then, failure remains because many Agile ideas are oversimplifications or interpreted in an extreme way, and many elements essential for success are missing. Coupled with other ideas that have been dogmatically forced on teams, such as "agile team rooms", and "an overall inertia and resistance to change in the Agile community," the Agile movement is ripe for change since its birth twenty years ago. "Agile 2" represents the work of fifteen experienced Agile experts, distilled into Agile 2: The Next Iteration of Agile by seven members of the team. Agile 2 values these pairs of attributes when properly balanced: thoughtfulness and prescription; outcomes and outputs, individuals and teams; business and technical understanding; individual empowerment and good leadership; adaptability and planning. With a new set of Agile principles to take Agile forward over the next 20 years, Agile 2 is applicable beyond software and hardware to all parts of an agile organization including "Agile HR", "Agile Finance", and so on. Like the original "Agile", "Agile 2", is just a set of ideas - powerful ideas. To undertake any endeavor, a single set of ideas is not enough. But a single set of ideas can be a powerful guide.

A breakthrough approach to managing agile software development, Agile methods might just be the alternative to outsourcing. However, agile development must scale in scope and discipline to be acceptable in the boardrooms of the Fortune 1000. In Agile Management for Software Engineering, David J. Anderson shows managers how to apply management science to gain the full business benefits of agility through application of the focused approach taught by Eli Goldratt in his Theory of Constraints. Whether you're using XP, Scrum, FDD, or another agile approach, you'll learn how to develop management discipline for all phases of the engineering process, implement realistic financial and production metrics, and focus on building software that delivers maximum customer value and outstanding business results.Coverage includes: Making the business case for agile methods: practical tools and disciplines How to choose an agile method for your next project Breakthrough application of Critical Chain Project Management and constraint-driven control of the flow of value Defines the four new roles for the agile manager in software projects—and competitive IT organizations Whether you're a development manager, project manager, team leader, or senior IT executive, this book will help you achieve all four of your most urgent challenges: lower cost, faster delivery, improved quality, and focused alignment with the business.

Enterprise Agility is practical framework for enhancing Agility and equipping your company with the tools to survive. Key Features Prepare your company to navigate the rapidly-moving business world Enhance Agility in every component of your organization Build a framework that meets the unique requirements of your enterprise Book Description The biggest challenge enterprises face today is dealing with fast-paced change in all spheres of business. Enterprise Agility shows how an enterprise can address this challenge head on and thrive in the dynamic environment. Avoiding the mechanistic construction of existing enterprises that focus on predictability and certainty, Enterprise Agility delivers practical advice for responding and adapting to the scale and accelerating pace of disruptive change in the business environment. Agility is a fundamental shift in thinking about how enterprises work to effectively deal with disruptive changes in the business environment. The core belief underlying agility is that enterprises are open and living systems. These living systems, also known as complex adaptive systems (CAS), are ideally suited to deal with change very effectively. Agility is to enterprises what health is to humans. There are some foundational principles that can be broadly applied, but the definition of healthy is very specific to each individual. Enterprise Agility takes a similar approach with regard to agility: it suggests foundational practices to improve the overall health of the body—culture, mindset, and leadership—and the health of its various organs: people, process, governance, structure, technology, and customers. The book also suggests a practical framework to create a plan to enhance agility. What you will learn Drive agility-oriented change across the enterprise Understand why agility matters (more than ever) to modern enterprises Adopt and influence an Agile mindset in your teams and in your organization Understand the concept of a CAS and how to model enterprise and leadership behaviors on CAS characteristics to enhance enterprise agility Understand and convey the differences between Agile and true enterprise agility Create an enterprise-specific action plan to enhance agility Become a champion for enterprise agility Recognize the advantages and challenges of distributed teams, and how Agile ways of working can remedy the rough spots Enable and motivate your IT partners to adopt Agile ways of working Who this book is for Enterprise Agility is a tool for anyone with the motivation to influence outcomes in an enterprise, who aspires to improve Agility. Readers from the following backgrounds will benefit: chief executive officer, chief information officer, people/human resource director, information technology director, head of change program, head of transformation, and Agile coach/consultant.