Software Project Management Brochure Template Page 15
ADVERTISEMENT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29Software Project Management
15
•
enforcing the feedback mechanism in the development process, in order to
detect inconsistencies in design as early as possible and reduce the costs
of fixing them.
Risk Assessment
In order to prevent project runaways, meet deadlines, stay within the project's
budget, and simultaneously maintain the product's high quality standards, it is
essential to timely identify and periodically evaluate certain critical factors. Such
factors include [1], [10], [29], [30]:
•
estimating the project's size in the early phases - the project's size affects
how the deadlines will be set up, and is positively correlated with
monetary expense and risk;
•
setting up the deadlines realistically - as a result, the necessary time to
establish the rhythm of the project, prevent delays, and enter a steady state
in which the effort is equally distributed from the beginning of the project,
without putting an extra workload to the team members at the end of the
project phases;
•
collecting and studying reports on other similar projects - this provides the
possibility of learning from the other projects' and other teams'
experiences; in that sense, a process data base is essential for an
organization that wants to go higher than Level 2 on the CMM level
ladder; engineering management depends on measurements, and their
proper use, and this data base is to be regarded as an organizational asset,
and it is to be properly managed;
•
top management commitment - if top management does not play a strong,
active role in the project from initiation through implementation, then all
other risks and issues may be impossible to address in a timely manner;
•
failure to gain user commitment - when the users are actively involved in
the requirements determination process, it creates a sense of ownership,
thereby minimizing the risk that the end-user expectations will not be met
and that the system will be rejected;
•
timeliness of additional user requirements - it is essential to have the users
involved in the development process from the beginning to the end;
however, it is highly preferable to have the requirements frozen at a
certain point in development;
•
familiarity with technology - the higher the organization’s experience
with application languages, technology databases, hardware, and
operating systems, the lower the risk in the project;
•
insufficient/inappropriate staffing - the risk of failing to provide adequate
staffing throughout the project can be mitigated by using disciplined
development processes and methodologies to break the project down into
manageable chunks, and developing contingency plans;
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Business