|
Does your eat a lot of pasta?
veni bibi saltavi
|
|
|
|
|
We might remedy, I'll be in the UK in a couple of weeks
Thank you and happy birthday to your son!
|
|
|
|
|
Happy birthday, sir!
Just out of curiosity (and if you don't mind me asking), how old are you now?
You have just been Sharapova'd.
|
|
|
|
|
|
Happy birthday, Carlo!
/ravi
|
|
|
|
|
|
Again? The bugger did this last year as well!
veni bibi saltavi
|
|
|
|
|
Happy Bday enjoy @CPallini
Life is all about share and care...
public class Life : ICareable,IShareable
{
// implements yours...
}
|
|
|
|
|
|
Hello!
(This is not a do my homework for me, its more please help me find sources if you can)
Basically, I have an assignment and I need examples of IT case studies of project failures for:
[X] Lack of user involvement - Mars Rover Project - Counting NASA as the user
[X] Long or unrealistic Time Scales - TAURUS
[X] Poor or no requirements - Using a personal example (Hope he accepts it...)
[X] Scope Creep - (Using TAURUS as my study)
[ ] No change control system - Need to find something!! ;-;
[X] Poor testing - HM Revenue and Customs
If anybody is willing to help me locate some case studies which are of UK projects I would be most grateful, the materials provided by the class are of mostly non UK projects, which is 'slightly' stupid as he wants UK examples...
I've tried googling, but all I can find is 200 PDFs of why projects fail and US examples, nothing which is really applicable ;-;
modified 19-Jun-15 6:24am.
|
|
|
|
|
Oh, I know some pretty examples of all of the above and may add some myself:
- Poor or no leadership
- No or utterly insane software architecture.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
And i second those
#region(start signature)
Life's like a nose, you've got to get out of it whats in it!
#endregion
|
|
|
|
|
Same here, I work as a junior system administrator (well, more in a lead position as I'm the only SysAdmin there) and I have some crazy stories of the system which would fit a few of these, just not sure I'd get away with it for the assignment...
|
|
|
|
|
Add "MOD" to your search query - that's where the real horror stories live... see ComputerWeekly[^]
|
|
|
|
|
Department of Health and individual health trusts can top anything in your wildest imaginings.
|
|
|
|
|
|
Yeah sorry, I made a mistake in a QA answer last week.
|
|
|
|
|
TAURUS should give you every possible failure; especially time frame and scope creep.
Look also at any government IT project.
veni bibi saltavi
|
|
|
|
|
Good point, I was debating on using TAURUS inside time frame to replace the one I have, I managed to trace the case study to Denver University. Using TAURUS for scope creep and Time frame should save my behind a reasonable amount, the teacher is a royal pain in the ass at times and I know he'd be willing to send it back just because a case study isn't a UK one :/
|
|
|
|
|
One more:
- Team - incompetent, not trained, over-dependence on search-engine results .
For case studies, not sure whether companies / corporates will ever make public their internal project reports (including failed ones).
A dated (1996) book where several case studies are presented is "Rapid Development" by Steve McConnell. Though dated, some of these case studies are still relevant, and independent of country (can happen in US, UK, anywhere). You can read some case studies in the Amazon preview.
modified 19-Jun-15 3:29am.
|
|
|
|
|
But that's still a management problem.
|
|
|
|
|
Agree.
One small point: 'Management problem' is like an umbrella term, and this is one of the sub-bullets there.
|
|
|
|
|
Project methodologies are all fine and dandy however we know that they rarely get used, as they are meant to be used, because the world is far to complex to be encapsulated into a project methodology.
The two principle causes of failure that I have seen for IT projects are:
(1)No experience in previously implementing IT projects - combined with too much pride to admit to this.
(2)Not learning from experience of previous projects - again pride in not owning up to previous failures and not taking corrective action.
These two sum up what I consider to make successful projects - you can study as many project methodologies and design patterns as you want. However you will make mistakes and keep making them if you do not learn why you made those mistakes and change your behaviour based on this experience.
A good project manager will be able to assess the competency of their team and will be able to factor in extra time for the mistakes that will be caused by the unexperienced team members.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
|
|
|
|
|
|
Shamefully it seems to matter to the teacher which is the ball-ache, Just got in lesson with him now so going to speak to him, hopefully he might be able to shed more light onto it.. Hopefully, but I have doubts as to him helping with it...
|
|
|
|