devxlogo

Bad Attitudes of Agile Development

Bad Attitudes of Agile Development

Bad Attitudes of Agile DevelopmentAre you guilty of one of these opinions?

Agile development methodologies have a lot of benefits to offer: simplicity, speed, engagement with end users. However, agile developers are sometimes guilty of some bad attitudes. In particular, they may fail to recognize the contributions of managers and staffers from other departments. In this post, Christopher Goldsbury examines what’s wrong with some common bad developer attitudes, including the following:

    [login]

  • “Why are you here? Agile doesn’t need managers.”
  • “The team runs the project, not the managers….We’ll decide what gets done.”
  • “There are no due dates or schedules in Agile.”
  • “Agile code is self documenting. There’s no need for requirements, architecture diagrams or technical specifications.”
  • “Agile rapidly embraces change; all change.”
  • “Agile uses generalists; we test our own software. There’s no need for a QA group.”

View article

See also  20 Real-World Examples of Embedded Systems
devxblackblue

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

About Our Journalist