• How-to Guide: Change in Project Management

  May 23, 2013

  
  

• How Much Project Management Is needed in a Federated Organization?

  May 23, 2013

  
  

• Become a Proactive Project Manager

  May 22, 2013

  
  

• Project Management - Communicating Successfully

  May 22, 2013

  
  

• Talk Like a Project Manager

  May 21, 2013

  
  

• How to Project Manage a Pyramid

  May 21, 2013

  
  

• The Art of Project Management: Scale

  May 20, 2013

  
  

• Project Management Foundations - Understanding the Maturity of Your Project Office

  May 20, 2013

  
  

• Why Are Companies “Good” but Very Rarely “Great” at Project Management?

  May 19, 2013

  
  

• Project Management Institute’s 2013 “Pulse of the Profession” Survey

  May 18, 2013

  
  

7 Agile Myths

June 21, 2012 | Author: PM Hut | Filed under: Agile Project Management

7 Agile Myths
By Marc Löffler

I recently talked about seven Agile Myths. You’ll hear about these myths most of the time on management level, but some of them can be found on the development level, too. IMHO it’s important to be aware of these myths to be prepared for possible discussions.

1. Agile = No documentation

   This is one of the most famous myths and I think we have to blame the agile manifesto for this. The line “Working software over comprehensive documentation” is often misunderstood with no documentation at all. But how could agile Frameworks like Scrum survive in highly regulated environments like the medical or financial industry if this would be right. For sure there is documentation, but we don’t waste time on documents that deliver no value to the project.

2. Agile = Anarchy

   The biggest fear of any manager is to lose control over their agile teams, because they think self organisation is the same as anarchy. Yes, the role of management changes but they still play an important role in their company. They are needed to define clear visions and goals and the constraints of a project. Only within these “fences” the team can work self organized. They are also needed to help the team to gain their full potential. This has nothing to do with anarchy.

3. Agile = faster

   IMHO it was a bad idea to name an iteration in Scrum a sprint. This implies that everything is real fast in agile. But at least in the beginning the complete opposite is true. Building in quality into a product takes time and quality is not discussable. You’ll be able to harvest the fruits later as you’ll have less bugs and the software is more maintainable and that’s the point where agile is bringing you up to speed.

4. Agile = silver bullet

   Yes, this true. Just kidding ;) There is no silver bullet in software development. I repeat: There is no silver bullet in software development. Sure, the process of software development has some impact, but in the end it is all about the people in a team. I saw awesome products created by a “waterfall team” and crappy software by agile teams. In the end it is all about the right people at the right place or as written in the agile manifest: Individuals and interactions over processes and tools (this also applies to Scrum, Kanban, XP and any other process).

5. Agile = simple switch

   Simple said: No it isn’t. The frameworks itself can be explained within 10 minutes, but what is often forgotten are the needed mindset behind and the principles that agile methods are based upon (Lean Thinking, Pull vs. Push, empiric process control, iterations and increments, self organisation…). In bigger corporations it may take years until you can talk about an agile company. You won’t believe it, but it is not enough to send your team to a two days ScrumMaster training…

6. Agile = Easy

   How can it be easy to deliver a possible shippable product every 1 – 4 weeks? In the past you weren’t able to do it after one year. It is a lot of hard work to get there and it is for sure not an easy thing to do. And I don’t want to mention continuous deployment here…

7. Agile = software development

   Often the agile journey starts in software development, but it should not stop here. To have an agile software development team in an non-agile environment is like planting a tree in the desert –> it won’t survive. The whole company culture has to change, everybody needs to adhere to the agile principles like lean thinking. Otherwise your agile transition will end in a blind alley and a lot of frustration.

What agile myths do you know. What are your experience with those myths? I’m looking forward to your comments!

Marc Löffler works as Functional Manager at Storz Endoskop Produktions GmbH in Switzerland. His passion is to help teams implementing agile frameworks like Scrum and XP and to transform our world of work. You can read more from Marc on his blog.

This entry was posted on Thursday, June 21st, 2012 and is filed under Agile Project Management. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Name: *
Email (will never be displayed): *
URL:
Your comments: *
Remember my information for the next time I visit.

• Agile Project Management
• Ask the Hut
• Certification
  • CAPM
  • ITIL
  • PgMP
  • PMP
• Change Management
• Communications Management
  • Communications Planning
  • Information Distribution
  • Performance Reporting
  • Project Closure
• Computer Based Information Systems
  • Latest Trends
  • Project Collaboration
• Concepts
  • Project Lifecycle Phases
  • Project Stakeholder Management
  • Role of the Project Manager
• Corporate Transformation
• Cost Management
  • Cost Estimating
  • Economic Evaluation
• Critical Chain Project Management
• Delegation
• History
• HR Management
  • Organizational Structures
  • Team Building
• Implementing Project Management
  • PM Implementation Plan
• Integration Management
  • Change Control
  • Project Management Framework
  • Project Plan Development
• Lessons Learned
• Management
• Miscellaneous
• People Issues
  • Conflict Management
  • Leadership
  • Motivation
• PMBOK
• PRINCE2
• Procurement Management
  • Contract Administration & Close-out
  • Procurement Plannning
  • Solicitation & Source Selection
• Program Management
• Project Lifecycle Phases
• Project Management Advantages
• Project Management Advantages
• Project Management as a Career
• Project Management Best Practices
• Project Management Charts
• Project Management Definitions
• Project Management Ethics
• Project Management for Beginners
• Project Management Guides
• Project Management Musings
• Project Management Office
• Project Management Proposals
• Project Management Templates
• Project Portfolio Management
• Project Workforce Management
• Quality Management
  • Principles
  • Techniques
• Requirements Management
• Risk Management
  • Risk Identification
  • Risk Quantification & Analysis
  • Risk Response & Control
• Scheduling
  • Normal and Crash Costs
  • Project Plan Refinement
  • Resource Constrained Projects
  • Resource Leveling
• Scope Management
  • Process of Change Control
  • Project Scope Management
  • Scope Change Control
• SCRUM
• Soft Management
• Time Management
  • Activity Definition
  • Activity Duration Estimate
  • Activity Sequencing
  • Critical Path
  • Network Planning
  • Project Milestones
• Training
• Uncategorized