Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Team notes/discussions

Stakeholders changes priorities based on their own timeline

Wasting time on epics that changes priority after

Bugs take over priority over any tasks

Client testing not done straight away

Proposal

Gliffy
imageAttachmentIdatt75366523
macroId1d7b5701-6998-4135-82b7-3d591b036b9b
baseUrlhttps://lf-onap.atlassian.net/wiki
nameProposal
diagramAttachmentIdatt75366516
containerId75333647
version1
timestamp1733349407163
  • PO backlog refining

    • Start of ONAP next release

    • Bi-weekly with stakeholders

  • Backlog grooming top priorities

    • Ensure ‘priority agreed’ epics gets groomed straight away

  • Epic level planning

    • Done by Scrum master/epic owners + epic team?

    • PO to agree on time-frame based on stakeholder expectation?

      • use given timeframe to create ‘sprint’

    • Use scrum board by epic to visualise progress

    • Use of ‘due’ on tasks to

    • Plan for '2 weeks' goal on agreed tasks for a particular epic

    • Epic level update

      • update and plan regularly

  • Development

    • Backlog grooming on demand

      • as needed

    • Stand up

      • daily

  • Mini releases

    • as needed

  • Release

    • based on ONAP timeline

  • Retro