• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Collapse

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

  • You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
  • You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  • If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

Previously on "Agile/SCRUM and IR35"

Collapse

  • too_many_details
    replied
    regardless of what you think of this whole Agile movement (of which SCRUM falls under), it is a fact that it currently is commanding the best software development rates outside Investment Banking.

    Personally, I have found that I enjoy my work more and feel less stressed working in this way. I'll leave the evaluation of its effectiveness over typical waterfall methodologies to the bean counters.

    R

    Leave a comment:


  • NotAllThere
    replied
    Originally posted by NickFitz View Post
    Pair programming is part of Extreme Programming (XP), not Agile or Scrum.
    Yeah, I didn't RC... The rest was true though.

    Leave a comment:


  • thunderlizard
    replied
    Scrum isn't so bad - actually I think if a person with common sense but no project methodology knowledge was suddenly given a load of work to get through, some people to do it, and somebody else to advise on what needed doing first - they might well independently invent Scrum. It is one of the simpler ones.


    Some of the key points of Scrum are
    -the developers choose what to work on
    -the developers manage themselves
    -the deliverables are split up until they're small enough for 1 person to handle, so there's minimal 'collaboration'
    Done properly, it's all about giving people space to do things, and "direction and control" should be conspicuous by its absence.

    But as usual, it all depends on how you're doing it.

    Leave a comment:


  • NickFitz
    replied
    Originally posted by NotAllThere View Post
    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.
    Pair programming is part of Extreme Programming (XP), not Agile or Scrum.

    Leave a comment:


  • Devlin
    replied
    Originally posted by someone has my name View Post
    Scrum / SCUM agile .. its all a hunk of junk
    From what I'm seeing of it, I have to agree. Amazes me how enthusiastic some seem to be about it though!

    Leave a comment:


  • SueEllen
    replied
    Originally posted by Peoplesoft bloke View Post
    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.
    Save your money and google.

    Leave a comment:


  • someone has my name
    replied
    Scrum / SCUM agile .. its all a hunk of junk

    Leave a comment:


  • Peoplesoft bloke
    replied
    Originally posted by NotAllThere View Post
    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.

    Leave a comment:


  • NotAllThere
    replied
    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.

    Leave a comment:


  • Bluebird
    replied
    Originally posted by Peoplesoft bloke View Post
    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...

    Leave a comment:


  • Peoplesoft bloke
    replied
    Originally posted by Bluebird View Post
    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.

    Leave a comment:


  • Bluebird
    replied
    Originally posted by Peoplesoft bloke View Post
    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....

    Leave a comment:


  • Peoplesoft bloke
    replied
    Originally posted by Devlin View Post
    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.......

    Leave a comment:


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

    Leave a comment:


  • Devlin
    replied
    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.

    Leave a comment:

Working...
X