Project Management

Please login or join to subscribe to this thread

Risk Management in Agile projects - how do you control, monitor, identify them?

linkedin twitter facebook   Agile   Information Technology   Risk Management  
avatar
Cristina Maciel Saint Laurent, Quebec, Canada
Risk Management in Waterfall projects are clearly defined, but in agile projects, most of the Scrum Master/PMs have the idea that they don't need to control or analyse risk. How do you do it today?
Sort By:
< 1 2 >
avatar
John Herman . Us, Aa, United States
Jan 24, 2017 4:40 PM
Replying to Cris Casey
...
@John -

While I agree with your comment at the conceptual level, I have found in practice "joint" or "shared" responsibility means no one is responsible. From another angle, it is unreasonable to share fiscal risk, for example, on a team member who is not charged with any fiscal responsibility and can take no direct steps to mitigate it.

So while there is no denying all project teams share in the outcome of their respective projects, properly managed risk (across a myriad of areas) must ultimately be owned by single individuals who have the ability and responsibility to take the necessary actions to avoid, reduce or eliminate it. Otherwise, and I think you'll appreciate this based on your blogging topics, a great deal of waste will be generated by folks who can't do anything to address the risks at hand.

Kindest regards,

- Cris
At every status meeting, and/or stand-up, we quickly review risks within the team. Yes, you are correct that developers generally can't share fiscal risk, just as sponsors can't share in most of the technical risks. I'm sorry if you interpreted my comment such that all of the project risks are shared across all of the project team. It's not a communal risk pool. The team as a whole should be aware of all of the risks, even if they can't control some of them because it's possible that ameliorating risk in one area could exaggerate it in another. Reviewing the risks at each meeting also helps keep them somewhat in the forefront of the team's thoughts.
avatar
Anonymous
Dr. Royce' paper in 1970 that is considered the definition of Waterfall can be found here
http://agileconsortium.pbworks.com/w/page/...ing%20Waterfall

This does not gives you any method to manage risk.

In my view the risk management as defined in PMBOK is project management approach and has very less to do with software development lifecycle is use.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Don't worry about people stealing your ideas. If your ideas are any good, you'll have to ram them down people's throats."

- Howard Aiken

ADVERTISEMENT

Sponsors