CPS releases follows ONAP’s Release ( see Releases - ONAP Wiki - Confluence )
...
CPS do a ‘'Scrumban’' way which is a mix of both scrum and KanBan
2 teams
to accommodate daily stand ups , code review and task grooming process
focus of epic level , i.e.
team 1 members is a mix of developers working on epic #1 and #2
team 2 members is a mix of developers working on epic #3 and #4
Weekly individual schedule to attend other team stand up to sync
...
Challenges
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 | |
Different epics varies duration | |
Multiple epics in progress simultaneously |
Proposal
| Gliffy | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
PO backlog refining
Start of ONAP next release
Bi-weekly with stakeholders
Backlog grooming top priorities
Ensure ‘priority agreed’ epics gets groomed straight awayas soon as possible
Epic level planning
Done by Scrum scrum master/epic owners + PO/epic team?
WIP limits
PO to agree on time-frame based on stakeholder expectation?
use given timeframe time frame to create ‘sprint’
each tasks on epic is planned to be completed on certain ‘'sprints’', i.e.
all on epic 1 is to be done on Sprint 1
2/3 tasks from epic 3 is on sprint 1 and rest is place on sprint 2 …
Use scrum board by epic to visualise progressUse of ‘due’ on tasks to
Dedicated sprint backlog for each epic
Plan for '2 weeks' goal on agreed tasks for a particular epic
Epic level update
update and plan regularlymeeting (weekly? monthly? …)
Development
Backlog grooming on demand
as needed
Stand up
daily
Mini releases
as needed
Release
based on ONAP timeline
Retro
| Gliffy | ||
|---|---|---|
|