Cooperation and Knowledge Sharing for Remote Agile Development

Cooperation and Knowledge Sharing for Remote Agile Development

June 01, 2020 by Egon Wuchner

Introduction

Remote work and remote agile development have been one of the remedies in this day and age of the Corona consequences. During the last weeks, I have come across several articles, posts and blogs about the pitfalls of remote working teams and recommendations on how to take countermeasures against missing collaboration.

I think the McKinsey article on “Revisiting agile teams after an abrupt shift to remote” [1] is an interesting contribution worth considering. I am going to refer to some other sources, but do not claim any completeness with respect to the topic. But across all articles, I have been missing some simple but effective means of not only promoting a more collaborative mindset but making cooperation actually happen.

Continue reading →

Posted by Egon Wuchner in General, 0 comments
Improving Software Quality by Choosing Reasonable Issue Types

Improving Software Quality by Choosing Reasonable Issue Types

May 02, 2020 by Konstantin Sokolov

Introduction in a Nutshell

Do you exactly know which issues types to use for your issue tracker and when to use which? Does everyone in your project know about your approach? Are issue types always used consistently in your project? Should  you use Technical User Stories or not? Do you use issue types at all? Do you find it reasonable that different issue trackers have such different default issue types? Have you ever thought about issue types at all?

If your answer to one or more of the questions above is “no”, or “don’t know” or “I don’t care”,  you are not alone, and this post might be of interest to you. It reveals the chaos behind the often mindless, uncertain and inconsistent usage of issue types in many software projects. It shows why a conscious and purposeful application of issue types can lead to better code comprehensibility as well as better quality monitoring and decision making in projects. It suggests a minimal set of reasonable issue types along with understandable rules for their usage. In particular, it reasons why a separate issue type is needed to deal with technical debt.

Continue reading →

Posted by Konstantin Sokolov in General, 0 comments