Project Strategy and Ways of work

[Davsarper]

Goal Title

The aim is to develop a project strategy and revise best ways of work to achieve it

Description

Through several strategy sessions we will:

• Define our north star (vision & mision)
• Establish the project pilars or areas, defining what success looks like for each
• Prioritise the measure of success, which are essential to consider the project succesful?
• Identify work required to achieve success
• Allocate work by team
• Produce an initial roadmap
• Evaluate required effort for the work against team capacity
• Develop and agree new ways of work, including meeting structure and use of project's repositories and projects

Definition of Done

When will this be considered as succesfully completed?

Details

• RACI
  • Accountable team or person: RAM, RPM
  • Responsible team or person: REG, RCM, CO-Is, Others
  • Informed and consulted people:
• Estimated effort FTE
  • High

Resourcing

February

• Whole team 1 day meeting
• RPM: 0.2

August

• RPM: 0.3
• REG: 0.3

Task and issue breakdown

• Plan sessions
• Conduct and facilitate sessions
• Strategy output: presentations and materials with outputs
• Ways of work: create project and documentation #44

Checklist

• This Story have been agreed with project members, it tackles prioritised work
  • If not: Label as ForPrioritisation so it discussed in the next monthly meeting, do not set a status
• I have filled in the Team Accountabe field
• I have included this Story in the agreed upon Milestone, set status as Planned
  • If not: set status as Backlog, to be Planned via weekly meetings or async discussions
• The work to be done is likely to span over a month
• I have broken down the work in monthly issues and added them above
• I have labeled this issue according to its main project: SATRE, TRESA, CORE DSH (ELA) or other (please agree and create a new label if necessary)
• If known: sum the total effort (points) of tracked issues and add it on the body
• Select a Story level of effort in the project fields

Reporting

5 February to 8 April

On 13 February the DSH had its second strategy session, based on last year's work it tried to define and prioritise specific work and activities for the project by creating milestones by project workstream. While we discussed aspects of the Community workstream in depth there was no time for other workstreams.

Therefore the definition of milestones and their prioritisation needs to be continued and more effectively integrated into monthly discussions. A current priority once the FY has ended is to revisit ways of work and specifically roadmap management.

A first effort in that direction has been the creation of a first project report to be used to better communicate and discuss some elements of the monthly meeting, in this way it resembles more weeklies where the asynchronous elements help make better use of the meeting time.

As further improvement to ways of work a proposal on how to better engage with PIs was developed, but not yet discussed.

14 August to 18 September

• Modified weekly template around stories rahter than people: improved reporting clarity and capacity
• Decided to hold monthly planning meetings and modify monthly date
• Identified the need to revisit priorities beyond SATRE and explore resources capacity

Initial strategy sessions

This story resulted in a project clear strategy and roadmap, as well as a first (since updated) proposal for ways of work.

Related work for this story continues in #54

[Davsarper]

@harisood I want to close this story considering we delivered what is was set out to do, I wonder though where to properly reflect ongoing work related to strategy and prioritisation, I am especifically thinking of the meeting we will have to reprioritise due to limited resources.
Do you see room for that work in your existing stories, on #34 perhaps (maybe wiht proper updates)?
It could also fit under my story #54 but feels different

[harisood]

I wonder if we should be having cadenced reviews of the strategy to make sure it's still relevant (e.g. quarterly), in which case we should keep this issue open?

[Davsarper]

On one hand it makes sense, on the other if everythign is "ongoing" we loose some insight about the workload and have a permanent issue for discrete tasks. If we keep it, then we should adjust effort

[Davsarper]

I am reopening as after 1st planning meeting it seems like the ongiong changes to WoW, planning meetings and strtegic decisions will continue to happen and they do fit here. Will evaluate wheter or not to keep WoW as part of #54 or not

[harisood]

Jan planning

Plan for an explicit strategy revisit session in Feb

[Davsarper]

@Davsarper wants to make this as much as a priority as possible to:

• Create due reports
• Revisit reports and monthlies format
• Propose and discuss PIs WoW

[Davsarper]

In May still want to do the above and (but may not be a must happen so not priority):

• work with @martintoreilly on roadmap v2