Do you have a nagging feeling that your Scrum team may not be investing in building the right thing? Do your products have features that are rarely or never used? Does it take your organization the full investment of building and launching a product to validate an idea?
After many years of working with Agile and being a witness to its results, we found the main mistakes (the dark side) that usually come up when implementing this methodology. Take a look at some of the reasons why Scrum fails within the software development projects.
There is often a vacuum between the company vision and the final outcome of software development projects, causing late validation and low value. This vacuum is present in pretty much all companies, caused by a wrong and ill-conceived product delivery approach.
How should you actually implement Continuous Delivery in Scrum projects? This video explains how easy it is for a Continuous Delivery implementation to be unsuccessful, how the Theory Of Constraints works, how to apply the Five Focussing Steps to Continuous Delivery, and how to home in on the constrained activities that are your keys to success.
Even if Scrum is the most popular Agile framework used in software development, it is not the only approach you can use. In this article, Mark Haynes discusses why you might consider Lean Kanban as a better approach for your organization.
This presentation explain the difference between the two terms effectiveness and efficiency and show how focusing on the latter in Agile can lead to multiple bad consequences that you will probably recognize from organizations in your field.
Agile Arizona is a conference for Scrum, Agile, Kanban and Lean practitioners and coaches organized by the Phoenix Scrum User Group in Arizona that consists of workshops and presentations. One of the primary goals of the conference is to help foster Agile education, personal growth, and a sense of community within Phoenix and Arizona.
Scrum Expert Copyright © 2009-2024 Martinig & Associates