Project management program logic diagram

Medium-term outcomes are what you would expect to follow on from the short-term outcomes you have identified. So if you have identified an increase in staff or parental knowledge as a short-term outcome, the medium-term outcome is likely to be the application of that knowledge, for example a change in behaviour. Inputs are the resources that you have which you are able to draw on to address the problem identified in your problem statement. It is good to think of both the material resources e.

The activities are the things that you do. This is likely to include running the program and training staff. It might also include developing a program manual and resources, or providing referrals to families. It is good to be specific about the numbers of program sessions you will run.

This describes who will be involved. It is good to clearly define the target group for your program and include relevant information about this population group for example age or cultural background. As well as the target group, you should include information about staff and others that may be involved e.

Making assumptions explicit is a really important part of the logic model. Assumptions are the beliefs we have about our program, the people involved, and how it will work. Unexamined assumptions are a big risk to program success. Shakman and Rodruiqez suggest asking "what is known, and what is being assumed?

It is worth spending some time on this section, and asking a range of people involved in the program to help you identify a full list of assumptions so you can address them. This element of a program logic requires you to consider the environment in which your program is being delivered. Economic, political, cultural, historical and social contexts all impact the way your program is delivered, and the outcomes that you can achieve.

Likewise, your program has potential to impact some of these factors too. For example, a change in the demographics of an area may mean you need to reconsider the target group for your program. We have developed a downloadable logic model [PDF, KB] checklist that you can use to review your draft logic model.

This checklist is slightly adapted from a worksheet in the University of Wisconsin-Exchange logic model resources:. Once your program logic is completed, it is a useful tool to plan your evaluation. The outcomes columns in the project will give you an idea of what you should be trying to measure.

It is good to try to measure both short and medium term outcomes. It is more difficult to measure the long term or impact outcomes, as the impact usually takes a long time to be realised, and there are many external factors that affect it, making it difficult to establish how much of the long term or impact outcome was the result of your program, and how much was the result of external factors.

The following may be particularly useful:. Templates, resources and a free online course are available through the University of Wisconsin-Exchange. A workshop toolkit Logic models for program design, implementation, and evaluation and a reference guide Logic models: A tool for designing and monitoring program evaluation from the US Department of Education.

Evaluation framework for health promotion and disease prevention programs from the Victorian Department of Health and Human Services. Lawton, B. Logic models: A tool for designing and monitoring program evaluations.

Washington, DC: U. McCawley, P. Idaho: University of Idaho Extension. Spreadsheet Editor. Data Widgets. Photos Effects. Visual Paradigm Desktop.

Photo Books. Diagrams Features Logic Diagram Software. Logic Diagram Software. Make a Logic Diagram. Create Logic Diagram faster and better. General Purpose Latch. Logic Diagram Example. Alarm Circuit Transformation. Sums of Products. Signal Expression. Products of Sums. Feature Highlights. Easiet Diagram Maker Easy drag-and-drop tools to help you create diagrams in minutes. Integrate with MS Office Integrate seamlessly with MS documents, spreadsheets and presentations to maximize productivity.

Easy Export and Sharing A wide range of export options that supports your sharing and publishing needs. High Quality Templates Create professional diagrams using a variety of templates. Seamless Collaboration Collaborate in real-time on the same diagram at the same time. A project can have start and finish milestones as well as intermediate milestones. It is also represented on a Node and is usually drawn as a small circle.

It logically comes after Predecessor s in a Project Network Diagram. Two related nodes are separated by a unidirectional arrow. Predecessors are shown towards the arrow tail while successors are shown towards the arrow head. Sub-network — It is simply called as a subnet. It is a subdivision or a part of a complete Project Network Diagram.

Dependencies — A Successor dependent node can have more than one predecessors. Similarly a predecessor can have more than one successors. To understand the logical relationships between two activities, we should look at each activity as a set of two distinct events. These are:. So, for two related activities, we will have two sets of S and F events respectively.

For these two sets, we can have four type of logical relationship between them. These Modifiers do not change the nature of a logical relationship. They just change the Start and Finish events of the dependent activities.

A lead accelerates the Successor activity whereas a Lag delays it. Project Network diagram is one of the many ways to represent project schedule.