Tag: agile

Accurately Time-Estimating Development Tasks

While I admit that logging tasks in Agile results in some overhead, there are many cases where this overhead is worth it. Decomposing user stories into tasks or subtasks in JIRA is a non-special case of task decomposition in general.

Tagged with: , , , ,

Process Artifacts Coming Soon

I was quipping this morning and I might have uncovered something useful. Culture consultant Jamie Notter put out this article and I mentioned to a coworker: This article is decidedly better than his last, but again, his solution is ‘pay my consultancy’ instead

Tagged with: ,

Why Use Points for Estimation?

I’ve often been asked to map points to hours as part of an estimation process. This kind of works and kind of doesn’t. I’ll give my rule of thumb at the end, but first I want to defend the use

Tagged with: , , ,

Agile Estimation: To Repoint or Not to Repoint?

There is a minority practice in Agile Scrum sometimes called Repointing. This article describes the practice, compares it to the usual practice, and concludes by recommending that teams do not engage in Repointing. The usual Agile estimation procedure for an

Tagged with: , , , ,

Applied Unknowns Analysis

One of the major Austrian critiques of certain kinds of analysis focuses on uncertainty. You can make a forecast based on certain data, but something unexpected might come along and muck everything up. In the past I have described ways

Tagged with: , , , , , , , , ,

Skills in Overcoming Uncertainty

This article outlines some skills in overcoming uncertainty. It’s heavily biased toward software engineering. I also talk about environmental variables which help overcome uncertainty and risk in software development. Tldr: Skills include the ability to research, the ability to trial

Tagged with: , , ,
Top