Change Management is one of those terms I never fully understood until I took a step back and said “WTF does that actually mean?!” The same could be said for some of the newer and currently “trendy” terminology in our industry, like DevOps, Delivery Engineering, Configuration Management, Internet of Things… Until you take a step back and consider what these terms really do mean in practice, how they relate to one another and how they’re different, it’s likely that you will only relate to the term as a buzzword-that is, something that means whatever it means to you. Here at Bitlancer, leading-edge terminology is all about what we’re actually doing with our clients. Here are some current projects we’re working on:
- Successful migration of multiple organizations from dedicated infrastructure to appropriate public cloud providers. We’re proponents of “letting your stack (and your DevOps mindset) decide” whether you prefer services with an inherently “ephemeral” or “persistent” bias towards virtual servers. It’s all about finding the right balance of abstraction, insight and control.
- Implementation of configuration management tooling (Chef, Puppet) to support a full continuous delivery pipeline for building, testing and deploying infrastructure code. - Architecting for AWS: CloudFormation, Auto Scaling Groups, and instance configuration with configuration management tools like Chef and Puppet.- Streamlining, standardizing and centralizing the management of authentication and authorization of instance access on public cloud infrastructure, to support growing teams.
- Training: In our world, “training” usually consists of teaching people all about what we’ve done for them so they can and will actually use it instead of avoiding it. Which is really important! There’s nothing worse than doing a bunch of work for a client and then having them just be confused by it. Not only does it put a buzz-kill on an ongoing relationship, but also it means that we don’t get to pass along our knowledge… which is a huge part of the value we add.
- Ongoing support for customers. Support is a lot like ongoing training; it focuses on helping clients get the most use and value from whatever tooling or processes or infrastructure we’ve helped them put in place. Questions come up, changes need to be made, new people need to ramp up… We love being part of all that.
- Extending your “DevOps Team:” While I dislike the term “DevOps Team” almost as strongly as I dislike the term “DevOps Engineer,” Bitlancer staff often functions as an extension of a client’s automation/tooling team. It can be good to have some extra hands on deck when things get broken and/or the team needs to complete certain tasks that are tricky and/or time-constrained. If we can help an organization embrace a DevOps mindset and put together their DevOps puzzle along the way, so much the better. What’s key in this context, however, is that the work we’re doing is core to your goals, and that your organization can invest sufficient time to support us.