Skip to main content

When Not To Use Agile

Over the years, Agile methodologies have taken the heat when they appear to have failed to deliver expected benefits to an organization.

If our project fails, the tendency is that “we must blame the Agile process and our practices in some way for this”.

Agile is not a magic stick to save a failing project and bring immediate results. It lets you uncover better ways of developing software by doing it and helping others do it.

As with all development methods, the skill and experience of users determine the degree of success and/or abuse of such activity.

So sometimes we obtain the agility by making up our own variation of this methodology. In this case, failure of this project should largely be incumbent upon us for deciding to sacrifice the practices we chose to ignore and the new ones we added.  Some are Agile while just for namesake, and following no methodology, just cherry-picking a couple of practices here and there, and picking the principles they like.

1.  Checkbook commitment doesn’t support organizational change management. CEOs create within the company their own personal family dysfunction.

2.    Culture doesn’t support change.

3.    There are no or ineffective retrospectives. Actions which come out get ignored or written off.

4.    In a race to finish features, the infrastructure gets worse and architecture becomes unstable. Distributed teams make this worse.

5.    Lack of collaboration in planning. Like having the whole team for release planning.

6.    None or too many Product Owners. Both cases look the same. Agile is yet another hat to wear and the person is already too busy. They check out and ask the team to just do Agile. Can’t get past the ‘this sucks’ phase of adoption if the business is not bought in.

7.    Bad Scrum Master which uses a command and control style with the team to look faster, yet in reality slows things down. Low morale actually makes people less productive

8.    No on-site evangelist. If the teams are distributed, need one at every site. Can’t reap the benefits of Agile or offshore without an on-site coach at each location.

9.    No solid team.

10. Tsunami of technical debt if don’t pull tests forward.

11. Traditional performance appraisals. Individual heroics rewarded

12. Revert to traditional. Change is hard.

World of Agile is a brand owned by Effective PMC Pvt Ltd. Founded in 2009 and specializes in providing professional training services on Project Management related certifications. In the last 7 years, trained more than 10K+ professionals from various verticals on certifications by Project Management Institute (PMI)® Such as Project Management Professional (PMP)®, PMI Agile Certified Practitioner (PMI-ACP)® other certifications like SCRUM, PRINCE2, ITIL, MICROSOFT PROJECT and many students have passed PMP® examination after attending our courses.

For More Information, Follow the Links below-

Comments

Popular posts from this blog

The Service Value System - Continual improvement | ITIL V4 Certification

Continual Improvement Continual improvement takes place in all areas of the organization and at all levels, from strategic to operational. When provisioning a service we should always keep continual improvement in mind, and should always be looking for opportunities to improve. To support continual improvement at all levels, the ITIL® SVS includes: ITIL® Continual Improvement Model provides organizations with a structured approach to implementing improvements Improve Service Value Chain Activity Continual Improvement Practice Continual Improvement Model Continual Improvement Model can be used as a high-level guide to support improvement initiatives.  The model supports an iterative approach to improvement, dividing work into manageable pieces with separate goals that can be achieved incrementally. The scope and details of each step of the model will vary significantly based on the subject and the type of improvement The steps of this model do not need to be carried out in a linear ...

What are Important Roles in Scrum-Agile Teams?

The Primary Team roles in scrum are named as • Product Owner  • Scrum Master • Development Team Scrum Master, Product Owner, and Team are considered as people who are committed to the project while customers and executive management are considered as involved but not committed to the project. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.  Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity. Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of “Done” product ensure a potentially useful version of working product is always available. All the roles are based on the concept of “S...

What is ITIL?

The term ITIL means "Information Technology Infrastructure Library". ITIL is the most popular and widely accepted approach to manage IT Service(ITSM). ITIL has been adopted by many organizations as the framework to manage their IT service. There are millions of practitioners worldwide with ITIL skills and capabilities. IT is important to keep in mind that ITIL is a set of best practices and not a standard, so organizations are free to adopt ITIL framework as is applicable or valuable to them. Advantages of adopting ITIL for your organization are immense. Therefore, all scale and size (Small , medium, Large) organizations all over the world use ITIL to help them improve the value of their services. The few important benefits of adopting ITIL are:  ITIL creates stronger alignment between IT and the business Improves service delivery and customer satisfaction Reduces costs with improved use of resources Provides Greater visibility of IT costs and assets A Brief History of ITIL: ...