Summary of Why Isn’t Agile Working?

Looking for the article?
We have the summary! Get the key insights in just 5 minutes.

Why Isn’t Agile Working? summary

Rating

7 Overall

7 Applicability

6 Innovation

8 Style

Recommendation

Agile project management techniques have the potential to help companies develop software focused on their customers’ needs in less time and with less waste than the old approaches. But as author John Cutler points out in this short, illustrated read from Hackernoon, agile isn’t a magic pill that will fix an organization’s productivity woes on its own. getAbstract recommends this short post as a starting point for those who may be considering an agile implementation but aren’t sure what to expect.

In this summary, you will learn

  • Why agile alone cannot improve software delivery results and the bottom line,
  • Which key concepts organizations need to master in order to make agile a worthwhile endeavor,
  • How learning to work on the right projects is vital to the success of every organization.
 

About the Author

John Cutler is a product development expert and a frequent technical contributor to Hackernoon and Medium.

 

Summary

Over the past couple of decades, many software companies and IT departments have realized that development rarely proceeds in a straight line from initial requirements to finished product. As teams struggled with changing requirements and grumbling customers, firms searched for more efficient ways to keep up with ever-evolving specifications and expectations. Against this backdrop of confusion and frustration, agile project management techniques emerged as a new approach to tackle the challenges that modern technology projects present.

Comment on this summary

More on this topic

Customers who read this summary also read

More by category