DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
The Latest "Software Integration: The Intersection of APIs, Microservices, and Cloud-Based Systems" Trend Report
Get the report
  1. DZone
  2. Culture and Methodologies
  3. Agile
  4. Striving To Be Happy in an Agile Environment

Striving To Be Happy in an Agile Environment

A happy worker is a productive worker, a happy worker is a more accomplished worker, and a happy worker is a more healthy worker.

Holger Paffrath user avatar by
Holger Paffrath
·
Nov. 23, 16 · Opinion
Like (5)
Save
Tweet
Share
4.81K Views

Join the DZone community and get the full member experience.

Join For Free

Have you ever sat in one of those emotional retrospectives where everyone draws a happy or sad face or a graph to show their feelings depending on how they felt the Sprint went?

They can and do feel like BS, especially to programmers like myself who are introverted and would prefer to sit in a dark room all day coding rather than share their feelings. However, there is some merit to measuring happiness during a sprint.

We have to do some clarification about what happiness is work-wise. It's not playing around all day, browsing Facebook or shooting each other with Nerf guns. It's more when are you happy being productive. You know the feeling; when you're in the zone. Time seems to pass by without you noticing and at the end of the day when it's time to go home (you have to be reminded that it's time to go home, as you are so focused), you have a feeling that you have accomplished something. These days are as rare as hen's teeth, but damn they feel good.

What is the magical formula that brings us those days? According to Lean Thinking, it is when the following criteria are met:

  • You have a clear objective. In other words, you know exactly what you need to accomplish.
  • The need for concentration is intense; so intense that no attention is left over to think about other things.
  • There's a lack of interruptions and distractions (this rules out the modern workplace!).
  • You receive clear and immediate feedback on the progress towards the objective. In other words, you have a feeling that you're getting somewhere.
  • There's sense of challenge (but not too much of a challenge). Your skills need to be just adequate enough to complete the task. If it's too hard, you get frustrated. If it's too easy, you get bored.

Jeff Sutherland is one of the co-creators of Scrum. His book Scrum, the Art of Doing Twice the Work in Half the Time summarizes Scrum in three points:

  1. Autonomy
  2. Mastery
  3. Purpose

I like this definition more. It's short and direct. But what do these words mean?

Autonomy comes from having a certain level of control over how you do a task or, more likely, how you accomplish a goal. The more vague the goal, the more the person has control over how you accomplish the end result. The more detailed the task, the fewer choices the person has on how to accomplish it and the more they feel a cog rather than a thinking person.

There was recently a scientific study that discussed the mortality rate of a person based on the level of control they had over their job. The findings were that if you have low control in a high-demand job, you have a 15.4% increase in the chance of death compared to a low-control, low-demand job.

For a high-control, high-demand type job, there was a 34% decrease in the odds of death compared to a high-control, low-demand job. So, having more control and a little bit of stress is actually good for you.

Mastery is where we want to learn more and get better. It's the struggle for perfection. It is what gives us a sense of challenge. When we are in the zone, we are learning. We are trying to figure out that little puzzle and put all of the pieces together. Once we have mastered that problem, we have accomplished something, and that little snippet of knowledge is tucked away for next time. (Not to mention the dopamine shot we get to activate the pleasure centers!)

Finally, there is purpose. This is what drives us to keep going. Without a purpose, all of our work feels like it is being done for nothing. That purpose needs to be perceived because without the perception of purpose, it doesn't matter how important the job is; it will have no meaning to the person carrying out the task.

So, why is happiness important? Quite simply, a happy worker is a productive worker. A happy worker is a more accomplished worker and a happy worker is a more healthy worker.

I'd like to suggest that for your next retrospective, you go through and do an emotional check. Rather than draw happy faces, discuss the above points and see what can be done to increase the likely hood of reaching them (or even if they are relevant). Let me know how it goes in the comments!

IT agile

Published at DZone with permission of Holger Paffrath, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Using Swagger for Creating a PingFederate Admin API Java Wrapper
  • How To Best Use Java Records as DTOs in Spring Boot 3
  • Keep Your Application Secrets Secret
  • 5 Steps for Getting Started in Deep Learning

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: