Project Management

Debunking Six Misconceptions About Agile

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog

RSS

View Posts By:

Cameron McGaughy
Lynda Bourne
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Wanda Curlee
Christian Bisson
Ramiro Rodrigues
Soma Bhattacharya
Emily Luijbregts
Sree Rao
Yasmina Khelifi
Marat Oyvetsky
Lenka Pincot
Jorge Martin Valdes Garciatorres
cyndee miller

Past Contributors:

Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie

Recent Posts

How Can We Keep Project Conflict in Check?

A Roadmap for Continuous Learning

The Power of Agile Team Cohesion

What Qualities Do the Best Project Managers Have?

The Power of Pauses and Silence

Categories

2020, Adult Development, Agile, Agile, Agile, agile, Agile management, Agile management, Agile;Community;Talent management, Artificial Intelligence, Backlog, Basics, Benefits Realization, Best Practices, BIM, Business Analysis, Business Analysis, Business Case, Business Transformation, Calculating Project Value, Canvas, Career Development, Career Development, Career Help, Career Help, Careers, Careers, Categories: Career Help, Change Management, Cloud Computing, Collaboration, Collaboration, Collaboration, Communication, Communication, Communication, Complexity, Conflict, Conflict Management, Consulting, Continuous Learning, Continuous Learning, Continuous Learning, Cost, COVID-19, Crises, Crisis Management, critical success factors, Cultural Awareness, Culture, Decision Making, Design Thinking, Digital Transformation, digital transformation, Digitalisation, Disruption, Diversity, Documentation, Earned Value Management, Education, EEWH, Enterprise Risk Management, Escalation management, Estimating, Ethics, execution, Expectations Management, Facilitation, feasibility studies, Future, Future of Project Management, Generational PM, Governance, Government, green building, Growth, Horizontal Development, Human Aspects of PM, Human Aspects of PM, Human Aspects of PM, Human Resources, Inclusion, Innovation, Intelligent Building, International, Internet of Things (IOT), Internet of Things (IoT), IOT, IT Project Management, IT Strategy, Knowledge, Leadership, Leadership, Leadership, lean construction, LEED, Lessons Learned, Lessons learned;Retrospective, Managing for Stakeholders, managing stakeholders as clients, Mentoring, Mentoring, Mentoring, Methodology, Metrics, Micromanagement, Microsoft Project PPM, Motivation, Negotiation, Neuroscience, neuroscience, New Practitioners, Nontraditional Project Management, OKR, Online Learning, opportunity, Organizational Project Management, Pandemic, People, People management, Planing, planning, PM & the Economy, PM History, PM Think About It, PMBOK Guide, PMI, PMI EMEA 2018, PMI EMEA Congress 2017, PMI EMEA Congress 2019, PMI Global Conference 2017, PMI Global Conference 2018, PMI Global Conference 2019, PMI Global Congress 2010 - North America, PMI Global Congress 2011 - EMEA, PMI Global Congress 2011 - North America, PMI Global Congress 2012 - EMEA, PMI Global Congress 2012 - North America, PMI Global Congress 2013 - EMEA, PMI Global Congress 2013 - North America, PMI Global Congress 2014 - EMEA, PMI Global Congress 2014 - North America, PMI GLobal Congress EMEA 2018, PMI PMO Symposium 2012, PMI PMO Symposium 2013, PMI PMO Symposium 2015, PMI PMO Symposium 2016, PMI PMO Symposium 2017, PMI PMO Symposium 2018, PMI Pulse of the Profession, PMO, pmo, PMO Project Management Office, portfolio, Portfolio Management, portfolio management, Portfolios (PPM), presentations, Priorities, Probability, Problem Structuring Methods, Process, Procurement, profess, Program Management, Programs (PMO), project, Project Delivery, Project Dependencies, Project Failure, project failure, Project Leadership, Project Management, project management, project management office, Project Planning, project planning, Project Requirements, Project Success, Ransomware, Reflections on the PM Life, Remote, Remote Work, Requirements Management, Research Conference 2010, Researching the Value of Project Management, Resiliency, Risk, Risk Management, Risk management, risk management, ROI, Roundtable, Salary Survey, Scheduling, Scope, Scrum, search, SelfLeadership, SelfLeadership, SelfLeadership, Servant Leadership, Sharing Knowledge, Sharing Knowledge, Sharing Knowledge, Social Responsibility, Sponsorship, Stakeholder, Stakeholder Management, stakeholder management, Strategy, swot, Talent Management, Talent Management, Talent Management, Talent Management Leadership SelfLeadership Collaboration Communication, Taskforce, Team Building, Teams, Teams in Agile, Teams in Agile, teamwork, Tech, Technical Debt, Technology, TED Talks, The Project Economy, Time, Timeline, Tools, tools, Transformation, transformation, Transition, Trust, Value, Vertical Development, Volunteering, Volunteering #Leadership #SelfLeadership, Volunteering Sharing Knowledge Leadership SelfLeadership Collaboration Trust, VUCA, Women in PM, Women in Project Management

