Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Tom Zeppenfeldt Ophileon
(:GRAPH) - [:DESCRIBES] -> (:RESULTSCHAIN)
 A graph is the most generic of data
structures, capable of elegantly
representing any kind of data in a highly
accessibl...
 A results chain is a tool that shows how a
project team believes a particular action it
takes will lead to some desired ...
(:RESULTSCHAIN) with transition nodes
Activity Output Outcome Impact
 As a linking point to attach transition indicators ...
(:RESULTSCHAIN) linking transition indicators and version
Activity Output Outcome Impact
Transition
indicator
Transition
i...
(:RESULTSCHAIN) versions compared
Activity
Output
Outcome
Impact
Transition
Version
Version 1 Version 2
(:RESULTSCHAIN) versions compared (version nodes hidden, laid out)
Version 1
Version 2
Activity
Output
Outcome
Impact
Tran...
Upcoming SlideShare
Loading in …5
×

(:GRAPH) - [:DESCRIBES] -> (:RESULTSCHAIN)

971 views

Published on

Thoughts on describing results chains in graphs, including versioning.

Published in: Technology
  • Dear Ophileon, thank you very much for the clarification downloadable address. I got it now.

    Thanks again,
    Bari
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Hi Blake , glad to read that it's clearer now :) BTW my friends call me Tom.

    Perhaps some additional remarks. Using graphs (so nodes and transitions) is not just handy when you need versioning for your results chains (RCs). Especially when you have more complex RCs, you can query the database to find answers to the following questions:
    - who is responsible for activities leading to a specific outcome?
    - if I scale down an activity, which outcomes will be impacted?

    Furthermore, it is possible to interlink RCs, contributing to a more precise and dynamic description of the real environment.

    So, you can do a lot of fun stuff with it. Using graphs for this purpose is still very young, so we're doing some research to find out the best implementation.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Ophelion,

    Thank you for the clarification and I better understand the purpose, at which you succeeded! It shows that simplifying log frame for some purposes is desirable. Log frames are by design more prescriptive, and this is a bit more descriptive, but also perhaps a bit closer to reality; for when something does not go as planned in the log frame, revisions are far from simple. Your results chain in a database would be easier to adjust.
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • @Blake : Thanks for your feedback. Although your comments are completely valid, the objective of this slideset was just to illustrate that, using currently available technology, it is relatively easy to store different versions of a resultschain in a database. When you compare it to the logical frameworks that are in many cases quite static presentations of project logic, flexible and versionable results chains allow for keeping a history of changes in project logic (e.g. because of changing environments or priorities) that can be audited.

    The :TS and :TE point to Transaction Start and Transaction End as they are stored in the database, and together with the yellow TRANSITION node, they form a transition between one step of a results chain and the next.

    @Lotiful

    Too bad that they took it down :( Fortunately, I still got my own version.. downloadable at https://drive.google.com/file/d/0B94bY8aQjI1HRHRXN0s1Qkc0UU0/edit?usp=sharing

    There's also this interesting document http://www.focusintl.com/RBM025-RBM%20HANDBOOK%20ON%20DEVELOPING%20RESULTS%20CHAINS.PDF. The example on page 78 inspired me to build this:
    http://www.ophileon.com/img/resultchain.png
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Thanks Tom. I am fully agree with Blake Gentry. We need more detail.
    I could not open the link of slide 3 which is http://www.fosonline.org/wordpress/wp- content/uploads/2010/09/FOS_Results_Chain_Guide_2007-05.pdf
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

(:GRAPH) - [:DESCRIBES] -> (:RESULTSCHAIN)

  1. 1. Tom Zeppenfeldt Ophileon (:GRAPH) - [:DESCRIBES] -> (:RESULTSCHAIN)
  2. 2.  A graph is the most generic of data structures, capable of elegantly representing any kind of data in a highly accessible way. (from : http://www.neo4j.org/learn/graphdatabase) (:GRAPH)
  3. 3.  A results chain is a tool that shows how a project team believes a particular action it takes will lead to some desired result. (from : http://www.fosonline.org/wordpress/wp- content/uploads/2010/09/FOS_Results_Chain_Guide_2007-05.pdf) (:RESULTSCHAIN) Activity Output Outcome Impact
  4. 4. (:RESULTSCHAIN) with transition nodes Activity Output Outcome Impact  As a linking point to attach transition indicators for monitoring  As a way to keep historic versions of a results chain  Each transition between steps of the results chain is split up into (:STEP) – [:TS] -> (:TRANSITION) – [:TE] -> (:STEP) TS TE TS TE TS TE
  5. 5. (:RESULTSCHAIN) linking transition indicators and version Activity Output Outcome Impact Transition indicator Transition indicator Transition indicator Transition indicator Transition indicator Transition indicator Version 1 Version 2
  6. 6. (:RESULTSCHAIN) versions compared Activity Output Outcome Impact Transition Version Version 1 Version 2
  7. 7. (:RESULTSCHAIN) versions compared (version nodes hidden, laid out) Version 1 Version 2 Activity Output Outcome Impact Transition Activity Output Outcome Impact Transition

×