Burgett Consulting

Did you know that companies with CI/CD pipelines and automated testing see up to 60% higher team efficiency? (Puppet). By automating repetitive tasks, Platform Engineering teams free up developers to focus on feature development rather than bug fixing and manual deployments. It’s all about working smarter, not harder.

Don't have a platform team yet? Or are you tired of wasting developer time setting up automated test suites? Let our experienced team help you set up the infrastructure you need so your team can focus on shipping features.

Platform Engineering teams are becoming essential to modern software development. According to Puppet, over 80% of high-performing organizations have dedicated platform teams that manage CI/CD pipelines, automate deployments, and standardize development environments. These teams are crucial for driving efficiency and reducing errors, allowing developers to focus on what they do best—building great software.

Is your company leveraging platform engineering yet? If you are not yet taking advantage of platform teams then reach out to us so we can get you on the right track. Let our experience help your team set up the infrastructure you need so your team can focus on shipping features.

Earlier I posted about the R.A.I.D. framework for project management. One thing I don't like about it is you often lose sight of important Decisions and Tasks while your focusing on Assumptions and Dependencies etc... For my projects I like to use my own framework I call the D.I.R.T. framework. Let me break it down for you!

Decisions - These are important action points for your project. Especially in the IT world you run into situations where you have to pick one way or the other. Documenting these decision points is key when you get to the end of a project and stakeholders ask why a key feature was changed or why a screen was altered.

Issues - Can't escape this one! Issues usually materialize out of Risks and you have to track them. Every project will have Issues that arise, but you can usually handle them with a Decision. Such as 'we are only going to migrate data after x date so we don't need to clean the old legacy data'. Documenting issues and the decisions taken to address them is key for any project.

Risks - These are prevalent with any project. An API might work differently than you scoped the project, or a library that is key to the project might lose its support or backers. I always like to tie Risks back to a Decision also so that we know 'if this happens we will handle it this way'. Just helps keep the project going.

Tasks - This seems very straight forward but Tasks are one of the most important things you need to track in a project. As part of this you do need to track dependancies too, but I like being able to add tasks to a project and link them to a decision or a risk or issue.

You could argue this is semantics, but for most project management systems your creating lines in a spreadsheet or cards with dependencies. Tracking Decisions, Issues, Risks and Tasks as line items in your project this way makes it super easy for anyone involved to see your blockers or problems or what your working on. Plus its fun to say 'show me your project's DIRT!'.

Got an IT project that needs some help? Feel free to pm me or respond to this post.

Considering a Migration from Office 365 to Google Workspace or Vice Versa? Here's How to Prepare:

Data Inventory:
- Catalog all the data that needs migration. Is it client-related or personal employee data?
- Encourage team members to centralize their critical data in a common space like SharePoint or Google Drive. This approach simplifies the migration process, allowing the migration team to manage data effectively. Post-migration, the migration team can assist in redistributing the data to individual accounts.
- Use a spreadsheet to track key files and folders, ensuring all critical data is successfully transferred. Otherwise you might forget something!

Email and Account Inventory:
- Determine the number of email accounts needing migration. Consider whether old accounts are necessary and if calendars and contacts should be included in the migration. The volume of historical data to be migrated can influence the migration timeline.

Validate Domain Ownership and Access:
-If you're changing domains or need email forwarding setups, ensure access to modify DNS and MX records is available. This step is crucial for redirecting emails properly.

Plan Your Migration Day:
- Select an optimal date and time for the migration. We recommend scheduling during periods of low activity, such as a long weekend, to minimize impact on daily operations.

Looking for Expert Guidance?
If you need assistance or have questions about migrating your company, don’t hesitate to reach out. Send us a message or leave a comment below, and we’ll help you navigate through the process for a smooth transition to your new platform.