| Date :
Next version of Risk
Analysis ...
Date : September 30,
2003
This project is the
most doable project out of all four and the team
consists of four members. These reasons have raised the
expectations among the customer and the project manager.
The manager and the customer can be tempted to increase
the scope and this can be a risk to the project. We can
avoid this risk by focusing on the critical requirements
of the project and ignore the fancy features until we
have built a system that handles all the basic
requirements.
The team members might
get little complacent and not stick to the schedule
since the project seems doable to begin with. We can
avoid this by sticking to the schedule and To-do list no
matter what and never letting the schedule slip for even
a single day.
We might get tempted to
use new tools like dot net or XML and in process get
behind the schedule. We can avoid this by deciding as
early as possible on the tool and start learning it.
We have decided to
follow extreme programming in our project but we are
still not sure about the extent to which we would stick
to extreme programming. We might start building a
prototype a little too early and then build on that. The
risk here is that in order to get something up and
running quickly we might not concentrate much on the
process of software engineering like requirements,
design or use cases. This might be fatal for the project
and we might build on something, which is not designed
properly. The way to avoid this is to have the courage
to throw something, which is not designed properly if at
all we follow XP all the way during the development.
Another way to avoid the risk is to concentrate on the
requirements and the design part of the software
development before even writing a single line of code. |
