Slackers need not apply

[dsc]

Dunno what pull requests are but to be fair I've seen plenty of people that can't do the bottom two. Developers or whatever sitting on the outskirts not saying a word on meetings. I put it down to most developers being socially awkward or something. The offshore guys are often particularly bad at this as well.
I've also suffered working with people who are too arrogant for their own good and when you finally dig in to the problem it's ballooned beyond help. And the crap contractor that just floats it and wasn't dynamic enough to be able call for help.
[...]

In a standard scrum you go around the room and talk about issues that each dev has got allocated, so there's no way to skip anyone or to not say anything. Yes you need a scrum master or some lead who knows what the hell is going on, but this is the bare minimum. To me it seems like the company has no idea what they are doing.

It's like hiring a bricky and stating in the job ad that they need to be able to tell you what they've done during the day or what their plan is for the current day.

[Gibbon]

https://www.atlassian.com/git/tutori...ncing/git-pull

Basically its setting out your workbench to start coding.

You Pull (get central code store from repository)
you code locally.
then you push & commit (to repository).
If you are lucky and the pile of fetid spaghetti compiles then hurrah!

One would hope you do the above for each major JIRA request.

I think the job spec means the dev raising pull requests to merge their changes into master which usually triggers a review in the atlassian toolset. The reason is to stop people trying to upload huge lumps of unreviewable code in one go. If multiple devs are working on the same repo then you need to pull from it at least everyday to make sure you're working on current code. If it's only you then no need. Each Jira should have its own branch or be split into sub tasks and sub branches if assigned to multiple devs.

[DrewG]

Saw this on a job posting today for an (inside) contract role:

Job Requirements (partial list):

• Pull requests will be expected multiple times weekly
• Expected to be vocal in scrum calls and give updates daily
• Expected to be self-starting but willing to ask for help - sitting on an issue for days will not be acceptable

Is this company being reasonable? Or does that sound like a red flag/toxic place to work?

I have worked with several contractors who made a habit of 'sitting on an issue' for weeks on end. Averaging less than one commit a week, even when given relatively simple tickets to complete.

Should of been none of my business, but i often got dumped with the work these slackers did not complete on time.

It's sounds like they've had tulip devs before, it also sounds like they are tulip at managing devs, it also sounds like they are tulip at hiring 'managers of one' and want to micromanage manage you with their tulipty daily scrum calls.

Who really needs a daily call? Well written updates go on update tickets please.

37 signals model is the only model I'd work under if I were to go back to being a dev.

[TheDude]

It's sounds like they've had tulip devs before, it also sounds like they are tulip at managing devs, it also sounds like they are tulip at hiring 'managers of one' and want to micromanage manage you with their tulipty daily scrum calls.

Who really needs a daily call? Well written updates go on update tickets please.

37 signals model is the only model I'd work under if I were to go back to being a dev.

I produce a tailored PPT for each standup.

[wattaj]

Who really needs a daily call?

Never underestimate the power of a well managed daily call to build a cohesive team during a fully remote project.

Note the "well managed" bit. I've seen bot sides of this and it only works where the guy in charge knows what the **** is going on.

[northernladuk]

Never underestimate the power of a well managed daily call to build a cohesive team during a fully remote project.

This. I'm not on the project side so can't comment on scrum and the like but I'm running ELS which is bumpy to say the least and daily defect and ELS calls are keeping us afloat at the moment.

On the comment about going round the room so can't miss anyone, that might be the case but some people's updates are the bare minimum to the point of almost being misleading. Sorry to say but our offshore friends tend to be the worst offenders with updates being 'It's OK' day after day or requiring a grilling to get the real detail out.

[wattaj]

Sorry to say but our offshore friends tend to be the worst offenders with updates being 'It's OK' day after day or requiring a grilling to get the real detail out.

^^ **** yeah!

[vetran]

I'm going to offer another opinion. Estimates are crap, they are guesses at best, based on experience of something similar you may have done.

The idea of penalising a dev because they are a day behind annoys the hell out of me. I've often got into something and felt that I could make it better for the customer if I spent a bit more time on it. Or I'm delayed because something I assumed was simple turns out to be hard. When you are on top of a dev for being a day late all you will get is people rushing the work. I get tired of refactoring other developers' work because they clearly rushed it and in turn made my day a little more difficult.

I feel sorry for you though if that's the environment you are in.

I have been through it with a number of different scrum masters, some are better than the others. The good ones understand the times are a guide. However whenever people start obviously dragging feet or even if the complexity is now understand it then its the masters job to get on top of it.

On one current project the PM is the scrum master and is very supportive. If concerned he will take it offline and have a chat with anyone involved, he has me occasionally helping other devs on reporting and sometimes he says oh I agree that isn't clear let me get the system architect and lets all have a chat.

Gilding the lily if you are on fixed price or transparent T&M are not acceptable, our current project is fixing an app another company screwed up. The customer is getting effectively a fixed price to deliver what the other lot promised, any extra work comes out of our bottom line that is a clear business decision.

Neither of these are unpleasant just the correct way to do it.

[vetran]

This. I'm not on the project side so can't comment on scrum and the like but I'm running ELS which is bumpy to say the least and daily defect and ELS calls are keeping us afloat at the moment.

On the comment about going round the room so can't miss anyone, that might be the case but some people's updates are the bare minimum to the point of almost being misleading. Sorry to say but our offshore friends tend to be the worst offenders with updates being 'It's OK' day after day or requiring a grilling to get the real detail out.

Jira has good reporting, use it to nail the jelly to the wall. You don't have to do it publicly.

[woohoo]

Neither of these are unpleasant just the correct way to do it.

When you put it like that it sounds great