Skip to main content

What Agile is Not

 



Agile is a methodology to manage a project that uses iterative and incremental approaches during project execution. Organizations across the globe have been using agile to boost their project success. While Agile is widely used, there are several misconceptions related to the methodology.

Due to its flexibility, people often relate agile with a lack of planning or structure. While it is essential to understand what agile is, it is also crucial to understand what agile is not. This is the area that we will focus upon in this iteration of agile learning.

1. Not a Silver Bullet

Like all other project management methodologies and techniques, agile does not guarantee the success of the project. Project executed along agile principles can also fail and face issues like missed deadlines, over budgeting, and changed requirements. Like any other project management methodologies, it is essential in agile project management to bring the development team and the client close and provide all the indispensable resource to the development team.

 

2. Not Anti-Documentation

Agile manifesto values working software over comprehensive documentation. However, this has led to the misinterpretation that agile is anti-documentation. This is not correct. A better way to put it would be that agile does not prefer documentation just for the sake of creating documents. While agile pushes back on documentation, it identifies it as an essential model of communication.

 

3. Not Anti-Planning

This myth may be farthest from the truth. Agile includes a lot of planning, ranging from daily planning in the form of daily standup to bi-weekly iteration planning and long term release planning. However, it is essential to note that Agile is anti-static planning. This means that agile expects the plan to change with the requirement and feedbacks. 

 

4. Not Undisciplined

The flexibility offered by agile is often identified as a lack of discipline. However, agile is a very disciplined way of project management and includes:

i. Upfront testing

ii. Regular feedback

iii. Regular delivery of product iteration

iv. Constant analysis and updates in the plan

 

5. Not Anti-architecture

The 90s saw a great rush in the development of big, complex structures. However, these architectures were complex, expensive, and hard to maintain. Agile reintroduced the culture of keeping things simple. However, agile is not entirely devoid of architecture and includes serious thinking. It just identifies that the best way to build a system is to make it simple.

 

6. Not an Excuse for Poor Quality

The whole objective of executing projects through MVPs is to deliver products quickly while ensuring that the minimum quality standards are met. Agile, in no way support the delivery of substandard results. The iteration plan should include sample checks for each iteration.

 

7. Not about Isolation

While agile supports the idea of downscaling for efficiency, it does not promote isolation. Agile is not about product owner or scrum master hiding the team and often promotes interactions between teams. We have already mentioned that it is essential in agile execution to bring the development team and the client closer and facilitate fluent communication between the two and other units.

 

8. Not About Rituals

The iterative approach of agile should not be confused with being a ritual. If any step loses its utility during project execution, it should be eliminated or modified to deliver better results.

 

9. Not About Stuff from the Book

Very often, due to an inaccurate understanding of agile, organizations do things by the book. Story, points, velocity, POs, Scrum Master, user stories, etc. are items used by the agile team, but they are not the definition of agile. Teams fail when they pay more attention to these activities rather than understanding their work.

 

So this is it! This is an extensive list of things that agile is not. If you are planning to try agile, it is essential to kill any misconception about the methodology. Don't opt for agile project management just because everyone uses it or because it seems to deliver better results. You need to ask yourself if you need agile. If you have been working in the project management spectrum and want to validate your learning or to explore prominent project management methodologies, we can help you with courses designed by industry experts. Explore our Project Management Courses Catalog and choose the course that enables you to improve your skill. You can also reach out to our career experts at support@certificationplanner.com if you have any query related to agile certifications. Happy Learning!

Labels:

Comments

Post a Comment

Popular posts from this blog

Optimizing Stakeholder Engagement

  Stakeholders are individuals or organizations who are involved in the project, or whose interests are positively or negatively affected by the result of the project. Stakeholders are essential as the project’s success or failure largely depends on the fulfillment of stakeholder’s needs or expectations. Due to this, the engagement of stakeholders intrinsically becomes an essential part of project management. The key to effective stakeholder engagement is “planning.” One has to systematically identify and prioritize stakeholders, along with establishing proper communication modes with them. So let’s look at the steps in the strategy to develop and optimize stakeholder engagement.   1. Stakeholder Identification The first step is to identify who all are being affected by the projects. It would be best if you considered all the individuals, interest groups, and right holders who would have an interest in the project. If you are running the project for a client, you may b...
Post a Comment
Read more

Salesforce - Einstein Analytics

Most of us may have heard of Salesforce in our organizations. We may have even worked on the Salesforce tool. So, what is the buzz about Salesforce? Salesforce is the pioneer in using cloud technology in the CRM system. It is a popular and leading customer relationship management (CRM) tool used by many organizations. It is so popular and user-friendly that it is used by start-ups as well as fortune 500 companies. When Salesforce was launched, it started as a tool that people in sales used to track their accounts, opportunities, leads, and financial information. It helped to create projections and follow up with their customers. Today, it is used in various industries to track their customer interactions, predictions, analytics, reports, and to manage customer accounts and information.      History of Salesforce Salesforce was started by Marc Benioff, Parker Harris, Frank Dominguez, and Dave Moellenhoff in an apartment in 1999. By 2000 they...
Post a Comment
Read more

An Introduction to Scrum

The Traditional Waterfall V/s the Revolutionary Scrum: Before we get into Scrum, let’s look at the waterfall method to understand how Scrum is different from the traditional approaches. The waterfall follows a lengthy and time-consuming process in developing a product. It goes through various stages, such as the plan, build, test, review, and deploy the final product. The waterfall model doesn’t shift to the next step without completing the previous step, removing the scope of overlap of tasks to optimize the process. Since project managers make all the significant decisions at the start, it takes months to complete the planning process, then goes for building, testing, and reviewing. As the final product gets delivered after a considerable lag, the final product often becomes partially obsolete by the time it is released. The process takes several years for a product to be ready after several times of back stepping into the process. Often, the development team begins working on...
Post a Comment
Read more