Skip to main content

A Project Management Method - Graphically

The real life business process entity is shown as an integral part of this workflow method because it requires a certain numbers of cycles to analyse, capture and structure all processes needed for the next phases. Depending on the complexity of the process, each phase might need to provide feedback for verification and/or request consensus and/or new information in order to proceed with the next phase of the workflow.

Waterfall Model
Path 1-3-5 describes a classical waterfall model ... maybe the first approach in managing a software development life cycle (SDLC). The various phases A-B-C-D are carried out sequentially but its progress is shown as flowing downwards as a water fall.
The waterfall approach gives the idea that the next phase will start when the water reaches the bottom of the fall, but it's also a way to quantify work (results) as a function of time (see diagram below).

For optimization purposes, activities within phases should be analyzed using the Project Network Diagram technique and, hence, phases could overlap.

Iterative Approach
An iterative approach is a method for delivering application functionalities in an incremental way, i.e., a single iteration can results in one or more deliverables and each deliverable represents a percentage of work to be performed. The degree of percentage of work should be such as to yield some tangible results. The result of an iteration is then used as input to the next iteration. The next iteration could take place in the same phase or the next phase, depending on its results and on the predesignated methodology policy. This process is repeated recursively until completion of an application (or project) is achieved.

The following example graph is the RUP (Rational Unified Process) from IBM  and it illustrates the iterative approach.
Iteration I1, E1, C1, C2, C3, C4, T1, and T2 are similar to sub-phases and can be tailored to meet the needs of an organization.

N.B. - This post is to be completed.

Popular posts from this blog

The differences between Project, Operation and Program

We said that a project is defined as a temporary endeavor that consumes resources, incurs cost and produce deliverables over a finite period of time to achieve a specific goal. They come in all shapes and sizes and can vary in length or complexity.

Operation type activities are similar to project activities in that they too produce deliverables, consume resources and incur cost. However they are on-going or repetitive in nature, hence they are not project activities or tasks. Some examples of operation activities are weekly maintenance of databases, paying invoices or help desk operations activities.

Programs are much larger than projects. They are made up of many projects and on going activities such as operation type activities and are similar to projects as they consume resources, incur cost and produce deliverables. However programs are more complex and include repetitive operation type activities such as maintenance work, facility administration etc, and are funded typically on a…

Forecasting Project Costs using Variance Analysis

One way to report on cost control and forecasting during project execution is to use the Variance Analysis method, that is, explaining the difference (or variance) between actual costs and the budgeted costs with numbers and make new estimates for completing the work. Please consult this link Earned Value Management for related literature and references.
For the purpose of making these calculations, I will use an hypothetical project example (but it could also be a task or phase). "A company has contracted a service provider to deliver a project in 10 working days (80 hours) for the estimated cost of $10,000 and a work effort of 200 hours. The contract is Time and Material, this means that the company pays the provider for the number of hours actually required to perform the service. So, the provider has no incentive to minimize the number of hours expended on the service. The less efficient the provider is, the more money it makes!"
Summary of Time and Material Contract (re…

Using PERT for estimating tasks

A simple way for estimating tasks is to use the PERT (Program Evaluation review technique) weighted average method. This method uses a weighted average duration estimate to calculate task duration, it gives the opportunity to take into account information based on different types of estimates values (such as poorly defined areas, probabilistics, and ranges for the schedule). This method is based on the Beta distribution model because it can model events which are constrained to take place within an interval defined by a minimum and maximum value. (For this reason, the Beta distribution is used extensively in PERT, CPM and other project planning/control systems to describe the time to completion of a task).

The term weighted average means that the equation uses weighted factors to calculate the expected task duration.
The equation and process modelling a task for PERT is the following:  E=(O+4M+P)/6 (equation)  E= Expected Value  O= Optimistic Value (this is equivalent to a minimum val…