So You Really Want to be an Agile Developer?

The page asks what it means to be an Agile Developer and contrasts two situations. In faux Agile, people perform agile practices without being allowed to adopt the core behaviors. In a more favorable case, a team may get closer to what the Agile Manifesto intended, but still not reach full-on Agile.

Reading notes

#

• “Faux Agile” describes groups that go through agile motions because managers want productivity or other benefits, while refusing to let them adopt core Agile behaviors.
• Even when conditions are better, many teams still do not get to experience full-on agile development.
• Full-on Agile means Agile as the manifesto authors intended, with the knobs turned up to 11.
• Full-on Agile is not a structure where business analysts own requirements, scrum masters or coaches stand apart from development, architects own product features or structure, or product owners stand between customers and the team.
• It is also not a setup where developers, writers, business people, sales, marketing, managers, project managers, testers, quality managers, or metrics roles work in separate compartments.
• The page says these activities are still necessary, but the development team collectively takes responsibility for them and decides which ones add value.
• The main consequence is that developers end up doing many things beyond the work they traditionally see as their own, and other specialists do too.
• The closing question is whether someone really wants to be a full-on Agile Developer.