When Your Project Manager Goes Full Sith With Absolutes And Ever-Changing Requirements
Description
The meme is a white page of black serif text, styled like a blog article. A large bold headline reads, “Is Your Project Manager A Sith Lord? Three Ways To Find Out.” Below, two numbered bold sub-headers appear: “1. He deals in absolutes.” and “2. He keeps altering the deal.” Each bullet is followed by paragraph text explaining that software engineering is full of grey areas but the Sith-like PM sees only black-and-white action points and deadlines, and that he continually adds new features despite agreed-upon specs. Quoted phrase marks around “for the good of the project” emphasize unwelcome scope creep. Technically, the joke skewers rigid management mind-sets, unrealistic deadlines, and constant requirement changes - classic pain points for engineers working with project managers
Comments
6Comment deleted
Our PM froze the release date in carbonite, then force-pushed three new epics into the sprint - turns out he’s added a fourth axis to the CAP theorem: C for Creep
The real dark side is when they say "I find your lack of velocity disturbing" while simultaneously adding three more epics to the sprint that's already at 200% capacity
Every senior engineer knows the PM who 'alters the deal' mid-sprint - you agreed on three story points, but now it's five 'because we're already touching that code anyway.' The Sith Lord comparison is apt: both wield absolute authority, both ignore the nuanced reality of complex systems, and both somehow convince leadership that adding 'just one more feature' won't delay the Death Star launch. The real tell? When your PM says 'I am altering the deal, pray I don't alter it any further,' except they definitely will, and your sprint retrospective becomes a therapy session about scope creep and the dark side of stakeholder management
When the PM says "pray I don’t alter it further," I rename the branch to release-2025-infinity and switch the burndown to a burn-up - entropy and scope creep are both monotonic
Sith PMs don't just alter the deal - they refactor requirements mid-sprint, praying you don't notice the breaking changes
Our PM is definitely Sith: estimates are absolutes, buffers are “a lack I find disturbing,” and any spec freeze is just carbonite until the next stand-up when he alters the deal