Agile/SCRUM and IR35

[Devlin]

Another team at my client's site is phasing in Agile management practices of which SCRUM is a key parts. With Sprints and fluid task allocation the order of the day with Scrum teams, it occurs to me that it could be deemed more "employee like" that having specific projects to work on.

What are people's thoughts on this?

[SueEllen]

Another team at my client's site is phasing in Agile management practices of which SCRUM is a key parts. With Sprints and fluid task allocation the order of the day with Scrum teams, it occurs to me that it could be deemed more "employee like" that having specific projects to work on.

What are people's thoughts on this?

Are you contracted to work on specific project(s)?

Do you have any say in the allocation of tasks?

I know when I worked using agile development methodologies (which are never implemented as they should be) I could choose what tasks I did if I spoke up first.

[Devlin]

Good question. Not sure about that level of detail. I'm guessing it will be rolled out to my team in the next few months so will have to find out what it means for me.

[ratewhore]

I would have thought an industry recognised way of working is IR35 neutral. However, the devil is in the detail as SueEllen rightly says...

[Peoplesoft bloke]

Another team at my client's site is phasing in Agile management practices of which SCRUM is a key parts. With Sprints and fluid task allocation the order of the day with Scrum teams, it occurs to me that it could be deemed more "employee like" that having specific projects to work on.

What are people's thoughts on this?

Ahem

What the crikey is this new managementspeak.

Proud to say I've never heard of it - but curious to know what utter utter utter nonsense they've dreamt up now.......

[Bluebird]

Ahem

What the crikey is this new managementspeak.

Proud to say I've never heard of it - but curious to know what utter utter utter nonsense they've dreamt up now.......

it means you do stuff on the back of a fag packet friday lunchtime, and Go Live on monday morning....

[Peoplesoft bloke]

it means you do stuff on the back of a fag packet friday lunchtime, and Go Live on monday morning....

Oh right, what my ex-colleague used to call ultra complex implementations with a project timescale of one nanosecond - just the usual stuff, then.

[Bluebird]

Oh right, what my ex-colleague used to call ultra complex implementations with a project timescale of one nanosecond - just the usual stuff, then.

yeah, usual thing - they just give it a different name every couple of months when a load of projects go tits-up...

confuses the users no end...

[NotAllThere]

It's not a managementspeak, it's geek-intelligentsia-programmerspeak. There's some neat ideas (IIRC, for example, that two people working together on one item is more efficient that two people working seperately on two items), and for some projects it could work very well. But most will treat is as the hoped for universal panacea, not do it properly and bin it after a few years.

[Peoplesoft bloke]

It's not a managementspeak, it's geek-intelligentsia-programmerspeak. There's some neat ideas (IIRC, for example, that two people working together on one item is more efficient that two people working seperately on two items), and for some projects it could work very well. But most will treat is as the hoped for universal panacea, not do it properly and bin it after a few years.

Thanks for this - looks like a trip to Waterstones may be in order before someone laughs at me for not knowing about this - anyone got a book recommendation? Sorry for the thread hijack btw.