Swarmia’s Post

Are you still relying on your issue tracker or using a spreadsheet to manually track the progress of cross-team engineering initiatives? If you nodded yes, this blog post is for you.

Keeping tabs on cross-team engineering initiatives is not easy. Ideally, you’d have a solution that: 🔹 Combines planned work from your issue tracker with completed work from your code repositories 🔹 Updates automatically In this blog post, we discuss how you can get just that.

Beyond mere developer productivity, what are the three fundamental principles that drive engineering impact? This post delves deeper into these 3 pillars:  - Alignment with business goals - Engineering excellence - A developer-friendly environment Share your thoughts in comments!

💡 Spend just 3 minutes and gain a valuable insight into a structured approach that transforms ideas into solid solutions according to established systems engineering good practices. This approach is ideal for those aiming to navigate the complexities of product development with ease and precision. 🛠️ #SystemsEngineering #ProductDevelopment #StructuredApproach

“Traditional” engineering is broken. The way we do engineering hasn’t changed since we invented the “Waterfall Model” in the 1960s. Big OEMs, and everyone else as a result, have been using the Waterfall Model as the standard of engineering since the 1950s. The Waterfall Model was effective in projects with stable, well-defined requirements. For instance, in the Apollo missions, this model enabled a structured, sequential approach to software development. With minimal changes and high risks involved, the model's systematic progression ensured thoroughness and reliability crucial for the mission's success. However, the requirements of today’s engineering has changed and it’s demanding more than the waterfall model — that’s why we’re building Flow Engineering. In Flow, stages evolve based on immediate feedback, not just at project's end. Flow gives you a dynamic, interconnected approach, a stark contrast to the linear confines of the Waterfall Model. That approach exists today, we’ve built it at Flow Engineering. The future of engineering isn't set in stone. It's fluid, it's agile, and you can build it with Flow Engineering.

🚀 Unveiling the Secrets to Solution Development Success! See our latest post where we decode the structured systems engineering process. 🛠️ From abstract ideas to real-world solutions, get the blueprint to navigate complex projects with ease. 🌟 Don't miss out on our "Engineering Clarity Infographic" you can download at the end of the article.

Read on to download a framework that you can use to measure the maturity of your engineering teams on the discipline of "engineering excellence". Continuing my series on Developing and Improving Engineering Capability, I have now published the second article that dives into the topics of "Engineering Excellence". In this article I have also provided a free framework that you can use to hopefully measure the maturity of your engineering teams on the disciplines that are crucial for engineering excellence. Thank you very much Bankey Sharma for your guiding thoughts and your unwavering commitments towards excellent peer reviews. The articles won't be the same without your watchful eyes over them. Please do share your thoughts here or on the article as they help me understand what brings most value to you and thus helps me concentrate my efforts on those topics. Thanks! #engineeringmanagement #engineeringexcellence

💡 Spend just 3 minutes and gain a valuable insight into a structured approach that transforms ideas into solid solutions according to established systems engineering good practices. This approach is ideal for those aiming to navigate the complexities of product development with ease and precision. 🛠️ #SystemsEngineering #ProductDevelopment #StructuredApproach

The Two Hardest Problems Engineers often joke that there are only two intractable problems in engineering… 1. Naming things 2. Off by one errors If you know anything about engineering, you know that this isn’t far from the truth. However, the truth is also that… Oftentimes, half the battle for business and product leadership can be disambiguating and naming things well. Names are very, very powerful. Obviously, they are essential to creating easy symbolic handles that people can use to refer to complex concepts or objects quickly. However, names, if used precisely, can be far more potent than that. They can also be used to… 1. Clarify the utility of a concept or entity E.g. Movie Search Page 2. Clarify the distinguishing characteristics of the given concept or entity from other concepts or utilities (particularly those that could be confused or conflated together) E.g. General Movie discovery vs Movie Search 3. Motivate and animate everyone toward a shared vision E.g. Movie Search 2.0 - Featuring Next-Gen Ranking 4. Imply a namespace for adjacent concepts that fit together - helping to map the concept space E.g. Movie Search, Movie Recommendations, Movie Rankings 5. Help drive important and implicit understanding in the problem domain E.g. I never mentioned the company I'm referring to in the examples, but I bet you could guess which one would have such features/concepts in their product. These few examples clearly show that naming things carefully can be a superpower for product and business leaders. It can be a key technique to accelerate everything from internal discussions, consensus building, and team alignment to external product marketing and sales.