We’re not psychic, so why do we bother predicting the future?
Developers still suffer task estimates, despite knowing they’re just fudging numbers. Here’s how we escaped the crystal balls and horoscopes.
There’s little in the world of software development more frustrating than estimating tasks. It’s a constant tug of war between developers and management. The result is an arbitrary number, a point in time that wasn’t there before, that will make you feel miserable for crossing it. Yay!
It’s a blatantly broken system, so we fixed it. With some small tweaks, we ended up with a far more reliable and comfortable way of working. Rather than declaring arbitrary targets to aim for, we treat our time like a resource, because it is.
“Give me a timebox and I will fill it with value.”
After an easy goodbye to estimating, we picked up timeboxing instead. A timebox is the time that the task owner is willing to have spent on any non-trivial task, preferably limited to a single day. Task owners are those to whom the result of the task is delivered. By changing the number’s origin, it immediately becomes far less arbitrary.
Spend an hour hacking away at it, you’ll end up with a clearer picture of the work required and the soundness of your timebox. Then continuously manage expectations with your task owner while working the task. Notify them when you trip over an unexpected problem, or when you’re progressing surprisingly fast. This allows them to tweak their task expectations and requirements. In the end, they should never be surprised by the result.
- Always deliver something of value
- Never exceed your timebox
- Task owners must know exactly what they’ll get
The resulting process is far less arcane and deeply includes the task owners. It’s proven to be a great way to involve our customers in what we do, and a comfortable way for developers to get work done.
Interested in how we mange our issues? Read “Milestones and Office hours“
I am an Atlassian certified trainer and over the years I have been spending much time with clients and their Jiras. In this blogpost, I have collected some small tips and tricks that will make your Jira usage better.
Jira Software is a powerful tool deployed in so many organizations, yet in day to day usage people are missing out on improvements, big and small.
In this post, I’ll take a closer look at the version of Jenkins X using Tekton, to give you an idea of how the general development, build, test, deploy flow looks like with Jenkins X. How does it feel to ship your code to production using a product coming from the Jenkins community that has very little Jenkins in it?
A crash course in Jenkins X and how to test it out on a local Kubernetes cluster
In this blog I will show you how to create snapshots of Persistent volumes in Kubernetes clusters and restore them again by only talking to the api server. This can be useful for either backups or when scaling stateful applications that need “startup data”.
Sneak peak at CSI Volume snapshotting Alpha feature
When I read Fowler’s new ‘Refactoring’ book I felt sure the example from the first chapter would make a good Code Kata. However, he didn’t include the code for the test cases. I can fix that!
Writing tests for ‘Theatrical Players’
Nicole Forsgren and the Accelerate DORA team has just released the newest iteration of the State of DevOps report. The report investigates what practices make us better at delivering valuable software to our users as measured by business outcomes. Read on for our analysis of the report, and how it can be best put to use.
The latest drivers of software delivery performance
A major challenge of software development is that our work is by and large invisible. This makes our folklore essential in business matters. Some of our commonly used arguments and visualizations are digital urban legends rather than solid foundations for informed decisions. Here, we’ll go through a few examples and some measures to address our misconceptions.
How the stories we tell influence our decisions
When you embark on your cloud native journey there will be important choices to make about cloud providers, continuous deployment, environments’ setup and separation. This guide will help you make the right choices by sharing lessons learnt from running cloud native apps in production.
Kubernetes has become the de facto container orchestration platform. When we help clients of different sizes and domains start their cloud native journeys in Kubernetes, we assist them in making sound decisions and technology choices. There is no one-size-fits-all solution when it comes to choosing cloud providers, CI tools, continuous deployment pipelines etc., so it is important to make the right decisions at the start. Failing to do so can be very costly in terms of lost time and money.
How to make the right technical choices on your cloud native journey
Learn how Docker and Kubernetes work and the key benefits they bring. Using real demos, I show how Docker is a great packaging and distribution technology, and how Kubernetes provides a powerful runtime for containerized applications.
Watch this introduction to Docker and Kubernetes at the Trondheim Developer Conference (TDC)
In the world of Agile and DevOps we use many figures, charts and diagrams to argue and reason about our world and how we prioritize and make choices. However, at all levels of the organization, we misuse and misinterpret figures. It’s time to be explicit, measure the right things and act on them. Watch this talk from DevOpsDays Zurich in May 2019.
Watch this talk from DevOpsDays Zurich
Summer is a great time to catch up on reading, whether you’re at the beach, in a summer house, or cozy at home. If your book backlog is on the short side, don’t worry! We compiled a list of great books for summer reading.
Inspiration for your summer reading list
Hear about upcoming events in Scandinavia, latest tech blogs, and training in the field of Continuous Delivery and DevOps