Steps and events before process change
Current Process Timeline
Feature will
be created on
OMNDC side
User stories
created on
OMNDC side
PMT: 3-4 topics confirmed mid Pi
Roadmap day
Here the
topics are
presented.
Epics are to
be created or
are already
created.
Impact on
providers is
discussed in
this meeting
Epic creation
Architect slot
PMT
Epic will be
created from
NDC/Stakehol
ders.
Solution will
be discussed
with
OpenSales
architect and
sizing to be
given.
Epic will be
presented to
the PMT and
will be
approved or
not
Kick-off/Refinement Super Tuesday
Topic will
start and will
be refined
into detail
with
NDC/Provider
PO gives the
green light if
topic is clear
and ready for
the PI
PI Event
Feature are
planned/User
stories are
refined for
the first 2
sprints.
Steps and events after process change
Improved Process Timeline
Feature will
be created on
OMNDC side
Roadmap day
Here the
topics are
presented.
Epics are to
be created or
are already
created.
Impact on
providers is
discussed in
this meeting
User stories
created on
OMNDC side
Epic creation
Architect slot
PMT
Epic will be
created from
NDC/Stakehol
ders.
Solution will
be discussed
with
OpenSales
architect and
sizing to be
given.
Epic will be
presented to
the PMT and
will be
approved or
not
Kick-off/Refinement Super Tuesday
Topic will
start and will
be refined
into detail
with
NDC/Provider
PO gives the
green light if
topic is clear
and ready for
the PI
PI Event
Feature are
planned/User
stories are
refined for
the first 2
sprints.
Before PMT
Part 1: Strategic Planning and Initial Approvals
•
•
•
•
•
Roadmap Day: Define and present new ideas and their potential impacts.
Epic Creation: Transform selected topics into drafted epics.
Architect Slot: Discuss technical solutions and provide preliminary sizing.
PMT Meeting: Obtain initial approval or feedback on the epics.
This first part focuses on defining the scope and strategic direction of the project,
ensuring that all proposed work is aligned with business objectives and technically
feasible. It involves high-level stakeholder engagement and decision-making.
Before PMT
Roadmap Day
• Timing: 50 days before the PI event.
• Input: Business objectives and innovation ideas from various stakeholders.
• Output: A list of proposed topics and their potential impact, identified for further
exploration and epic creation.
Epic Creation
• Timing: 45 days before the PI event.
• Input: Selected topics from Roadmap Day.
• Output: Drafted epics that clearly outline the scope and goals, ready for architectural
review and discussion.
Architect Slot
• Timing: 40 days before the PI event.
• Input: Epics requiring technical input and preliminary sizing estimates.
• Output: A technical solution proposal and initial sizing from OpenSales architects,
providing a feasibility assessment for each epic.
PMT (Project Management Team) Meeting
• Timing: 35 days before the PI event.
• Input: Epics along with proposed solutions and sizings from the Architect Slot.
• Output: Approval or feedback on epics; this may result in approved, returned for
revision, or rejected statuses.
After PMT
Part 2: Tactical Preparation and Execution Planning
• Kick-off/Refinement: Transition approved epics into scoped features ready for breakdown.
• Super Tuesday: Finalize feature-level details to ensure clarity and alignment.
• Pre-PI User Story Creation: Break down features into detailed user stories, preparing them
for the PI.
• PI Event: Finalize the plan and schedule for execution during the upcoming PI.
After PMT
Kick-off/Refinement
• Timing: 30 days before the PI event.
• Input: Approved epics from the PMT meeting.
• Output: Features defined and scoped, ready for the next phase of breakdown into US.
Super Tuesday
• Timing: 15 days before the PI event.
• Input: Features scoped during the Kick-off/Refinement stage.
• Output: Final refinement at the feature level, ensuring each feature is aligned and
clarified. This step focuses on preparing for the detailed user story creation.
Pre-PI User Story Creation
• Timing: 10 days before the PI event.
• Input: Refined features from Super Tuesday.
• Output: Detailed user stories created by the team, ensuring all features are translated
into actionable items that meet the team’s "Definition of Ready."
PI Event
• Timing: Scheduled day of the PI.
• Input: All approved features and fully refined user stories from the Pre-PI User Story
Creation stage.
• Output: A clear and structured plan for the PI, with features and user stories
scheduled for the first two sprints. The Product Owner provides the final go/no-go
decision.