One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor. The authors provide insight into the underlying causes of business value risk and provide ten tips on how to avoid them.
Continuing the series of interviews with Stoos Network Event participants, Shane Hastie spoke to Catherine Louis and Deborah Hartmann Preuss about their experiences at the event and their hopes and expectations for the future of the Stoos Network. The Stoos Network aims to encourage shift in organisational management from traditional hierarchical leadership toward more collaborative approaches.
Interruptions are something that every team has to deal with and, if not managed appropriately, they can potentially have a detrimental affect on their ability to deliver. In a recent post on the Agile Advice blog, Mishkin Berteig described seven options that teams could consider to deal with interruptions when using Scrum or iterative Agile approaches.
This article shows how automating certain programmable aspects of a test suite can help software delivery. Covered are automated testing, costs per deployment, tests as documentation & manual testing.
Risk management is the hottest topic in IT. Processes for effective risk management and investment decision making will allow Agile techniques to scale beyond projects to the enterprise. Without them, Agile will be confined to the ghetto of development. In this article Chris and Olav present some tools and techniques to identify and manage risks on Agile projects.
In this presentation Don Reinertsen examines some key lean methods including queue management, batch size reduction, WIP constraints, and cadence. He also discusses the governing economic tradeoffs and how these methods can be exploited by product developers.
Nanjangud C Narendra presents a case study of an enterprise Agile project in the light of Lehman’s laws of software evolution, along with observations on Agile practices used and their outcome.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Does success at the team level always result in success at the organization level? Sanjiv Augustine and Arlen Bankston discuss the Seven Deadly Sins that organizations repeatedly make so you can steer clear of them and benefit from a successful Enterprise Agile Adoption.
In Agile, adoption and transformation are typically viewed as one big event. Mike Cottmeyer provides a holistic perspective that looks as adoption as the implementation of practices, and transformation along two dimensions, organizational and personal. Mike discusses how they are a means to an end, and how to avoid the trap of focusing on practice adoption as a goal.
This mini-book offers an easy to follow 10 step guide to taking the initial plunge and start using Lean principles to optimizing value and flow in your system. Each step consists of a section explaining “why” followed by examples of specific tools, practices and rules that have helped other teams better understand and optimize their system.
This book guides the reader on crafting their own agile adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted them. Business values are also a component of these patterns so your adoption is always focused on addressing your particular environment.
