Development Articles
 
Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
User Name:
Password:
Remember me

The Shed is going Social! Join us on FaceBook and Twitter and chime in on the conversation.

Go Back   Dev Shed ForumsOtherDevelopment Articles

Reply
Add This Thread To:
  Del.icio.us   Digg   Google   Spurl   Blink   Furl   Simpy   Y! MyWeb 
Thread Tools Search this Thread Rate Thread Display Modes
 
Unread Dev Shed Forums Sponsor:
  #1  
Old May 21st, 2003, 02:35 PM
Ducani
Guest
Dev Shed Newbie (0 - 499 posts)
 
Posts: n/a  
Time spent in forums:
Reputation Power:
Risky Business (part 1)

Risky Business \(part 1\)

May 21, 2003 - Successful developers know that the secret to the success of a project lies in managing the risks that might unfold during the course of the project. In this article, find out how to build a comprehensive risk management plan that allows you to complete your projects on time, every time. for full article.

Please discuss this article in this thread. You can read the article here .

Reply With Quote
  #2  
Old May 24th, 2003, 09:13 AM
nao's Avatar
nao nao is offline
junior vice president
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Jan 2002
Location: Springfield
Posts: 251 nao User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 12
Question Confused.

I read the article twice.

I think Risk Management is a difficult subject so I applaude the author for writing the article. There are many useful pointers for anybody involved in project management - basics such as good monitoring/auditing practices that are essential.

However, I think the article is too 'shallow' to be of any practical use. There are no real formulas to apply and where the author has made an attempt to formulate an approach (RE, RC, RRL) the initial conditions are more 'qualitative' than 'quantative'.

For example:

Risk Exposure (RE) = 'The probability of occurrence x Impact Risk Exposure

How do I calculate 'probability of occurance' in the first place?

I cannot think of how to begin quantifying the risk of one of my top programmers leaving in the middle of a project due to x, y or z reasons.

It just felt like I was reading the 'glossary' in the back of a book on Risk Management for Dummys.

I would ask the author to include some case-studies in the next installment, to use real numbers and instances so we can work though the motions.

I don't know, what does everybody think?

Nao

Reply With Quote
  #3  
Old May 24th, 2003, 09:42 AM
Jcaputo's Avatar
Jcaputo Jcaputo is offline
Kiss My Converse!
Dev Shed Intermediate (1500 - 1999 posts)
 
Join Date: May 2003
Location: Davie, Florida
Posts: 1,520 Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level) 
Time spent in forums: 2 Weeks 1 Day 19 h 26 m 5 sec
Reputation Power: 338
I think you have some valid points - writing an article like this is a delicate balance between writing a case study and writing an article that would appeal to someone whose knowledge base on this topic was limited - and trying to find a balance between the two.

Reply With Quote
  #4  
Old May 27th, 2003, 01:22 AM
melonfire melonfire is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Mar 2002
Posts: 45 melonfire User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 12
We only intended the article to be a very basic introduction to the topic, and this is stated at the outset itself. Please do NOT treat this as an in-depth course, it is not supposed to be (and something of that sort would also probably not be very valuable to most readers here as well).

All we were attempting was to provide a basic appreciation of the raison d'etre of the science of risk management

And yes, a case study will be included in the second part, together with links to more detailed material...coming soon

Reply With Quote
  #5  
Old May 27th, 2003, 10:07 AM
nao's Avatar
nao nao is offline
junior vice president
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Jan 2002
Location: Springfield
Posts: 251 nao User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 12
can't wait!

Melonfire,

I wrote that review as objectively as I could (see 'nao' above). I'm not trying to be nice for the sake of being nice - if it was a crap article, I would have said so! - but I think it was a good intro. I think I went into it thinking, "$h*t! I need to read this!"...

I re-read my posting - the part where I wrote:

Quote:
It just felt like I was reading the 'glossary' in the back of a book on Risk Management for Dummys.


It came out wrong - I now realise that it WAS intentionally written as a breif summary - sorry about that!

But hey, now you got me hooked for part II!

Best,

Nao

Reply With Quote
  #6  
Old May 27th, 2003, 10:12 AM
Jcaputo's Avatar
Jcaputo Jcaputo is offline
Kiss My Converse!
Dev Shed Intermediate (1500 - 1999 posts)
 
Join Date: May 2003
Location: Davie, Florida
Posts: 1,520 Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level)Jcaputo User rank is Major (30000 - 40000 Reputation Level) 
Time spent in forums: 2 Weeks 1 Day 19 h 26 m 5 sec
Reputation Power: 338
Nao

If you havent done so already, I highly recommend signing up for the Weekly DevShed newsletter, which will tell you when part II is actually posted.

Reply With Quote
  #7  
Old May 27th, 2003, 11:55 PM
melonfire melonfire is offline
Contributing User
Dev Shed Newbie (0 - 499 posts)
 
Join Date: Mar 2002
Posts: 45 melonfire User rank is Just a Lowly Private (1 - 20 Reputation Level) 
Time spent in forums: < 1 sec
Reputation Power: 12
nao - No problem. Keep coming back and telling us what you think, it helps us get better at it

Reply With Quote
  #8  
Old May 28th, 2003, 10:04 AM
Ducani
Guest
Dev Shed Newbie (0 - 499 posts)
 
Posts: n/a  
Time spent in forums:
Reputation Power:
If you would like to see an article covering a particular topic, please post your request here.

Reply With Quote
Reply

Viewing: Dev Shed ForumsOtherDevelopment Articles > Risky Business (part 1)

Developer Shed Advertisers and Affiliates



Thread Tools  Search this Thread 
Search this Thread:

Advanced Search
Display Modes  Rate This Thread 
Rate This Thread:


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
View Your Warnings | New Posts | Latest News | Latest Threads | Shoutbox
Forum Jump

Forums: » Register « |  User CP |  Games |  Calendar |  Members |  FAQs |  Sitemap |  Support | 
  
 


Powered by: vBulletin Version 3.0.5
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.

© 2003-2013 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap