Same as us - we actually had our formal re-introduction to Scrum done by Cochango just 2 weeks ago.
Agile and ITIL - what is it (in laymans terms!)
- Thread starter ~J~
- Start date
Same as us - we actually had our formal re-introduction to Scrum done by Cochango just 2 weeks ago.
Associate
- Joined
- 2 Sep 2007
- Posts
- 874
- Location
- Scotland
'Agile environment' means hot-desks and flexi-time.
ITIL - pretty sure it's a network protocol.
HTH
ITIL - pretty sure it's a network protocol.
HTH
When was this?
2 years ago
And did you sleep through as much of it as I did?
Seriously though, I've seen half-implemented ITIL, bits chosen here and there, incomplete CMDB's, etc - but at the end of the day it never really seems to work the way it should do. Better than nothing I suppose though.
![[DOD]Asprilla](/styles/overclockers/avatars/8.png){kind=avatar}
Soldato
- Joined
- 10 Nov 2003
- Posts
- 14,034
- Location
- Surrey, by the river
That wasn't my understanding, but anyway; development of an existing production system is small changes. If they had put the production line is using Agile, then you'd have a point. Unfortunately putting a single machine in a plant doesn't actually achieve anything.
Soldato
- Joined
- 19 Apr 2004
- Posts
- 4,793
- Location
- London
There's no reason why you can't take the concepts of agile and implement them for waterfall. You do the same thing as in Scrum, but call them "phases" instead of "sprints".
I did that to a Prince2 guy that I know, who still works in a waterfall environment. His response? "Oh, yeah, that's a great idea a series of very small, measurable delivery phases...I wonder why no-one thought of it before!"
But then it would just be iterative development - and you'd lose out on the other benefits of agile. Iterative development certainly has benefits for organisations that can't afford to go fully agile but it also poses problems as well.
I don't really understand why it has taken so long for companies to adopt lean thinking like Agile practices anyway. Such ideas have been around for decades and organisations are still slow to pick them up.
Soldato
- Joined
- 10 Nov 2003
- Posts
- 14,034
- Location
- Surrey, by the river
Becasue they are difficult to implement. Lean Sigma has been around for donkey's years, but actually getting a Sigma (Six or Lean) project up and running, accurately identifying your defects etc is a world away from what people know and understand.
Even in companies like Amex, where just about everyone has been through Six Sigma training it's just too difficult for most people without some serious will power and a pretty big change in corporate attitudes.
Soldato
- Joined
- 19 Apr 2004
- Posts
- 4,793
- Location
- London
No, but they were certainly an influence to the guys that created agile. Agile takes ideas from Toyota but also people like Volvo who did a lot of work on team autonomy.
Hehe, I did an ITIL foundation course last week and I can't remember much of it. Hence me not knowing what a CMDB is. I'm involved in Incident/Problem/Change management to varying degrees. Everything's in a bit of a mess atm, with bits of ITIL implemented in some areas but not others.
Soldato
- Joined
- 19 Apr 2004
- Posts
- 4,793
- Location
- London
[DOD]Asprilla;13806010 said:
It's certainly difficult, but there have been lots of companies that have started up since then who could have embraced such ideas during startup rather than gone down the old fashioned route. I'd just expect a lot more innovation in the IT sector than what I've seen so far, although I'd be keen to know more about the inner workings of companies like google.
Soldato
- Joined
- 10 Nov 2003
- Posts
- 14,034
- Location
- Surrey, by the river
In most start-ups the employees have come from somewhere, and its a lot easier and comforting to go with what you know that to try something completely different, especially if it is your own company.
There are very few innovative people who are willing to take the risk.
There are very few innovative people who are willing to take the risk.
Soldato
- Joined
- 18 Oct 2002
- Posts
- 9,637
- Location
- Xbox Live
Agile is an attempt to reduce the cost of implementing IT solutions, whilst accepting that requirements will be changed dueing the course of the project
ITIL is an overhead, implemented to manage change. (but sadly needed because humans work in IT and by their very nature can not be trusted)
ITIL is an overhead, implemented to manage change. (but sadly needed because humans work in IT and by their very nature can not be trusted)
Iterations and 'release early, release often' were directly from Toyota and Matsu****a factories. We're talking 70s and 80s. Their production lines use Agile, not just the R&D guys. Nowadays they are more like Kanban; i.e. no iterations - simply because everything gels so well they don't need to stop throughput to arrange the next iteration.[DOD]Asprilla;13805956 said:
Agile is not soley about reducing cost. Too many people are too quick to jump to that conclusion. Agile is about delivering value early. It is about adapting, for both the team and the business. It is about feedback, it is about communication, it is about getting what you actually want, even if you don't know what that is yet. It cannot be summarised into "cost reduction"
Now Kanban I'm fully aware of, but while I was working at Toyota, never once did I hear about "Agile", and this was only last year.
Soldato
- Joined
- 18 Oct 2002
- Posts
- 9,637
- Location
- Xbox Live
It was a 1 liner ffs
and ultimately costs will be reduced if all you said above (which I agree with) happens on the project.