Prepared for Dr. Amine Merve Ercan — 28 September 2026

Purpose and evidence boundaries

This workbook develops demonstrable service education capabilities through two independent portfolio cases. It is not work commissioned, approved or deployed by Siemens Healthineers or Veralto. All product names, business baselines, targets, personas, regional arrangements and governance roles below are fictional design assumptions unless specifically identified otherwise. No clinical competency or product compliance is certified by these materials. Status: design draft, not a completed pilot.

User-confirmed professional experience: founder of CogOS; led the project with four teammates; venture currently in incubation. Project manager of Teacherpreneurship; project ended after a professor died and another professor wished to withdraw. Dates, exact responsibilities, incubation programme and delivered outcomes remain to be collected. These are real experience claims reported by the user, separate from the simulated cases.

Delivery sequence and evidence register

ID Deliverable Skill demonstrated Acceptance evidence Current status
01 Project charter and requirements Business alignment, project management Scope, owner, assumptions, acceptance criteria Draft below
02 Learner and customer journey Customer Journey Mapping Stages, touchpoints, pain points, owner, measures Hypothesis map below
03 Target operating model Operating model design Roles, decisions, interfaces, cadence, tools, metrics Draft below
04 Process specification Process design Trigger, inputs, branches, outputs, exceptions, records Draft below
05 Governance and RACI Governance, stakeholder collaboration One accountable role per activity, release authority Draft below
06 Prioritised backlog Agile planning User stories and testable acceptance criteria Initial backlog below
07 Working learning prototype Service education, digital delivery Playable flow and tested decisions Not built
08 Source and review records Quality assurance Source version, reviewer, change log Template below; no review performed
09 Pilot and measurement protocol Customer success, workforce development Outcomes, denominators, collection and follow-up Draft below
10 Dashboard Capability measurement Synthetic data labelled; formulas traceable Specification only
11 Pilot, revision and retrospective Continuous improvement Actual observations, decisions and before/after versions Not performed
12 Portfolio case and CV integration Evidence-based communication Links to completed work; precise claim boundaries Later stage

Concepts in plain Turkish

Agile: Büyük işi küçük, değerlendirilebilir parçalara bölmek; kısa aralıklarla gerçek geri bildirim alıp öncelikleri değiştirmek. Bir pano açmak veya planı sık değiştirmek tek başına agile uygulama değildir. Bu bireysel çalışma için Kanban ve haftalık inceleme uygundur. Gerçek Scrum rolleri ve etkinlikleri uygulanmadıkça Scrum takım deneyimi yazılmayacak.

Operating model: Hizmet sürekli çalışırken kim neyi yapar, kim karar verir, hangi araçlar kullanılır, ekipler nasıl devreder, sonuç nasıl ölçülür? Bir defalık proje takviminden farklı olarak kalıcı işletim düzenini tanımlar.

Process design: Belirli bir işin hangi tetikleyiciyle başlayıp hangi karar adımları ve istisnalar üzerinden hangi çıktıyla biteceğini tasarlamak. Operating model içindeki tek bir iş akışıdır.

Governance: Kim hangi kararı hangi kanıta dayanarak verebilir? Kim içeriği onaylar, itirazı çözer, değişikliği yayımlar veya geri çeker?

Agile working system for both cases

Board columns: Backlog, Ready, In progress, Review, Done. Separate Blocked flag with reason and next action. Limit In progress to two items. One-week review cycle is proposed, not claimed as past practice.

Ready: user need, acceptance criteria, owner, required sources and dependencies documented.

Done: artifact exists; acceptance checks pass; version recorded; prototype label visible; known issues recorded. Domain content cannot be marked expert-approved without an actual reviewer.

ID Priority User story Acceptance Initial status
MR-01 P0 As a learner I need to know what completion means Distinction from authorisation appears at entry and exit Ready
MR-02 P0 As a learner I need an escalation route Pending status, assigned role and context are visible Ready
MR-03 P0 As a reviewer I need source traceability Missing version blocks approved release Backlog
MR-04 P1 As an educator I need gap evidence Completion and assessment have distinct fields Backlog
AQ-01 P0 As a learner I need the right documentation version Exact-match and missing-match paths work Ready
AQ-02 P0 As support I need a useful question Query includes fictional product/version/context Backlog
AQ-03 P1 As a coordinator I need targeted reassignment Changed objective identifies affected learners Backlog
X-01 P0 As a viewer I need truthful case status Independent fictional case label on every public case page Ready
X-02 P1 As project owner I need improvement evidence Feedback links to change, version and retest result Backlog

Review agenda: demonstrate completed item; compare with acceptance criteria; capture user feedback; decide next priority. Retrospective: what delayed work, what improved clarity, what one change to try next cycle. Maintain actual dated records rather than reconstructing fictitious past events.

Tool access and setup

Notion is the proposed single hub for documents, backlog and evidence register. Notion connection verified on 28 September 2026. This project hub and case pages are created in Ema Ercan’s Space.

Workspace structure: Service Education Portfolio / MR Case / AquaTrace Case / Backlog / Evidence Register / Decision Log. Backlog properties: ID, title, case, status, priority, owner, acceptance criteria, source dependency, due date, evidence link, blocked reason. Evidence properties: claim, artifact, real/simulated, created date, reviewed by, limitations.