In levels 1 and 2 of the Degree (and HND) we teach you various methodologies such as SSADM.
At level 3 we expect some discernment. Is there a down side to methodologies? What are the pros and cons?
In this section we shall
"Methodology" originally meant the study of methods.
However, it is now widely used to mean a set of concepts and techniques to be used together. A rigorous and complete process containing phased activities, deliverables, baselines, standards, and reviews encompassing the life-cycle of development, management, and support of software, hardware, or systems.
I used to be a methodology addict but I'm much better now
The methodology addict believes that if you tip information into the hopper, crank the methodology handle and grind through all the stages and components, a useful system will magically appear out the other end. It won't, but a depressing number of software engineers never grow out of this belief.
Methodologies don't deliver systems - people do.
Question: What obstacles make this impractical? What is the alternative?
PRINCE (PRojects IN a Controlled Environment)
Another UK Government method in the public domain
Not a step-by-step "how to run successful projects" system
Suggested responsibilities for the steering board, PM, quality assurance and so on
Time, costs, quality, how to handle problems
Meetings, reports, quality reviews
Methodologies provide standards for:
Are they used properly?
Are they just labels to give people the impression that the organisation
is well run?
Do they really help?
Should they be prescriptive?
|Other topics||Comments please to: firstname.lastname@example.org||© 1999, University of Glamorgan|