Rethinking Agile

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.

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.

Agile Project Delivery reviews how different Agile methods can be applied to project delivery in complex corporate environments beyond the Agile Manifesto’s original scope of software development. Taking readers through a typical project lifecycle, the text demonstrates how Agile techniques can be applied to each phase of a project using valuable tools and examples. Agile Project Delivery covers various approaches that are used across the many methodologies and frameworks that are part of the Agile family, including Scrum, XP, and Crystal, as well as some of Agile’s influences, such as Lean and Kanban. Agile Project Delivery also provides readers with advanced instructions for using Atlassian’s industry-leading Agile software, Jira. Bridging the gap between Agile methodology and application, this concise guide features practical delivery approaches, engaging case studies, useful templates to assist in Agile application, and chapter discussion questions to reinforce understanding on how to harness the benefits of Agile. With a focus on settings outside of software development and an accessible, pragmatic approach, Agile Project Delivery is an invaluable resource for students in any project management course, as well as for both aspiring and experienced project practitioners.

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"

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.

The first book to cover Agile Modeling, a new modeling technique created specifically for XP projects eXtreme Programming (XP) has created a buzz in the software development community-much like Design Patterns did several years ago. Although XP presents a methodology for faster software development, many developers find that XP does not allow for modeling time, which is critical to ensure that a project meets its proposed requirements. They have also found that standard modeling techniques that use the Unified Modeling Language (UML) often do not work with this methodology. In this innovative book, Software Development columnist Scott Ambler presents Agile Modeling (AM)-a technique that he created for modeling XP projects using pieces of the UML and Rational's Unified Process (RUP). Ambler clearly explains AM, and shows readers how to incorporate AM, UML, and RUP into their development projects with the help of numerous case studies integrated throughout the book. AM was created by the author for modeling XP projects-an element lacking in the original XP design The XP community and its creator have embraced AM, which should give this book strong market acceptance Companion Web site at www.agilemodeling.com features updates, links to XP and AM resources, and ongoing case studies about agile modeling.

The Kanban board is constructed, the swim lanes are drawn and the blockade stickers are positioned. Now what? Kanban is not able to reach its full potential in many companies. Often, the meaning behind the individual practices, such as WIP limits, is not correctly understood. All hope is placed in a method instead of actions. Kanban helps uncover the weak points in a work system, and as a result, reveals how to better generate value for the customer. This book can help in tweaking an existing Kanban system, as well as expand your own repertoire of solutions. Klaus Leopold describes in detail the principles and functionality of Kanban, which are not always intuitive. He discusses typical problems that he has observed in his work with real-world Kanban systems. Klaus illustrates the possibilities that exist when the entire value creation chain of a company is taken into account and how tools such as Cost of Delay and forecasting can become strategic aids. Thus, it should become clear that Kanban is not a team method, but rather a method for improvement that considers the entire value creation chain of a company.