![]() |
Home
|
Project Delivery
|
Methodology |
|
Choosing the correct Methodology |
|
|
PMR's preferred Methodology is derived from current best practice such as DMAIC, Prince 2 and Rational/RUP. Different 'flavours' can be tailored to meet the precise project/programme needs. For example, IT and development projects will almost certainly require an iterative approach in order to minimise business risk. Project Management is fundamentally about the Business Case and the Project Deliverables. |
|
|
Business Case Part of the Business Case is concerned with capturing the client's requirements. Rational Software believe that this is best done using visual modelling and Use Cases. |
|
|
|
|
|
The above (courtesy of Rational Software) gives an indication of the top level of a Use Case specifying part of a library system. Each element can be drilled down into for further detail/information and additional diagrams illustrate flow, state transitions, deployment and interaction. This technique is extremely powerful and is applicable to business and technology projects. The aim is to facilitate the capture of clients and users requirements in a form which can be understood by all parties. There are a number of documents which help capture the Business Case, which can be summarised in a single document - a Vision Document. This and a Glossary represent the minimum requirements for creating a successful project. |
|
|
Deliverables The Requirements translate into a series of Deliverables which need to be made. Critical Success Factors (CSF's) are those deliverables which must be made for the project to be regarded as a success. A key element of modern methodologies, which applies to most types of project, is that of iteration. |
|
|
|
|
|
Traditionally, projects have used the Waterfall process where requirements are cast in stone at the start of the project and all change is resisted. The result is that business risk does not start to fall off until the end of the project life cycle. An Iterative process breaks the project down into a series of smaller projects, or iterations, each of which tackles specific deliverables and each of which is designed to eliminate business risk early. This type of approach recognises that change is a natural part of the project lifecycle, welcomes change and manages it - but only at the ends of iterations. PMR's methodology favours these elements where the project type permits, and our own business tool, Project ToolSet, utilises process and method to create and manage projects based on these principles. How PMR can Help ?
|
|