a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 #

letra de crooked alignment - awol (nerd)

[intro]
rapid, raci, ratsi… (whatever)
i don’t care what you call these things,they don’t decide anything at all
what you need to do is straighten out that crooked alignment

[verse]
there’s a number one blocker in large orgs, there is no denying it, (nuh, uh)
bring together two different teams, there’s escalation or alignment, (call the boss!)
it’s not that they can’t agree on the overall right direction, (my way!)
it’s mostly about each individual team’s prioritization, (nuh, uh)
team a needs team b’s api, but team c controls the acls, (no way)
team c needs teams d, e, and f, (come on!) but f can not be hassled
-groan-
we rely on a process called rapid and it’s anything but
six months fly by while we verbally joust while sitting on our b-tts
month 1 we’re arguing about what are the project’s requirements
month 2 we’re arguing about fast follows for well past my retirement
month 3 we’re arguing about our date for a date that’s some time in month 4
month 5 we’re arguing the scope changed, by month 6 it changes even more, (come on, guys!)
and the sad truth is all these problems are “miscommunication”, (what’d you say?)
terms like “platform” or “ownership” lead to discombobulation
-gas face sound-
requests go ignored, prs unapproved, folks can’t even talk nice
-phhhlllpppppbbbt-
but just remember you’re on the same team watching the same stock price
-money cha-ching-
[bridge: teddy roosevelt awol]
we are against crooked business, big or little
we are in favor of honest business, big or little
you got that right, teddy
now let’s show ‘em how it’s done

[verse]
break out the level, time to uplevel, and let’s fall in line together
crooked alignment’s a feedback loop applying nasty pressure
this is why we engineer our principles no matter what feelings are felt
they help decision-making when things get unexpectedly difficult
team a needs team b’s api and the interface is well-defined
onboarding is self-service, teams c, d, e, and f pay them no mind
directly responsible individuals lead us to a decider
they’re there to close the gap between teams, not make it any wider
month 1 we agree that we don’t need any engineering design docs
month 2 we agree that we can easily work with just ui mocks, (back of the napkin folks)
month 3 we agree about our date for launch that’s some time in month 4
month 5 we agree on wine at the launch party, by month 6 we’re counting score
because we’re part of the same system, we shouldn’t need alignment, we should just align
worry about just heading forward, you’ve already left the wrong path behind
otherwise, you’ll still be veering off road, act before it’s far too late
adjust that alignment cross your org until your team is finally straight

- awol nerd

letras aleatórias

MAIS ACESSADOS