Headlines from today state that the new Trump administration will put a 25% tariff on imports from Mexico, and Canada. Additionally, a 10% tariff on goods imported from China. A tariff is a fee charged by the Federal government on goods coming into the country. That fee is paid by the importer, not the exporter. For example, Target wants to sell PlayStation in their stores, so they purchase them from Sony, who builds these in China. Target receives the shipment of PlayStations, where they will be charged the tariff. Target pays the tariff to the Government to receive these goods. Target then must decide how to recoup the additional fees. They can either choose to eat the cost and reduce their revenue, or they can increase the selling cost. The outcome is a combination of the two. As a result, consumer prices, specifically for food and cars are going to go up. And businesses lose money by having to pay tariffs and selling few items. For th...
I have the privilege of attending AWS Re:Invent conference from 02-Dec to 06-Dec. Here's my planned schedule for the week. Sunday, 01-Dec Depart MSP @ 6:45pm CST Arrive LAS @ 8:12pm PST Monday, 02-Dec Design Secure and resilient relational database architectures on AWS Observability-driven development AWS Fundamentals for the accidental SQL Server database administrator Unleashing AWS Agility with Terraform How to navigate your SQL Server Migration journey with AWS Deep Dive into Amazon DynamoDB using Design Puzzles Visionaries in the Stadium w/ Angela Duckworth and some AI folks Tuesday, 03-Dec Identify and manage Amazon Aurora & RDS Snapshots Scalable database solutions with Aurora PostgreSQL Limitless Database Data models for Amazon Neptune using GenAI and diagram-as-code tools Deep Dive into Amazon Aurora query plan management Bingo Night Hashicorp Customer Reception @ Chica Wednesday, 04-Dec AWS Re:Invent 5k Race Essentials for migrating from Oracle to Amazon Aurora...
In the previous post, we argued that estimation is a smell—a signal that teams are compensating for unmanaged uncertainty. Velocity, as a direct descendant of estimation, inherits that smell. Scrum reminds us that the purpose of a Sprint is to produce an *Increment of value* , not to consume a predetermined number of points. Velocity measures effort expended inside the team. Customers, however, experience outcomes: features delivered, bugs fixed, and capabilities unlocked. No customer has ever benefited from a higher velocity. Why Velocity Persists Velocity survives because it is visible, numeric, and easy to chart. It gives leaders something to point at and teams something to optimize. Unfortunately, that optimization rarely aligns with value delivery. When a measure becomes a target, it ceases to be a good measure. When velocity becomes important, teams respond predictably. Estimates inflate. Stories are sliced to satisfy point targets rather than user needs. Lower-risk, lower-valu...
Comments
Post a Comment