Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Lipstick Agile: 13 Signs You Probably Need a New Job

DZone's Guide to

Lipstick Agile: 13 Signs You Probably Need a New Job

A little insight into what NOT to look for in an Agile company. For all those times when you looked back and wished you knew then what you know now.

· Agile Zone ·
Free Resource

The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.

Happiness in the Trenches?

Have you noticed how many people in the Agile field are unhappy with their work situation — caught in a lipstick Agile situation where an organization already struggles doing Agile (not to mention "becoming agile")? 

Scrum masters and Agile coaches who are close to either burnout or indifference. Product owners who “own” the product by name only, and developers who are questioning why Scrum a) skips all the practices that make XP work, and b) often turns out to be just another form of micromanagement.

Lipstick Agile — 13 Signs You Probably Need a New Job by Age of Product


Lipstick Agile Statements and Observations

Here is a list of my issues that made me not accept an offer in the past or started having second thoughts on being part of an organization:

  1. “How many teams can you handle at the same time — three or four?” (A prospective client.)
  2. “The availability of meeting rooms is a difficult topic here.” (There was no space at all available.)
  3. “We don’t need physical boards; we use Jira.” (“When you put problem in a computer, box hide answer. Problem must be visible!” Hideshi Yokoi, former President of the Toyota Production System Support Center in Erlanger, Kentucky, USA.)
  4. “Test automation does not work for us. We always test manually.” (A manager from a corporate QA silo without an engineering background.)
  5. “We deploy once a week so that the governance team has a chance to sign-off our work.” (The team created an excellent build pipeline and could deploy at will.)
  6. “As a Scrum Master, you will also report the performance metrics of the team to the project manager after each sprint.” (A prospective client.)
  7. “We can invest more in learning once we have delivered [the application] and proven our usefulness.” (Knowledge sharing as a reward.)
  8. “I think pair programming is a waste of resources. Remember, it is twice the work in half the time.” (Thank you, Mr. Sutherland, for not pointing at the fine-print so every business guy gets it wrong.)
  9. “Why would you include the developers in the user interviews? They are supposed to write code. The business analysts can do the talking.”
  10. “We need to meet numbers and deadline. That’s more important than living up to some fancy initiatives of the C-level like ‘becoming agile.’”
  11. “We know what we need to build, talking to users is a distraction.”
  12. Observation: Stakeholders do not participate in ceremonies, for example, sprint reviews. Never.
  13. Observation: Stickies on a physical board seem to have been aligned with a bubble level. (A prospective client, looking for a dedicated, full-time Scrum Master for a team comprising of five people.)

What has made you reconsider your job situation in the past?

Download the ‘Scrum Anti-Patterns Guide’ — it covers more than 160 scrum anti-patterns that hold your Scrum team back.

Adopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap, brought to you in partnership with Techtown Training

Topics:
scrum master ,agile coaching ,product owner ,failure ,anti-pattern ,agile transition ,agile adoption ,agile

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}