3 Ways the Agile Methodology Is Implemented Incorrectly

Posted by Patricia Block

Oct 19, 2015 5:30:44 PM Agile

The key to Agile methodology is ‘selling’ Agile methodology by promising solutions to age old IT concerns: projects that run over budget and time, lack of project team effectiveness, lack of real collaboration, poor product quality and dissatisfied customers.

I've been involved in a number of Agile project disputes and have concluded that Agile, the methodology itself, is not what failed but rather its utilization and implementation. 

3 Ways the Agile Methodology Is Implemented Incorrectly

The Agile methodology produces the promised effects when the professional services team understands proper implementation. Without it, the following can result:

1) Delivery over Quality

The Agile principle of "early and continuous delivery of valuable software" which focuses on continuous delivery can have the effect of creating an unmanageable defect backlog while developers focus on providing deliverables to the customer. With proper implementation of Agile methodology, such defects become part of the backlog which ultimately makes their way into a sprint.

2) Development over Planning

In theory, developers code while collaborating with stakeholders to define, refine and change requirements as the project goes along. The Agile methodology, however, does not distinguish between material and minor changes with every change having a cost. With proper implementation of Agile methodology, material changes are made throughout the project so that sprints can be added, which incorporate the backlog instead of material changes being added at the end, making the code harder to fix.

3) Collaboration over Management

Agile emphasizes teams that collaborate in a group evolutionary manner which can appear to be inconsistent with responsible management. With proper implementation of Agile methodology, a product owner, team and scrum master allow the project to evolve with accountable stakeholders at the helm.

In Conclusion

When Agile methodology is not implemented properly, it can result in non-specific requirements, hidden actual cost of development and prevention of effective management. Contrary to what Agile methodology inherently promotes, the result can be long-running projects, dissatisfied customers and an overall IT ineffectiveness.

And thus the dispute between IT vendor and customer begins…

That’s why Agile Strategies was born. Agile Strategies can help (a) perform project forensics, (b) interpret the contractual requirements and (c) introduce remedies to bridge the stopgap in order to enable the project to get back on track and proceed toward completion.  Our strategic partnership with Vizuri brings to the table a combination of their years of experience delivering solutions and mentoring clients in the Agile methodology with legal forensics from Agile Strategies.   

Are you stuck in an Agile project gone wrong? Contact us today to schedule a complimentary consultation. Together with Vizuri, Agile Strategies has the experience and expertise necessary to get your project back on track. 

Posted by Patricia Block

Patricia brings nearly 20 years of legal experience in business and information technology which has allowed her to develop a proprietary process, combining legal and project management forensics, that enables customers to get their projects back on track.

Find me on:


Posts by Topic

see all
Request a Complimentary Docker Consultation

An Open View

Vizuri Blog

Subscribing to our blog is a great way to stay up to date with the latest information from Vizuri, as well as our strategic partners. We focus on providing a range of content that is practically useful and relevant from both a technical and business perspective.

We promise to respect your privacy.