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
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. Timebox != Commitment

Timebox != Commitment

Tobias Mayer user avatar by
Tobias Mayer
·
Apr. 13, 13 · Interview
Like (0)
Save
Tweet
Share
6.43K Views

Join the DZone community and get the full member experience.

Join For Free
Procrastinating this evening, I got lost in a long stream of tweets about timeboxing, fascinated at how much disdain was aimed at a simple unit of time, and how it was blamed for sloppy workmanship, poor quality, panic and many other dysfunctional behaviors.

Having already given up on doing anything I needed to do tonight, I jumped into the stream to challenge this point of view. After a few back and forths I realized the disdain arose not from anything a timebox actually is, but what people confuse it with.

It seems there is an understanding of a timebox that goes something like this.

  1. Set a timebox size
  2. Commit to a bunch of work
  3. Realize you are failing to complete it all
  4. Rush to finish
  5. Produce crappy work
  6. Be exhausted
  7. Go to #2—repeat until dead, or company goes out of business

The only part of this that has anything to do with timeboxing is #1. The rest is about making promises you can’t keep, and doing it again and again. Timebox antagonists call this commitment.

Here’s my understanding of timeboxing.

  1. Set a timebox size
  2. Engage in dialog with requester/s. Review requests, prioritize
  3. Select a request, small enough to fit inside the timebox
  4. Complete the work to the satisfaction of the requester
  5. Breathe [reassess remaining requests if necessary]
  6. Go to #3—until there is no request that can fit in the remaining time.
  7. Stop work [if time remaining, take Slack time]
  8. Reflect. Learn from mistakes, and adapt accordingly
  9. Go to #2—repeat until all requests met, or deadline arrived at.

Hard to really get the essence of this in pseudocode, but I think it’s reasonably clear. There is still commitment in this description, but it is a reasonable, wise commitment. The work committed to is independent of the timebox length. The timebox is there to create rhythm, and to create space. It is a heartbeat. That’s all.

Life abounds with natural rhythm, finding our own work rhythm and honoring it is a beautiful thing. It requires release though, an alignment with life. 

If you are using a timebox to force commitment in order to meet externally imposed goals, and you are not changing your behavior when this becomes apparent. Go ahead, blame the timebox. It’s easier than looking to thyself.

Requests Stream (computing) IT Dialog (software) Heartbeat (computing) Release (agency) Slack (software) Clear (Unix) Commit (data management)

Published at DZone with permission of Tobias Mayer. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • The Beauty of Java Optional and Either
  • Microservices 101: Transactional Outbox and Inbox
  • DevOps for Developers — Introduction and Version Control
  • How Elasticsearch Works

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: