Nik Gupta’s Post

What people get wrong about measuring engineering velocity: Velocity metrics (lead time, cycle time) are not good performance metrics. They're good diagnostic metrics. Every business and team wants to ship value to customers faster and more predictably. When people talk about engineering velocity, they usually mean, “How fast is work being done?" and "How do we make it go faster?” Every team, service, and business is unique, so there are no standard benchmarks for velocity. When using metrics, it's crucial to understand their purpose and what you hope to achieve from measuring them. Engineering metrics are helpful for 3 reasons: 1. They enable you to measure over time, allowing you to see progress and regressions. 2. They act as a “guardrail” to take action if things go off track. 3. They can inform decision-making around investments that lead to improvements. Measuring is not helpful without action. Metrics that aim to measure “velocity” are typically incomplete proxy indicators, so they should be treated with caution. If a project takes a long time to complete, it might be because it’s a big, complex project that is supposed to take a long time. That’s perfectly OK. You must be careful when interpreting data. You can't use velocity measures to compare teams since they are inaccurate and lead to incorrect assumptions. Use velocity as a diagnostic metric to improve processes and remove bottlenecks, making stakeholders, customers, and engineers happier. ~~~ ✍️ What are your thoughts on engineering metrics like this?

💡 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

🚀 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.

💡 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

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!

Precision beats power and timing beats speed - Conor McGregor, Companies do not know why systems engineering has a benefit? For many companies it is only the question how to fill DOORS or Polarion. Additionally, many System Engineers waste meetings for discussions about the right wordings, definitions. Time is just wasted - If developers are invited, more money is wasted. Organizations create so much chaos. Developers are working under chaotic conditions. Agile way of working is so much more speed. But what is speed, when just more cost is wasted because information is not well distributed? They do not get the right information about interfaces and functions they have to develop. Usually they bring their codes to the cars and nothing is working. Everybody asks, what is the benefit of systems engineering? For Automated Driving this becomes even more safety-critical and is an honest concern. 💡But right Systems Engineering is so much more effective In fact, Systems Engineering's main purpose is "Make sure, that Interfaces are clear and functionalities are defined and tested in time" In other words. Systems Engineers are modern technical leaders. They make sure that people are talking to each other about the products to be developed in order to satisfy the stakeholders. The main job of an SE: First Priority: -Define functionalities based on stakeholder needs and development constraints -Make sure different teams have continuous exhange and fixed interfaces -Make sure functionalities are verified & validated In order to do that: -Choose methods that fit to your purpose -Tailor your processes to your purpose -Use existing tools that fit to your purpose Purpose is built over time. So don't waste time. Act. What's your opinion of systems engineering?

Happy New Year! This blog post aims to explore the key aspects of thinking like an engineer in both testing and developing, drawing parallels between everyday tasks and engineering strategies. And remember: the first step to being good at something is to suck at it! #newyear #engineer #devops

TEST EARLY TEST OFTEN / CONCURRENT ENGINEERING | Engineering that Begins with the End in Mind  https://lnkd.in/eJhY55zt

In engineering, chaotic systems start predictably but soon go off course. To handle this, we use feedback loops that constantly adjust and correct, keeping things stable despite the unpredictability. This is how control theory turns chaos into order, ensuring systems stay on track. This idea applies to our lives too. Just like in engineering, adapting and responding to life's unexpected twists helps us stay on course and reach our goals. Control theory isn't just for engineers—it's a way to think about resilience and strategic planning in our everyday lives.