scaling agile
You Can’t Rush Agile Change Too often, organizations try to rush agile change. It is usually because they want to see the business benefits of agile as quickly as possible. Unfortunately, change doesn’t work like that—you can’t rush it. In fact, trying to change too fast often results in no change at all. Here are some examples to avoid. |
||
Scaling Product Agility: More Product, Not More Process Focusing on scaling product discovery that feeds product delivery is valuable to scaling frameworks. A cross-team product discovery cadence highlights work that's valuable to everyone and facilitates workflow for all the teams, helping them produce more of what they really need (and less of what they don’t). |
||
The Secret Recipe for Scaling Agile Projects Based on his own experience in delivering a large-scale agile project, Venkatesh Krishnamurthy shares with us a secret recipe for scaling agile projects. Apart from team size, tailoring practices to accommodate scaling plays a key role for successful implementation. |
||
Is a Framework Needed to Scale Agile? There are varying reactions to using frameworks to scale agile. One concern surrounding the rise of SAFe and DAD is the creation of new methods that are compared with or pitted against existing sets of techniques, fragmenting the agile community. Do you really need a framework to scale agile? |
||
Are You Getting Everything You Need from Your Infrastructure? Culture may be vital to the success of agile, but there are a number of technical requirements that must be in place for development teams to be able to bring the speed and quality that agile was designed to deliver. Nate Odell looks specifically at the needs of an agile infrastructure. |
||
How to Scale Agile for Larger Teams and Organizations Agile seems suited for smaller teams because of less bureaucracy and management overhead. So how do you implement, run, and achieve success with agile in larger efforts? The success or failure of scaling agile to large teams is based on your organization’s maturity as it applies to agile. |
||
Tips for Scaling Agile Development It used to be normal to hear that agile projects should be small in both time frame and team size. Now, it seems conventional wisdom dictates that we should be scaling agile. But how do you go about doing this? Mukesh Chaudhary lists some useful tips to scale efficiently. |
||
Moving Beyond a Superficial Understanding of Agile While agile is almost universally hailed, the majority of executives only have a "superficial" understanding of the methodology. Steve Vaughn explains that this level of understanding by upper management is a serious impediment to the necessary culture change that needs to take place. |