Why won't programmers give useful feedback to upper management?
Is it that hard to take 15 minutes of your day to update your project's status?
We always have to hire expensive project managers or else everything goes to hell, without a nanny around programmers are literally like incompetent clueless children.
Are all programmers autistic like this?
Dealing with programmers is by far the most bullshit part of being in upper management, not even customers are that bad.
Because programming is not operating a press where at the end of the day I can just say "I used X of raw material and made Y pieces of half-product".
Also, sometimes I may be working on something that's more on the inside of the program so I can't really fire up a new screen or whatever and say "yeah, I did this today".
I have never worked with you personally but not everything is easy to quantify when you don't know how everything should be done.
I often get asked how far I am and is expected to give them a percentage like I would know something like that.
It is a bit easier if it is divided into smaller projects, but exiting problems usually take a couple of days and thus, a percentage every day is hard to estimate.
What I personally prefer is scrum.
We used that (or a version of that, probably, never saw the difference) that worked really well.
We kept everyone informed by having small meetings and then we knew who to go to and how far people were, what was holding them back, etc.
I'm not actually a project manager, I'm the project owner.
We use Scrum, and the programmers I'm complaining about usually have piss easy 1-2 day long stories that were carefully crafted for them, I was a developer in the past I know how a little pressure feels, but going a whole month without giving a report or outright refusting to participate in weekly meetings is just ridiculous, some programmers are just that autistic.
my experience with scrum & scrum """"masters""""
>So what have you done yesterday anon?
>I did this and that
>Any road block?
>Let me create a story
>There is no need, I fixed it, as it was a road block
>I see.. What are you gonna do today?
>This and that
>Any road block
>I'll tell you when I get here
Pretty much worthless if you ask me senpai, wasting 30 minutes everyday listening to people's crap for nothing and trying to anticipate things you don't have control over. Pure madness.
Pure madness is not doing anything to measure your projects and try to stay on schedule, sure, it is fun being the cool boss that doesn't helicopters around the development room, but from my experience all that leads to is the programmers browsing 4chan/reddit/facebook/Youtube/whatever wasting their time all day.
Programmer here. I'm dealing with people like you every day at work. We update the oroject's status when we're 100% sure it's working properly and, especially, that's exactly what you asked. Because usually we can't just say "oh it's fine" or "hey anon we're proceeding". There are bugs that could come out of nowhere after the compiling process or during the testing. So unless you want a technical report (which probably you couldn't even read without someone explaining it) just let us do our job.
Divide and conquer. Smaller tasks == shorter sprints. If you can't Divide it into shorter tasks, don't bother programmers until the sprint is done.
Let them come to you if they need something from you. Be available as project managers.
my experience without scrum & scrum """"masters""""
>"What are you doing, programmer?"
>"I'm swapping all the program's icons with spinning skulls"
>"Why? did the customer ask for that?"
That's when I decided I had to hire a project manager.
What information do you expect to obtain from the weekly meetings that you cannot obtain from whatever tool you're using to track completed user stories?
I'm sure you've given them a way to contact you in case they need you, right?
So...? Why waste time with meetings and not just let them develop?
t. Project Owner
>going a whole month without giving a report is just ridiculous
if the management doesn't request one, why would I care?
>refusting to participate in weekly meetings is just ridiculous
The madness lies where the people who write the code is in charge of everything.
If the project is big, you should make a plan for the project.
What parts should be created, in which order, how should they be tested, who should write the tests, who should write the tasks etc.
Just tossing people a project they are not ready to handle is just asking for problems