Clifford Odendaal 30‑day plan (week-by-week, with program touchpoints)
Deliverables: One‑page product vision mapped to service areas; access checklist (Jira, Confluence, ServiceNow, monitoring). SAFe touch: Confirm Product Manager and RTE contacts and immediate PI cadence for alignment
Deliverables: Stakeholder map (Business Owners, Admin Services, Teaching & Learning, Cybersecurity), inventory of critical services, top 10 risk register. SAFe touch: Schedule team backlog refinement and initial story slicing; sync with Scrum Master to observe team DoR/DoD practices
Deliverables: Draft prioritized backlog (8–12 items) using WSJF and risk weighting; 1–2 timeboxed spikes for unknowns. SAFe touch: Validate feature/epic alignment with Product Manager and ensure dependencies registered in the Program Board for the next PI
Deliverables: Runbooks, rollback criteria, synthetic checks, and one dry‑run of a low‑risk change with telemetry validation. SAFe touch: Demo outcomes in sprint review; capture feedback for feature refinement ahead of PI planning
Deliverables: Final 30/90 roadmap, executive one‑slide (KPIs, top 3 risks, asks), handoff pack (runbooks, backlog, dashboards). SAFe touch: Prepare PI inputs (team objectives, dependencies) and review with Business Owners and RTE for program-level commitments
Artifacts I’ll produce: Team backlog, DoR / DoD templates, WSJF-prioritized feature list, runbooks, one‑page vision, exec one‑slide, and handoff pack. Ceremonies I will participate in: Daily standups, backlog refinement, sprint planning, sprint review, retrospective (team level); PI planning, System Demo, and Program Increment syncs at program level. Stakeholder cadence: Daily scrum (team), weekly 15‑minute exec RAG, biweekly refinement with Product Manager, and PI planning alignment with RTE/Business Owners
SAFe‑aligned Product Ownership for datacenter and networking: I’ll prioritize the team backlog for maximum program value, de‑risk the first changes with validated runbooks, and feed clear, WSJF‑scored PI inputs into the program so you get measurable outcomes without disrupting operations
Team-level PO responsibilities: Owns story prioritization, acceptance criteria, and backlog readiness for the Agile Team; collaborates daily with Agile Team members and the Scrum Master to ensure predictable delivery
Program-level interactions: Partners with the Product Manager and Release Train Engineer (RTE) to align features, PI objectives, and dependencies across teams; represents the team in PI planning and program ceremonies
Business alignment: Engages Business Owners and Customers for outcome validation and to ensure work contributes to value/viability across USF IT service areas
Example journey map I will create:
Proposal for USF IT:
