Why

Time Spent Making vs. Time Spent on Process

I've spent a lot of time observing teams. At first glance almost every team I see is working hard, and trying to do the right thing the best they can. Sure they may not be super effective or efficient, but it's not for lack of trying, and often not their fault. One of the key things I look for is how a team works, and more specifically how they allocate their time. If you really think about it there are really only two things teams do: Productive work, making, building, etc. Communicating, estimating, justifying, and explaining the work, and status

  • Mark Thomas
    Mark Thomas
4 min read
Why

Organizational Methodology Adoption

How did your team end up using your current methodology? It's kind of a trick question, because if you are using a branded Agile methodology you have probably already made choices that are highly limiting to your teams empowerment, and the trust of the organization that's needed for long term success. Capital A Agile software development has fully infected many teams. There are so many lessons to be learned from software development history. We stand on the shoulders of giants; but the leadership at many companies are not part of that on-going conversation. This means that you must assume that

  • Mark Thomas
    Mark Thomas
1 min read
Why

Software Complexity and Leadership

I am of the school of thought that says software products are complex. Even, or perhaps especially, when you try and make them simple to your users. The technology is a part of it, but most of the complexity comes from the fact that you are designing and building something new. The work to understand the problem space, customer need, and how that intersects with the technology you need to build is all part of that. The most efficient process to implement something is usually not the most effective process to design that same thing. Properly done, teams are constantly

  • Mark Thomas
    Mark Thomas
2 min read
Why

Why Companies Fail at Software.

Companies big and small, especially ones that don't have software deep in their founding DNA tend to fail more than they succeed in their software projects. The fabled digital transformations are very expensive, but don't always end up the way people hope. I've seen a few of these, and there are some common factors and trends. Watch this space for more on how to spot things going wrong, and some of the things you could do to avoid the pitfalls.

  • Mark Thomas
    Mark Thomas
1 min read