Journey to DISTekian Agility: Mind-over-Methods
At DISTek, we pride ourselves on the ability to remain adaptable. We make it a priority to listen and are quick to adapt to the processes, tools, and approaches of …
At DISTek, we pride ourselves on the ability to remain adaptable. We make it a priority to listen and are quick to adapt to the processes, tools, and approaches of …
Conferences are one of those things you hear about and see all the cool swag from those who attended. After hearing about it for years, I finally decided to take …
I joined DISTek a little over a year ago. One fine afternoon, as I was rushing back from lunch, I got a call from a recruiter asking about my job …
In the past, DISTek faced long and challenging development cycles with single individuals assigned to complete projects in isolation. Projects were often plagued with schedule delays, cost overages, and quality problems. Guided by a SAFe champion and small team of coaches, DISTek successfully implemented the Scrum framework within SAFe 4.5.
The book Team of Teams, by Stanley McChrystal, covers a lot of topics that strongly relate to the direction that DISTek is heading. Some of these concepts, such as shared consciousness, cooperation across silos, localized decision-making, and information sharing, I hope to write about in future blog posts. In this blog, however, I will discuss how the structure of Team of Teams fits with DISTek and how we are setting up our organization to be adaptable to growth.
Another year has come and gone and many eventful happenings took place in the history of DISTek. We may look back at 2015 as a turning point due to the substantial changes we made in all aspects of our business. Those end-of-the-year cards you get in the mail always seem to be bragging a little too much, but that is just what I am going to do because I think the year DISTek had is worth bragging about.
Procuring software engineering services from a proven contract house has many benefits, which you already know if you’ve ever been cornered by one of their sales team members. As an engineer I know that there are always tradeoffs which must be made, and getting outside help on a project is no different. One possible way to maximize the value and effectiveness of contract software engineers is by the use of pair programming. Pair programming is an Agile software concept I was introduced to during my time working with a client, however it can be shoehorned easily into any development process. Pair programming simply means getting two engineers to sit together at the same workstation, often with two keyboards, to work together on a software solution. There are well documented benefits of increasing speed and learning while reducing mistakes and costs. In my experience, those benefits are compounded when using the services of a software contractor.