Hackernoon logoLipstick Agile by@stefanw

Lipstick Agile

Stefan Wolpers Hacker Noon profile picture

@stefanwStefan Wolpers

Professional Scrum Trainer (PST) with Scrum.org.

Agile and Happiness in the Trenches

Have you noticed how many people in the agile field are unhappy with their work situation?

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.

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 w/o 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 situation?

Please click the “clapping hands” 👏, if you found this post useful–it would mean a lot to me!

Do you want to read more like this? Well:


Join Hacker Noon

Create your free account to unlock your custom reading experience.