Date


Categories: Agile


For those of us in the project management community, agile is a familiar term. But despite its prominence, it’s often misunderstood. 

All too often, teams and organizations focus on the wrong things or are misinformed. And eventually, agile takes the blame. 

Here are six common misconceptions that can lead to an anti-agile mindset:

  1. It is all about the tool. Any tool that’s hailed as what makes agile works is still just a tool. Yes, with distributed teams it helps to have a tool where everyone has access to project details and data. However, when introducing your team to agile, your training shouldn’t be tool-centric. I prefer teams to see and understand how agile really works—the simple use of sticky notes or a whiteboard does the trick. The move to a tool can and will happen eventually, and when it occurs, you don’t have to send multiple follow-ups to ensure the team is populating the data. 

 

  1. Agile is changing requirements in the middle of the sprint. While agile is known for inspecting and adapting, changes can get out of control. I hear teams talking about changes happening so often that they can barely focus on the work, or they are constantly handling changes. When the pressure to change a requirement is happening too often within a sprint and ends up becoming a norm in the team, the product managers or sponsors need to jump in to determine what needs to be built. Otherwise, team members tend not to focus on the work because they know no matter what they do today, everything will change tomorrow.

 

  1. Agile doesn’t use data. The idea that data isn’t tracked is wrong. In fact, there are many ways to look at data. However, we also have to be mindful so data isn’t just being used for the sake of data, leading teams to start bluffing around it.  

 

  1. Agile doesn’t offer predictability. You’ll often hear that there was better predictability before—and now nothing works. Sponsors always need to know the timeline. And yes, this can be done in agile. In fact, using and tracking the right data can bring in the predictability your team needs. The velocity metric will let you know how much a team can handle in a sprint. So, whether it’s a burndown chart, sprint or release planning, there are multiple ways to get the required predictability and commit accordingly.   

 

  1. Agile doesn’t offer time to think. I recently was in a session about thought leadership and someone mentioned agile being the greatest blocker because there was no time to think. Interpretation, I believe, is the biggest problem of all. You can still block a certain percentage of your team’s capacity or yours to try out new ideas, participate in hackathons or learn a new skill that adds advantage to your product or service. If you are not speaking up about the problems, you should. And if flexibility isn’t allowed, that’s because of the team culture, not the process. 

 

  1. Agile is all about micromanagement. One of the funniest misconceptions I’ve heard is that an organization moved to agile because leadership wanted everything to be micromanaged. Individuals didn’t understand that team capacity and complexity (as measured in story points) aren’t ways to track team members. Instead, they are tools to help team members make the right commitments during their sprints, commitments they can actually keep and deliver. In this case, a lack of explanation about why the organization moved toward agile triggered multiple miscommunications. So, the responsibility lies with management and the agile coach to take the time to explain the move to agile. Because instead of micromanagement, agile is really about the opposite. It, in fact, allows teams to be empowered, to be able to self organize, to be vocal and to get the work done. 

These are six misconceptions I’ve seen about agile. What are the common ones you’ve encountered?

Posted by Soma Bhattacharya on: May 24, 2019 12:48 PM | Permalink

