Professional Documents
Culture Documents
Why Isnt Agile Working Cutler en 31789
Why Isnt Agile Working Cutler en 31789
Why Isnt Agile Working Cutler en 31789
Rating ? Qualities ?
Analytical
Overview
For Beginners
Take-Aways
• Agile has become a project management buzzword that many companies grab onto in the name of
enhanced productivity.
• The agile framework alone can’t fix underlying problems with company culture or values.
• The key to making agile, or any other process, as effective as possible is first to identify the right problems
to work on at the right times.
• Once agile is adopted, organizations must guard against unplanned work or multitasking.
• The ultimate goal of agile, or any other adopted methodology, must be the realization of defined benefits.
1 of 3
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.
Yet as agile has grown from a grassroots movement focused on better, more targeted software into a
mainstream approach embraced by companies of all sizes and in all industries, the methodologies have lost
some of their shine. In a typical scenario, management reads about the wonders of agile and champions its
adoption, complete with training, tools and maybe even new staff. Then, after months of hand-wringing
and project meetings, company leaders panic when projects aren’t completed on time. Frustrated that agile
didn’t deliver on its promise, the company changes course again.
“Address sources of unplanned work, and quantify the economic impact of having a
shared service.”
But often times, the problem lies not with agile itself but with the underlying culture of the organization and
the expectation that a new process can fix problems that may have been festering for years. Compounding
the problems is a failure to account for characteristics inherent to most projects, such as time spent
waiting for approvals, testing or sign-off on requirements. Portfolio managers can mitigate much of that lost
time by diligently lining up multiple projects, but they need strong buy-in and support from management.
Even the most bulletproof plans can take a hit when unexpected work arises, as it usually does, and
increasingly complex systems can sap developer productivity. In order to squeeze the most out of agile,
companies need to factor all these perturbations into their implementation and give project management the
means and authority to mitigate them. Above all, organizations must ruthlessly focus on the projects that are
most meaningful to their mission and then commit the resources necessary to finish them, agile or not.
www.getabstract.com
2 of 3
3 of 3