-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Develop RAM Engagement Prioritisation Template #67
Comments
This is the current set of proposed dimensions for RAM project engagement prioritisation (tested in DCE context):
|
This looks great @f-rower ! My understanding is that then this issue is basically going into detail on step 3 - we should probs create separate ones for step 1, step 2, and the overall plan (which tbh I think can be #66 ). If this is the case this should maybe be renamed to 'RAM project prioritisation', with the general flow being called the RAM Engagement Pipeline |
I agree with the sentiment, but before we make too many changes, perhaps let's bring up this plan at next Monday's meeting @harisood so the team is somewhat aligned on what's happening? |
@f-rower is this what you had in mind for bullet 3 above?
|
It's pretty basic but some initial thoughts there! |
Thoughts and actions following from discussion during RAM meeting 11/3/2024
|
RAMs to carry this out for their own project and provide feedback by 22nd April |
Provide a description
This issue focuses on developing a RAM Engagement Prioritisation Template.
Links to issue #66
Currently, this RAM Engagement Prioritisation Template is based on a first successful attempt at developing a framework for prioritising RAM engagement within a programme, and using it to obtain buy-in from programme leadership.
Discussions between @harisood, @dingaaling, and @f-rower show that the nature of RAM engagement also depends on the lifecycle stage of a programme. Assessment of programme lifecycle will need to be a preceding step to RAM activity/engagement prioritisation).
Currently, we understand the lifecycle as having three steps: steps 1-3:
Therefore, a more generic version of the RAM Engagement Prioritisation Template will be the long-term goal of this issue.
Tasks to complete:
The text was updated successfully, but these errors were encountered: