What are some signs that your project at work is ending?
ItsASine (Kayla)

ItsASine (Kayla) @itsasine

About: Azure DevOps and git admin with a weird interest in résumés and portfolios 🎉 Lawful Neutral

Joined:
Feb 4, 2017

What are some signs that your project at work is ending?

Publish Date: Oct 23 '18
30 10

I've been on multiple projects at my current workplace and am wondering if other people have the same signs that a project is sunsetting. Note: I'm not a lead, so I'm one of the ones that only officially knows day-of that I'm being reassigned.

Common themes from my past projects:

  • The PM gets another team and blows off your meetings in favor of theirs
    • Possibly includes other shared services style people like scrum masters, lawyers, marketing, customer service types, that sort of thing
  • Recurring meetings are updated regularly to extend the end date another month
  • The pressure to have a fleshed out backlog of work eases up
    • Note: you must still maintain the appearance of a backlog to not make the grunts suspicious
    • Whether or not things are fully vetted (and whether or not anyone higher up cares) before being marked ready is the larger indicator
  • (on a ridiculously large team) Multiple people are being spun off in waves

And my possible one from today which prompted this post: One-off events that are taking time away from engineering are not to be rescheduled for after the release because of Reasons. Or maybe I'm just being paranoid.

People who have been through multiple reassignments or project ends, what have you noticed as a trend?

Comments 10 total

  • Ben Halpern
    Ben HalpernOct 23, 2018

    Great discussion! I don't have a lot of big org experience, but from freelancing in my past, communication tends to get less frequent until they basically ghost you.

    • Ben Halpern
      Ben HalpernOct 23, 2018

      Startups:

      • Founders are excited about some new shiny thing.
      • ItsASine (Kayla)
        ItsASine (Kayla)Oct 23, 2018

        Oh man, I just saw on LinkedIn a CEO/founder I know added being CTO/Founder of another startup to his profile. RIP my friends at his old place.

    • Frank Carr
      Frank CarrOct 24, 2018

      Yep. I've had that done when working as a contractor. It's pretty dumb since I was a contractor. Why not be up front about it?

      As an employee, you get sidelined doing support and doing nothing, like they hope you'll just leave. Or else, they'll figure out a way to "reduction in force" you like giving you a bad review or the like. Once again, a dumb and often dishonest way to do things.

  • dev-head
    dev-headOct 24, 2018

    Here's some I have seen in the past...

    • significant changes to scope.
    • feedback ignored/dismissed.
    • crickets/dear-in-headlights when you ask about the next phase.
    • pushing back on deadline is impossible, regardless to scope change(s).
    • team member(s) re-assigned
    • service is down but no one cares to tell anyone about the outage, let alone fix it.
    • ItsASine (Kayla)
      ItsASine (Kayla)Oct 24, 2018

      pushing back on deadline is impossible, regardless to scope change(s)

      Heh, sounds like most of my projects were doomed from the start ;)

    • rhymes
      rhymesOct 24, 2018

      service is down but no one cares to tell anyone about the outage, let alone fix it.

      My post about breaking the login is exactly this 😬

  • rhymes
    rhymesOct 24, 2018

    I've experienced PMs being reshuffled but also finding out from other employees because upper management didn't bother being upfront with contractors 🤔🤣

    I've also worked on absolutely pointless prototypes because market research wasn't done and then when the truth caught up it was suddenly not a priority anymore ✌🏾

  • Antonio Radovcic
    Antonio RadovcicOct 24, 2018

    From an agency-perspective it is a good indicator your company is being phased out by a client when they hire other agencies/freelancers to work on the same thing.

  • Josh Hawkins
    Josh HawkinsOct 28, 2018

    In my experience, it was any of these

    • team isn't meeting expectations but can't easily be replaced
    • developers gossiping about other projects more than normal
    • developers not being challenged enough
    • project costing more money than it produces, while management diverts attention to new projects
Add comment