Why Agile Is Failing in Large Enterprises, And What You Can Do About It

Editor's Notes

• #4: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #5: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #6: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #7: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #9: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #10: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #11: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #12: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #14: Matrixed management Non-instantly available resources Project funding models Limited access to subject matter expertise Shared requirements between teams Technical debt Defects Tightly coupled architectures
• #16: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #17: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #18: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
• #19: 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.