Hendrik Dahmke: Product Velocity Requires a Shared Understanding
In this guest post, Hendrik Dahmke examines Product Velocity from the perspective of a systems engineer.
Product Velocity is a new approach that enables companies to learn faster, make decisions more quickly, and deliver results.
Agility Requirements Attack security Architecture Automotive Barcamp Digital transformation Eclipse GfSE Hardware Innovation Integration Communication Complexity Conferences Artificial intelligence MBSE Modeling Traceability Openness PLM Product development Processes Quality ReConf Interface Semiant Security Software SpaceX Standards SysML SysML v2 Systems thinking Systems Engineering TdSE Tim Weilkiens Traceability Transformation Trends UML Video Christmas Further training Tools

In this guest post, Hendrik Dahmke examines Product Velocity from the perspective of a systems engineer.

The four value streams in product development are features, defects, risks and technical debt. We need to optimize these.

Creating stakeholder value should be the goal of product development. The entire organization must be geared towards this.

Removing blockers quickly is an indication that agility is practised in the organization. Saab Aeronautics can do this in an hour.

Industrial DevOps finally brings speed to product development. This fits in with my own book Product Velocity.

After frameworks like SAFe failed to deliver, Bryan Finster shows in this case study how Continuous Delivery has enabled agility.

Agility in requirements management has many advantages, but also needs structure and guard rails, such as quality gates.
Unfortunately this website uses cookies! The website also works without cookies, but then you won't be able to watch videos or leave comments. You can decide for yourself what you allow. Data protection comes first - we promise!