Comments (11)

Please login or join to subscribe to this item
avatar
Wade Harshman Scrum Master| Allegion Indianapolis, In, USA
I've never heard #5, that Agile doesn't offer time to think. I'm more familiar with the obverse argument, that Agile (more accurately, Scrum) has too many meetings. This is also a myth, but I smile to know we have contradictory misinformation.

avatar
Drew Craig Coach, Practitioner, Consultant, Humanist| North Highland Philadelphia, Pa, USA
Thank you, Soma. Good perspectives. Also, that Agile is not a thing, and not simply a light switch the organization can flip on when decide time to transform.

avatar
Eduin Fernando Valdes Alvarado Project Manager| F y F Fabricamos Futuro Villavicencio, Meta, Colombia
Thanks for sharing

avatar
Suzi MS United Kingdom
Interesting post, thanks for sharing!

avatar
Manish Shrivastava Mumbai Thane And Navi Mumbai, Maharashtra, India
Agile is micromanagement of software development activities of product/services for user/business requirements. This requires more time for requirement gathering interactions, and hence more meetings and time consumed to finalize the requirements.

hence it (Agile practices) will always require more time to freeze the requirements, for which development activities can start and definitely requires more time.

I do not agree for the statement "Agile doesn’t offer time to think" as it has team discussion and meeting in pipeline for the development life-cycle.

avatar
Frank Spiegel Senior Projectmanager, PMP, PMI-ACP| Commerzbank AG Oberursel, Germany
The common misconcept I experience is the claim that it is not possible to finalize something during a short sprint. Coming from the waterfall approach it could be a hard learning topic to show the opposite.

avatar
David Choi Executive Program Manager| Teradata Hong Kong, Hong Kong
I agreed with Andrew Craig above that Agile is not a light switch that organization can flip to start doing Agile, Agile is both a culture change and process re-engineering for any organizations that have not used Agile before. also an experienced Agile practitioner in the team will ensure the switch to Agile journey is going in the right direction and minimize the above misconceptions.

avatar
himanshu bhargav Technology Program Manager| Goldman Sachs Malvern, Pa, USA
Some that I have witnessed:
1. Agile makes functional managers less engaged and productive rather insecure about their jobs. It's actually untrue however many managers feel that way as their roles and duties as servant leaders, enablers are not clearly explained and socialized.
2. Business assumes Agile will reduce time to market, enable faster ROI realization etc. only through making software delivery world more nimble and agile. This does not work until full value stream right from concept/ ideation stage to final use by end customer is optimized using Lean and Agile optimization. Local optimization won't deliver benefits as intended and can further confuse employees rather than increasing employee engagement and enhancing satisfaction for employees, customers.

avatar
himanshu bhargav Technology Program Manager| Goldman Sachs Malvern, Pa, USA
Some that I have witnessed:
1. Agile makes functional managers less engaged and productive rather insecure about their jobs. It's actually untrue however many managers feel that way as their roles and duties as servant leaders, enablers are not clearly explained and socialized.
2. Business assumes Agile will reduce time to market, enable faster ROI realization etc. only through making software delivery world more nimble and agile. This does not work until full value stream right from concept/ ideation stage to final use by end customer is optimized using Lean and Agile optimization. Local optimization won't deliver benefits as intended and can further confuse employees rather than increasing employee engagement and enhancing satisfaction for employees, customers.

avatar
Glenn Chundrlek Project Management Specialist| Miami University Loveland, Oh, USA
I've heard all of these misconceptions, but the most egregious I've heard is that Agile is only good for software development projects. While Agile and its variants are not universally applicable, there are definitely other disciplines where a small team of people can work together in a collaborative manner to accomplish a goal. As I like to say, one does not do Agile, one is or becomes Agile.

avatar
Priya Patra Delivery Director| Capgemini India Technology Services Ltd Mumbai, India
And the most famous one - Agile does not plan :(

Please Login/Register to leave a comment.

ADVERTISEMENTS

"I don't like work - no man does - but I like what is in the work - the chance to find yourself."

- Joseph Conrad

ADVERTISEMENT

Sponsors