We are a group of dedicated software professionals committed to increasing the knowledge of risk management and general software project management skills for ourselves and others. We have come together as a team in the context of a graduate level course on Software Project Management at George Mason University. Within that context we have been exposed to the three essential elements of effective software management: People, Process, and Product (a.k.a. The Three P's). We have constructed this website in order to gain new insights into the software project management process and increase our knowledge of one of it's most important elements: effective risk management. This site is both our product and the documention of our process.
We hope that you find the information on risk management helpful and the description of our management process instructive. We invite you to post comments and questions on our Risk Management Bulletin Board.
Software Reuse.
(MS Word 6.0)
In this paper, K. Jordan explains the costs and benefits of software reuse, focusing on a
product line approach to software development.
ISO 9000-3 and Compliance Risks For Organizations.
(MS Word 6.0)
In this paper, D. May explores the hidden risks of complying with the international
standard of software quality!
Managing Risk with Metrics.
(MS Word 6.0)
In this paper, P. McNeece proposes using common software project management metrics as a
tool to identify and track risk items.
Quality and Risk Management.
(MS Word 6.0)
In this paper, R. Miller discusses how quality software techniques are both a contributor
to, as well as a mitigator of, a software development program's risk.
Keeping a Good Software Team.
(MS Word 6.0)
In this paper, A. Mirantes talks about common problems and possible solutions for
keeping and motivating a software team.
Does Configuration Management Mitigate Project Risk?.
(MS Word 6.0)
In this paper, J. Mundell presents common software development activities and their
associated risks while exploring what if any effect the role of configuration management
has in controlling or reducing those risks.
Use of Earned Value Management to Mitigate Software
Development Risk.
(MS Word 6.0)
In his paper, P. Young explores how Earned Value Management
techniques can be used for risk identification and monitoring on
software development projects. He also investigates the use of
Software Inspections for work package definition as part of the Earned
Value Management program.
To build our site we performed activities such as requirements gathering, identifying objectives, assigning tasks, developing, testing, managing change, and of course dealing with RISK! We describe these activities in the following types of documents:
And of course our status reports and test results show our progress over the course of
the semester!
MJY Team Documents
Even serious topics like software and risk managment need a little humor...
Levity.
For the sites of other class teams see
other SWSE 625 sites.